The inevitable reality of life: change.
Sometimes you walk out the door.
Sometimes, you’re pushed.
Either way, it’s change. Embrace it.
The inevitable reality of life: change.
Sometimes you walk out the door.
Sometimes, you’re pushed.
Either way, it’s change. Embrace it.
Reverting a commit is an awesome concept. Reverting a reversion is even better.
In IT, sometimes, you should clean out the fridge, so to speak. For example, delete old accounts. Delete old rules. Delete old processes.
I was cleaning out my own email rules just the other day, and this one came up, which was from another account’s auto-responder. It has been dutifully sending out responses to every request that hits its mailbox… for about three years:

Time to clean things up a bit.
I’d never paid attention to certain version numbers, and release dates, of certain applications. And, frankly, always assumed that things were up to date.
Apparently, that assumption was likely mistaken.
$ bash --version
GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin18)
Copyright (C) 2007 Free Software Foundation, Inc.
Wow.
The copyright on that specific version on the state of the art macos — all Macs — was 2007. TWELVE years ago.
What version is currently available? Unsure, but I’m going to bet that it’s most certainly not v3.2.57(2).
Ah, yes… it’s slightly newer:

Isn’t quite as state of the art having GPL-software that’s static. Yeah, I know, it makes things more stable. I get it. But there will be some newer capabilities, improvements, bug patching and so forth that will be revealed with the continuing march of progress.
Now… what are the risks to doing the upgrade?
[Edit: Well, I’m certainly not the first to see this and I only started pondering it when I wanted to make kubectl auto-complete available directly. Probably a good idea to upgrade.]

In fairness, I wasn’t doing any low-level dev work — no code. But was doing some higher-level management type work. So, this whole remote/iPad work thing has started to make sense for me in some limited cases.