Why developers should be excited about implementing migrations

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…