722 karma · joined August 25, 2022
I was running a cluster of 4 of them when I was learning about Kubernetes
Spec sheet: https://psref.lenovo.com/syspool/Sys/PDF/ThinkCentre/ThinkCe...
I spent several years maintaining a C library that handled these for some embedded instrumentation. This included most key mathematical functions as well. Most interesting thing I ever had to look after.
The outcome is that introducing the tool actually tangibly increases business risk in a changing climate.
One thing in life is never to get into a position where you need to defend yourself against this scenario which is why I would never even consider using the tool.
The true cost of all technology is only apparent when you get the exit fee invoice.
Someone else's computer has been painful and very expensive for our organisation so far. Escalating costs aren't even the worst problem.
And GitHub is popular but seriously so so so not right in many ways.
What they have succeeded in doing is merely centralising leverage and forcing entrenchment.
But that doesn't mean it works. It's literally only there because it is entrenched. A lot of the time it doesn't work and has an extremely large support cost.
But the mouse, if it doesn't work and it says it does on the box then that is the vendor issue.
People don’t care about that. They want the computer to go away and actually stop bugging them.
What is the truth is that they had all the opportunities and staff and squandered both on mismanagement and quality issues and continue to do so to this day. What we have left is pissed off customers, pissed off developers and a declining market position other than where they could lock businesses in. The only market keeping them alive is entrenchment and naive MSPs and retail pushing their crap.
I look forward to their VR strategy going down the toilet with Meta, where it belongs.
Fire the board. Kill off the marketing situation which is basically lies at this point, remove telemetry from your products, invest in QA again rather than getting “insiders” to do it, remove decades of bloat and build quality not quantity and perhaps people will have confidence again.
In a survival situation you're better off with VHF/UHF HTs and a tested network of people that you already know who have them and how to use them. And even that is of dubious use.
It can be used for good and it can be used for bad. Less is more with Helm otherwise it will create bad.
This (and CNI) are the rough bits of Kubernetes.
Now I have a studio display. Get out of box, plug it in, works. Open laptop, spans display instantly. Unplug, windows move to the laptop. Never goes wrong. No bugs.