News for hackers. Stuff that matters.
Re:Why Google stores billions of lines of code in a single r... by smallnamespace on Sunday December 10, 2017 @01:05AM (#15890207)
The dynamics actually played out very differently at Google. Because it was a monorepo with automated testing, if you didn't want other teams to break you when they change the dependencies, then you had better have a robust test suite.

Breaking changes would then lead to a discussion with your team, rather than your fruitlessly trying to binary search to find the commit that broke you.

Over time, the culture at Google became that all teams need to write tests at the unit, functional, and (usually) integration level.

There are no comments on this comment yet.