5 ms·
Even at our current scale, we often make large changes throughout our code base, and having a single repository is useful for continuous modernization. Splittin
by ktRolster 10y ago
Even at our current scale, we often make large changes throughout our code base, and having a single repository is useful for continuous modernization. Splitting it up would make large, atomic refactorings more difficult.
I read it, but none of those things make me think better of their code.
- personjerry 10y agoAh, but the perfectionist engineer is rarely satisfied with production code quality. Hence we have another important part of a software company--the managers, who optimize for things like getting features out more quickly, things that are effective at doing what companies seek: make money.
- serge2k 10y ago> the managers, who optimize for things like getting features out more quickly, things that are effective at doing what companies seek: make money Which works great until the day you wake up to realize your code base has become an incomprehensible mess and your engineering systems are outdated and your competitors are shipping better software at a faster pace. I'm not really disagreeing, I'm just saying a balance must be struck. Really hate companies that view anything but feature work as a loss.
- spicyj 10y agoAs someone who works at Facebook on a team dedicated to improving developer efficiency (React), I assure you that FB sees value in long-term maintenance and tooling improvements. All the teams building features do too.