oh shit haha hey y'all. i'm blown away. also my site is blown away, y'all killed my cloudflare account. maybe go to your room and think about what you did.

The problem is not AI. The problem is still very human: the humans in charge don’t know what they don’t know, and they believe that whatever they imagine is true.

They also often believe that anything they can think of must be easy - just a matter of a worker spending a little time. Or maybe an AI can do it.

Management rarely learns from group failures, because they naturally assume that since the project was “easy”, it must be a problem with the workers.

CEOs routines run companies into the ground and the switch to a new company, fist full of cash on the way out. Once in a while, one of those repeat failures ascends into politics.

> The truth is, working in tech always sucked, and never really was what they thought it was.

This is just not true. Working in tech was awesome for me for at least thirteen years from 1988 - 2000. Probably well beyond, actually. The main reason it began to suck was due to business -- corporate acquisitions and mergers -- not tech. Working for a good company, solving fun problems, making meaningful software, and having happy customers was tech heaven.

The so called AI job loses are not due to AI. I don't think there is anyone out there to argue otherwise.

In a year but probably sooner, when software systems start collapsing, and they will, hiring in tech sector will skyrocket. In fact, I don't believe the world have enough developers to backfill for the AI deficiencies.

To me the math is obvious. Assuming humans touch a 1% of all software systems created, something we know it is simply never going to be true given the current state and upcoming regulations, the 47 million developers world-wide (and that includes all kinds of developers) are simply not enough.

However, although jobs will be back and it will be better payed, programming will "suck" even more and I don't think it will be for everyone. If you are not the kind of person that enjoys reversing a piece of tangled mess it might not be for you.

If AI is everything and AI is software then everything is software and everyone would like to have a piece of that software.

Damn. Phenomenal read. Just a really excellent piece of prose in its own right, topic be damned.

Yet the topic is also what makes it so good. It's written by someone who has also seen the vastness of impact technology has had, who has a firm grasp of the difference between technology and industry. Someone who knows the technology didn't get people addicted to social media and short-form videos and click-bait headlines and microtransactions, it was the industry that consciously chose greed and harm.

I love technology, and I'll keep wielding and mastering it until I'm dead in the ground. It's the industry aspect that I'm increasingly dissatisfied and disillusioned with.

Lovely writing!

> ... to which they nod before moving on to a lighter topic, like whether we're going to nuke Iran or not.

> There are no more juniors. There was a funeral for their passing in 2024. Nobody came.

> AI didn't take our jobs. Greed did.

Love the sarcasm, it carries a cynical form of experience :)

The sentiment of the article is spot on. I retired four years ago and it had already been going down hill for over a decade at that point. But…

The but is simply to remind people that programming can still be fun. Programming as a career? Not really.

If you don't believe me, that programming is still fun, go do some programming for your own personal project. (Still fun.)

(But, yeah, so glad to have left. I recall toward the end of my career, a coworker and I having lunch in Apple Park and sitting there, lost in thought watching a gardener tending the plants and trees in the center of the "park". When my co-worker started to say something about the gardener I knew instantly where his thoughts had also been going and what he was going to say next.)

> AI didn't take our jobs. Greed did. Same greed that moved factories to Bangladesh and keeps slaves in cobalt mines in the Congo, wearing a new mask. Tell the nephew to do something else. Anything. It won't save him either, but at least he won't have to pretend the thing destroying his life is a robot.

This hit me hard. This article is art. I think I need to sleep on this and read it again in the morning.

Programming has always sucked. The difference now is that we have AI agents that can do the sucking for us, and somehow that made everything worse because now we have to debug code we didn't write, can't fully understand, and definitely can't explain in a code review.

Oh man...

Really enjoyed it, and went back and read "Programming Sucks" which is also full of delightful nuggets like this:

"The only reason coders’ computers work better than non-coders’ computers is coders know computers are schizophrenic little children with auto-immune diseases and we don’t beat them when they’re bad."

This was beautiful. I also appreciated the backlink to Peter Welch’s spiritual ancestor to this essay, which I had forgotten how to find, and had the joy of reading again.

I’m trying to piece together a thought. Is it right if my employer wants to “own” the gain in productivity from these tools?

I’m being paid the same. I’m still doing 40 hours. The huge gains in productivity are not mine to enjoy, it seems.

I don't agree with everything this piece concludes, but I do admire getting to read through a whole HN article without feeling the sheen of AI co-authorship.

Not in my team and not in my code base.

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.

Isn’t it a bit ironic that a (presumably statically generated) blog post about “programming sucks” is being chocked to death by HN?

Archive link as the site seems down - https://web.archive.org/web/20260507003341/https://www.stvn....

I wonder if the embedded programming sector has been relatively safe and unharmed by AI. Is there anybody here who can weigh in?

Let me add to the chorus of admiration for this piece of writing. Poignant, accurate, appropriately cynical.

> You knew. And you signed off anyway. Because the alternative was losing the job, and the job was the mortgage, and the school fees, and the visa, and the version of yourself who'd fix it later once things stabilized.

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.

Im 19 trying to break into teach and third exactly what scares me they killed the apprenticeship before i could get in how do you become Sara if there's no Ben left to learn from.

Great read. Got absorbed into few scenes. The scene with applauds played in my head as a silent movie with Charlie Chaplin presenting his perfect plans and crowd applauding unrealistically fast (due to under-cranking) with piano playing Super Mario theme in background.

> The previous captain started a fire because another captain explained internal combustion to him at Captainpalooza 2025, and he wanted to start iterating towards that.

Hey, that's agile!

Such a great write-up!

Very well written article, joy to read, which is getting more rare these days.

Also I think it's always worth repeating the risk of losing long-term institutional knowledge when opting for AI as an explicit replacement for junior devs. Another tragic case of short-term gains prioritized over long-term success.

Wow some story. I forgot time reading it. It's fiction, Right?...

I'm doing my best to mimic enthusiasm, but it's becoming harder and harder to do so. I was afraid I was turning into a dinosaur, so I tried to be excited about AI. We can do more with computers, we can build faster, we can prototype, etc. But when you have automation you get people with spreadsheets running the business and this is a little bit too close to an assembly line for my liking.

I guess I'll be in the industry until it eventually spits me out, but if the rippling effects of software being devaluated can be so big that I don't know what I'll even do once this chapter of my life is over.

"AI didn't take our jobs. Greed did. Same greed that moved factories to Bangladesh and keeps slaves in cobalt mines in the Congo, wearing a new mask." :((( that is sad and so true. Economical thinking should be regulated

> The truth is, working in tech always sucked, and never really was what they thought it was.

This is just not true. Working in tech (starting 1989) was awesome for me for at least 20 years, and tolerable for quite some time after. The main reason it began to suck was due to business -- corporate acquisitions and mergers and tech-ignorant MBA decisions, for example -- not tech. Working for a good company, solving fun problems, making meaningful software, collaborating with committed peers, and having (and directly supporting) happy customers was tech heaven.

It sounds like the author shouldn't be in tech. For many, perhaps most of us programming is joy. It's why we started in our teens and have continued for 40 years. This is just a cynical post that adds no new value. We didn't kill the junior training mechanism. Juniors are still hired in the 100's thousands every year. There are valuable things to be said about the impact of AI. This isn't one of them.

It's one thing to have to cope with the stress of job obsolescence over a generation but the speed has picked up so much that people just feel rushed and paranoid. Never enough time to settle down and feel secure for a bit.

We all wanted gigabyte per second downloads not gigabyte per second life changes.

"There are no more juniors. There was a funeral for their passing in 2024. Nobody came. The machine does what they do now, but cheaper. 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. We optimized for output, and abolished apprenticeship. A few years from now, we'll wonder where all the seniors are. We shot them. Nobody will remember."

is brilliant writing. It's such good writing that it might convince you it's true. But it's cope. By that point, all senior engineer jobs will be automated too. And companies with old unknown chron jobs and USB sticks will get replaced by ones that innovate.

This is absurdly well written.

I don’t know how someone takes the familiar anxiety around AI replacing developers and turns it into something this beautiful and funny.

Once again, the programming industry has robbed literature of a potential Nobel Prize candidate.

> A few years from now, we'll wonder where all the seniors are.

Did we solve the ageism problem by mistake?

>AI didn't take our jobs. Greed did.

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.

Yes. And the reason for all of this is the same as it's always been, and requires literally no technical knowledge to understand.

There is essentially zero accountability for harm.

There is no button on your toaster that blows up the toaster.

But there's a link in your email. And that's a button.

And no one has figured out how to punish Microsoft or Apple or Google for allowing that to continue, though we do this just fine elsewhere.

Someone or something has to be punished, regulated or otherwise hurt for anything to change here.

Oh boy, I can relate to the sentiment of the article, it feels like how it has always been in enterprise consulting.

I don't get the sentiment at all, to me all that make it sucks is just incompetent people not programming nor tech.

> Later is never. We all knew that.

AI will do all the "later" things we could not do and the civilisation will flourish. :')

One of the best things I've read this year. Also one of the worst things I've read this year, actually. But also, I enjoyed reading it.

good article ! guy should be writing instead of IT delivery

lol

Please check back later Error 1027 This website has been temporarily rate limited

Funny and insightful! AI can't write articles like this :)

Is that ironic at all or is it really helpful? Hard to say.

So good. I had this read to me by Eleven Labs' reader and it somehow very very good with conveying the emotion. 5 stars, will recommend

Ya hit real hard. Are there people in tech that can really write like this? Wow nail on the head

Amazingly Real.

Very good simple explanation for what is happening.

I was expecting another AI rant. I got really great writing instead. This escalated quickly.

Computer languages cannot be trusted, even from ISO. You may have a chance with a simple preprocessor and simple assembler.

Don't forget, for most software out there, but not all, its development time is ridicoulus compared to its life cycle.

Loved it. I'm retired

> You remember being the junior whose first PR got shredded by a senior who took the time to explain why.

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.

Person needs to go work at another company

On Greed;

“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-...

The USB stick hints at a big problem in our trade though: how do you "reboot" your IT infrastructure if it literally burns to the ground? I'm not talking about Google-scale systems (which still couldn't restart from scratch IIUC but they're actually working on it?) but only about SMEs.

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?

Think this is very good article, and good to highlight with a link to an older one.

The Moloch article from Scott Alexander. Covers the broader themes.

Software just seemed immune from it for a couple decades, but Moloch caught up to it.

https://slatestarcodex.com/2014/07/30/meditations-on-moloch/