4 ms·
The problem I find is you get handed a legacy system and asked to give it new features. You have no idea what the code does. You have to narrow in on the tiny p
by xupybd 6y ago
The problem I find is you get handed a legacy system and asked to give it new features. You have no idea what the code does. You have to narrow in on the tiny part the customer wants changed. They see the change as simple and easy. So they don't understand why you spent three weeks refactoring and adding test. They just want their new feature. As this goes on the code gets worse and the customer gets more unhappy.
- fckthisguy 6y agoIn cases like this, being "handed a legacy system [with] no idea what the code does" is already a red flag. I've developed on plenty of legacy systems and the ones that went the best were the ones where I was given time to become familiar with the code first. Preferably with the going-out developer still around. The fact that POs and stakeholders don't try to protect this knowledge exchange, and often see it as unproductive, is a major problem in our industry.