Articles & Stories
Are you choosing between upgrading your package now, or upgrading later? Do it this instant. Later becomes never. Stop thinking about if 2.5 to 2.6 is worth the time. Just upgrade.
I know, you have to pay a price right now. It’s non-trivial. You have to scour the release notes, and write a script that touches every one of your source files. I know you have real work to do, and you don’t want to wait a week while your users piss on your now-shaky product. But the patina is worth more than the new features, speed increases, cleaner API, and faster development. It’s an investment. One day, version 3.0 is going to pay dividends.
Don’t sentence your peers to compounded misery. That 2.5 to 2.6 upgrade you were going to do, but wasn’t worth the time — wait, now it’s 2.7?
Now your peers have to read the old docs about 2.5 to 2.6. They’ll struggle in a vacuum, since the tech zeitgeist no longer recalls the minutiae of that upgrade. And then, they’ve got to do 2.6 to 2.7? Following your example, they’ll fail to muster the will-power. It’ll be 2.5 forever.
Make upgrading a habit. Develop a visceral reaction to seeing 2.5, when the docs say 2.6. Don’t feel clean until your systems are fresh.
Berlin-based software engineer building machine learning backends.
If you're in the area, send me an email, auf Deutsch oder in English.
Want updates when I write?