Re: "Michael Sentonas hopes trophy will remind staff that failure is unacceptable"
It's a bit like the budget to fix things when there was no budget to stop them going wrong in the first place.
42029 publicly visible posts • joined 16 Jun 2014
We had a MOTD reminding users to log out when they finished work, ending "This includes you $NAME_OF_LAST_OFFENDER". It worked very well; so much so we had to remove it after it was left pointing to the same person for too long once we stopped finding abandoned logins.
"That was OpenSSL, IIRC."
It was. But the point here is that unless you know why something is done in some particular way you can significantly screw up when you "fix" it.
"Also, how could a single guy change centrally important cryptographic code is a mystery to me."
But letting an LLM do it would be OK seems to be the current thinking.
"code is an unambiguous description of what the computer should do"
It's an unambiguous description of what the computer will do, not what it should do. They are not necessarily the same thing and it's from the gaps between that the bugs emerge and flourish.
I remember reading something a long time ago about comments in code that went along the lines of "journeymen programmers say what the code does, master craftsmen say why they did it this way, great programmers say why they didn't do it some other way.".
I always held that development was simply the process of launching a program into the maintenance cycle. Good documentation is going to be essential to the future maintainers. The code itself will never be enough.
"Agile happened because projects got bigger than 3 people could handle and developers thought they were better than project managers"
Alternatively they discovered just how crap some project managers are. What provoked me into retiring was my last (as it turned out) client's PM. After spending the afternoon before he went on holiday havering as who was going to do what he changed his mind that evening and rung someone up to reverse his eventual (and to my mind correct) decision.
Ironically, before he was appointed the client tried to get me to turn permie to take the job. They didn't realise how close I was to their mandatory retirement age and I didn't tell them. I was more than 2 years over it when I quit.
I've mentioned before an old colleague who's previously worked at Shorts in Belfast. The designer required a square hole in wood to take a steel rod. There was no indication as to how it was to be made; presumably the hole was too long for chisels or their mechanised equivalents. My friend waited until the designer had left, drilled a hole with the diameter of the side of the square, took the rod and a large hammer...
On reflection I've remembered the box girder bridge saga. Along with those half joint bridges they were one of the go-to type of structure* of the UK motorway expansion. The consequence was the reduced lanes and speeds over the Tinsley viaduct on the M1 and a bridge across a river (possibly the Wye) on the M50 and the circuitous routes round the Warley interchange whilst they were being repaired. How could I have forgotten them?
Bridge engineers are not always a good exemplar of engineering excellence and hang the cost.
* I almost wrote mainstays which would have been unintentionally ironic.
"Easily solved but no accounting for users stupidity in the plan."
And by solving it easily for her you have encouraged her to keep doing that. You should have pointed out that deleted means deleted. Emphasise how much work it's going to take you and then restore them in batches over a few days.
"Crowdstrike couldn't update machines that weren't connected to the Internet, and they couldn't update machines or VMs that weren't running, and they couldn't update VM snapshots."
They couldn't update machines that were switched off either.
So?
Yes, it's amazing that we still have people coming here and sounding out about staging without having read exactly how this happened. I'm sure a few admins who thought they had a staging setup got a nasty shock when they found it didn't help them.
I once got dumped in one of those courses where HR send staff to get their intelligences insulted (The staff's intelligences, that is; HR would lap it up and come back for more). The presenter was obviously pre-loaded with caffeine or something stronger - one bad sign was that instead of the usual "talk to your neighbour and introduce them" gimmick he made it two neighbours. I made my excuses and left PDQ.
"the advertising brokers who are using their monopoly position"
Brokers are businesses. Conventionally run businesses (Musk might not understand that concept) are aware that they are dependent on their customers continuing to do business with them. I rather think they can get away with pulling wool over their customers' eye in regard to online advertising in general but they wouldn't be able to disguise from their customers what would happen if they placed advertising on X.
Unconventionally run businesses might not be so aware. That doesn't stop reality being real.
There's usually a lot of truth in old sayings so here's one to consider: "He who pays the piper calls the tune."