Change, It’s Rarely A Good Thing
Most especially when it comes from the management classes.
Change is a thing that’s inevitable in all our lives and we often just have to suck it up whether it’s to do with looking disappointedly in the mirror as we age¹, the rapid inherent dilapidation of our unaffordable motor vehicles, or primarily with the things that matter the most — the technology that we progressive engineers depend on the Grand Game use every day.
I wouldn’t like vim to change at all, that would be a form of technological heresy, nor would I like awk, grep, or sed to suddenly have their command line options change or their output me reformatted overnight either. Those events would be extremely irritating, borderline panic inducing, and break much of the code I’ve written during my accidental tenure in the Grand Game of Software Engineering².
It’s actually one of the reasons I refuse to use the ever changing VSC with its bells, whistles, add-ons, and inconsistencies. Sometimes you don’t really quite what’s going to happen when you give in to the relentless nagging to update some add-on or other, quite often one that you never knew you had in the first place.
Alas, things do change and it can be intensely irritating when do — most especially if they don’t have a really good reason to do so.
