I often hear that developers aren't keen on doing work to upgrade the frameworks/platforms/tools that they use (or the software they're building is using). It's not writing code, and so it's not considered "real development" work.
I think that doing the work to support upgrades or migrations is one of the most important and valuable things a developer can do:
- It's often a simple way to fix potential security vulnerabilities.
- It normally brings performance improvements.
- Updates bring new capabilities and options for things to add to the software.
- Keeping up with the latest versions makes future updates/migrations easier.
- It can help you learn and get hands-on experience with the latest technologies.
- It can allow you to see a large part of or various/obscure parts of the code base, helping you to learn more about the code you're working on.
- It can make it easier for other developers in the team.
So, a high-impact task that helps you learn while supporting the team by doing things they don't want to do? Sounds like a great thing to prioritise if you get the chance.
0 comments:
Post a Comment
I get a lot of comment spam :( - moderation may take a while.