4 ms·
This is not true. If something's working, you don't change it for no reason. Business requirements and requests change all the time. 90% of our work is done in
by grumple 5y ago
This is not true. If something's working, you don't change it for no reason.
Business requirements and requests change all the time. 90% of our work is done in response to that. The other 10% is fixing up technical problems due to increased scaling or bugs found, and then basically never do we upgrade a system to keep up with security updates or change to a more modern tech.
- AnIdiotOnTheNet 5y ago> This is not true. If something's working, you don't change it for no reason Sure, there's often a reason like "we wanted to write it in a different language" or "we've overhauled the UI to be slower and more cumbersome".
- Nextgrid 5y ago"we need to justify our front-end developers' and designers' jobs"
- nonameiguess 5y agoThis highly depends. I believe what Grumple is talking about is contracted work for a specific customer that is asking you for something different, even though what you've already delivered works. You're talking about consumer-facing product teams that make whatever they want and try to sell it after the fact, coming to their own decisions regarding what their "requirements" should be. When your work is funded by a specific customer, the requirements are whatever that customer says they are. And they're almost never going to let you change something just because you wanted to in order to learn a technology you can put on your resume.