3 ms·
It happens when you have a lot of new people who refuse to work with legacy code (which is anything over 2 years old), trivialize the complexity of the existing
by trixie_ 5y ago
It happens when you have a lot of new people who refuse to work with legacy code (which is anything over 2 years old), trivialize the complexity of the existing system (because they don’t understand a tenth of what it does), go create a sub par replacement with tons of people and years of work (that ends up coupled to the legacy system anyways), and now the company has two systems to maintain requiring double the resources as before. When everyone gets fed up and leaves, the cycle will start again. Our system is about four levels deep now. It’s the f’ing matrix.
- nikau 5y agoMost of the new development I've worked on has been terrible, I attribute it to agile and the two week sprints churning out non stop MVP code that's technical debt from day one.