Hacker News new | past | comments | ask | show | jobs | submit login

Despite almost everything being in one big repo, it has silos. Not everyone has read access to everything. Some code, like the important bits of Search, is only available on a need-to-know basis.



So what happens if search adopts your internal library and your update to it breaks search? Do you need to get someone from the search team to go investigate? How is that prioritised?


The tooling is such that you will know if a change will break something in a silo before it is submitted. You then work with the affected team. It’s not a big deal.


it's search's fault for locking down their code and so search gets to fix it.


And if they don't think it's important right now? Are other teams who need the change just blocked?


? then their code doesn't build anymore and they will have a very sad time.


But I thought the precommit hooks would block this merge if it breaks search?


There’s no merge or precommit hooks or blocking.

If they chose to make their code invisible to me then I can’t fix it.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: