No I don't. I remember flagging that a tool is bugged, my manager-but-also-engineer-himself telling me "why cannot you do this, just press this button here" and then my entire work for that week getting obliberated because surprise surprise, the tool was bugged. And his voice "What? This wasn't supposed to happen.".
> You told yourself the seniors could absorb the missing hands, that the agents would cover the gap.
In every company I've been to the correlation between age, seniority, and skill, was very loose. I'll never forget going to my first job, talking to literally the oldest man there, and him telling me that smart pointers in C++ are silly and real men use bare pointers.
> You knew what happens to a codebase when the people who'd catch the errors get pushed out, or learn to stop catching them.
Recently I thought that we as a society need to stop expecting everything digital to work 24/7. Adding more nines to availability costs exponentially more effort but the gains are minimal. Imagine a world where every year for two days we just shut down the internet - one day for Postgres upgrade, and the other just for chilling on the beach. Would the society collapse? I don't think so. Managers understand this, but they prefer faulty software over giving their overly eager programmers a break.
> Of course, juniors weren't valuable for what they produced, they were valuable for who they would become: the senior engineer who knows where the bodies are buried.
Not all of them. Not even most of them. Very few would become valuable contributors, most of them would never make code better than AI does. That's the sad truth. I sit in a meeting with 6 seniors and we spend an hour discussing irrelevant shit and eventually postponing the decision until "later time" aka "we'll quickly do whatever once the situation becomes urgent". How is that better than vibe-coding a functionality?
> When she dies, the thing that produces people like her is already gone.
Literally not a problem because if every single company is fighting the same issue, then your company isn't disadvantaged by also having the issue.
“If greed were not the master of modern man--ably assisted by envy--how could it be that the frenzy of economism does not abate as higher "standards of living" are attained, and that it is precisely the richest societies which pursue their economic advantage with the greatest ruthlessness? How could we explain the almost universal refusal on the part of the rulers of the rich societies--where organized along private enterprise or collective enterprise lines--to work towards the humanisation of work? It is only necessary to assert that something would reduce the "standard of living" and every debate is instantly closed. That soul-destroying, meaningless, mechanical, monotonous, moronic work is an insult to human nature which must necessarily and inevitably produce either escapism or aggression, and that no amount of "bread and circuses" can compensate for the damage done--these are facts which are neither denied nor acknowledged but are met with an unbreakable conspiracy of silence--because to deny them would be too obviously absurd and to acknowledge them would condemn the central preoccupation of modern society as a crime against humanity.”
― From the book, Small Is Beautiful: Economics as if People Mattered by E.F. Schumacher.
1) See wikipedia for an overview/links to the book etc. - https://en.wikipedia.org/wiki/Small_Is_Beautiful
2) Small is Beautiful Revisited 50 Years On: A New Study Guide to Small is Beautiful - https://centerforneweconomics.org/envision/library/small-is-...
How does a medium-sized SME were all the payrolls depends on Sara and her USB stick do if, literally, their servers do catch fire.
You've got backups, then what? How automated is the reinstallation of your typical SME's infra?
The closest I saw to that scenario was some documentary where some little trading firm had just time to fetch the backup hard drives before leaving the building on fire after a plane crashed into it on 9/11. The CEO (I think it was the CEO) was explaining that had he not grabbed a HDD with the backups, the company was done (not that I advice onsite/offline backups on HDDs that you must not forget to grab when the shit hits the fan as a solution btw).
I understand the "just drink the cloud kool-aid" angle: but are SMEs typically doing that?
How many SMEs out there are depending on Sara's knowledge of the USB memory stick and how to use it?
I've definitely seen similar things. And I'm sure many of you did too.
Many houses of cards?
I devised a system to perform bare-metal backups onto an easily-swapped, external 2.5" hard drive, using Acronis. I provided a plurality of these hard drives, and they were to be rotated off-site. The system was tolerant of human error and would proceed with making valid, current backups even if the drives were rotated incorrectly, or if not rotated at all on any given day. The backup drives each had complete file history (yay shadow copies) from an ever-advancing date, so any given drive could be used as a time machine of varying resolution, and also as the single source from which to independently start fresh.
I'd watch the logs to see that it was done, and for the most part: Whoever was assigned to that role normally did it properly-enough.
I documented it and showed the other technical folks how it works.
Sometimes I'd wander back and make sure the backup drives weren't accumulating on-site (there should never be more than 2 on-site). I'd periodically test these backups by restoring them completely onto identical hardware, to make sure the system hadn't got crufted up somehow and that it still continued to perform its task of restoring a working system from zero.
It worked fine for years and years. We never had to use that backup, but I had every confidence that it would be useful if that ever became necessary.
Eventually, my role changed and those things rather officially became Not My Problem.
Later, they moved the accounting system from that lineage of stout Proliant boxes to a trash-tier small-form 1u Lenovo machine that someone found used, on eBay, for cheap.
Backups are handled by the clown, somehow. The last I heard anything about it, the person doing the talking was very pleased with the money they'd saved and that they'd no longer have to pay "extortion" to Acronis.
I have every expectation that nobody has ever restored these backups. They're probably relying on the sheer hope that they'll never have to restore them, much less from zero.
And I also hope they never have to restore them, lest they may find out exactly what that data is worth to them.
Like every job, we overestimate our importance.
What do they do? They pay everyone the same as last month as a temporary measure, ask you to talk to your manager if your pay should be more this month, warn everyone that they're going to recalculate the payroll and adjust any differences next month. Then they calculate everyone's pay from the inputs, which really isn't such a hard problem when the alternative is failure. Maybe they pay some fancy consultants or an SAAS provider for a few months. Maybe they have to cut a few corners. Maybe they even get fined by their state's DoL. Life goes on.
I think at least in part, that is the point: orgs are missing the part of the equation where the institutional and organizational knowledge is critical. Sure, the code to accomplish parts B and C can be re-duct-taped together in a month or so by off-shore, or maybe an agent... but part A, its plumbing, and why it does what it does the way it does it due to historical failures and the knowledge behind that is probably what keeps it going.
Those things are learned starting at the ground level by bumping into them in the trenches.
The SpecOps guys have the following bit of wisdom on offer: "Two is one and one is none".
Maersk ground to a halt because it got done nearly 100% by cryptolocker. IIRC they went to hard copy records, called everyone, got all of IT together with some company credit cards to get new laptops and flash drives and shit and literally rebuilt their infra from scratch.
https://www.itnews.com.au/news/maersk-had-to-reinstall-all-i...
I read a better post mortem but thats the highlights.
>How many SMEs out there are depending on Sara's knowledge of the USB memory stick and how to use it?
Part of my day job is finding, documenting and remediating these sort of issues.
"The CEO Coded this application in VB5 15 years ago, the entire business relies on it, theres no source code, theres no binary backups and the one computer it runs on just had its PSU fail"
"Theres a cron somewhere that compresses, zips and transports the payroll database interstate, outside of our network, before our weekly pay run"
"Theres been no documentation of this environment for 20 years, most of the hardware is that old, and the team that developed it just sold all their shares and left"
This shit is my life lmao.
Theres obviously some bias, because the good companies aren't asking me to do it for them. But I make a decent living examining, documenting and remediating this shit.
One of my favorite jobs early in my career was working for a really shonky wireless isp. The majority of the network was built by sales people using terrible tools with no documentation. I actually cant overstate how bad they were originally, they had entire areas of network with no recorded network config or credentials. My daily workflow was getting a ticket from a customer I had never heard of > trying to figure out where they were and what services they had (2 of their 3 billing systems were offline, and I often had to grep out information from a sqldump to find this stuff) > performing a discovery, L2 upwards of their infrastructure > semi offensively trying to authenticate into their infrastructure > resolve and document so that other people can reliably service them. All while pretending this was absolutely normal to the customer. Turns out there were lots of ISPs in the same boat, and turns out there's lots of non isp businesses in the same boat.
Don't forget, for most software out there, but not all, its development time is ridicoulus compared to its life cycle.
The doll catches the fire.
The greed of gullible CEOs. I assure you there's a talent pipeline collapse that's in progress and you'll be hard press to find senior engineers in few years because AI output is not something a junior can ride easily and you killed that pipline of junior engineers today.
Slaying the goose that lays the Golden eggs in your corporate greed.
You'll pay pack with interest and then some.
Good luck.
Sure. But when it comes to coding, even greed couldn't do it without AI. At best it could outsource, still giving it to humans.
Build it greenfield 7 years ago, everyting is well documented, everything special screams at you if it breaks and tells you how to fix it (if it even needs fixing).
We spend time on upgrading stuff because of external dependencies and otherwise add new features.
Programming doesn't suck.