Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

If you read a history of Uber getting to monorepos [1], [2], it is obviously that they did it as an attempt to make their shared spaghetti code a bit more structured. Now they are writing articles about fighting a consequences of that move. For me the moral is: never go monorepo. It is at least counterproductive, but more like destructive even for large capable teams.

[1] https://eng.uber.com/ios-monorepo/

[2] https://eng.uber.com/android-engineering-code-monorepo/



Consider applying for YC's Summer 2026 batch! Applications are open till May 4

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

Search: