3 ms·
Not a CTO. 1. Not only legacy code eats resources that can be thrown on new developments. While legacy code is most troublesome, it still will be at maximum on
by baybal2 8y ago
Not a CTO.
1. Not only legacy code eats resources that can be thrown on new developments. While legacy code is most troublesome, it still will be at maximum only twice as bad resource-wise, than new and pretty code.
2. As company grows, it may well be that a piece of software being used by by less than 5 people at the company, but require an own developer team to continue actively support it.
3. Maintenance resources vs resources spend on development is a never ending drama.
4. You should proactively think how to cull you internal projects, and be able to dictate to the rest of the company to stop using it.
5. Custom software for "business guys" - an easy way to multiply IT support budget. Hiring technically illiterate analysts, finance people, supply chain people costs a lot, a great great lot.
6. Last point. THERE SHOULD BE AN IRON WALL in between people making "money making code" and all other tech at the company. Can't stress this more.
- frant-hartm 8y agoCould you elaborate on the last point?
- baybal2 8y agoWell, the most extreme case will be for example: in an online ads company, somebody disrupts the team responsible for bidding software to do somebody's pet project, do a UI job, or making them do software for internal IT needs.
- toadworrier 8y ago> While legacy code is most troublesome, it still will be at maximum only twice as bad resource-wise, than new and pretty code. This reflects an assumption -- perhaps one nurtured by engineers -- that paying down technical debt is about writing new shiny code. But in my experience, new code is where most technical debt accrues. True technical debt reduction usually involves improving the behaviour of old code. It might also involve cleaning up that code; but mostly it's about cleaning up the workings of the running system.
- dasmoth 8y ago2. As company grows, it may well be that a piece of software being used by by less than 5 people at the company, but require an own developer team to continue actively support it. I recognize the scenario you’re warning against here — but worth being careful about conflating user count with value produced. Some really valuable tools have small numbers of users, e.g. tools for curating some internal dataset. Sometimes the number of users is small only because the tool is handling most of the drudgery.