

This is the correct answer.
Just another Space Monkey. An Infrastructure Idealist.


This is the correct answer.


My first tech job was in '98. My recommendation is to take the LLMs as the democratizing force they are and start running with every project idea you’ve ever had. Prototyping out your ideas has never been easier. If you land on an idea that lets you transition from employee to owner of your own self-made money printer, why not bet on yourself?
I like to daydream about what you get when all of those very smart, unemployed engineers are doing with a Claude MAX account and a whole lot of time on their hands. I’m pretty sure Big Enshittified Tech is about to have a whole lot of very new, very agile competitors very soon. Combined with a ton of very expensive consultants flooding the market, I’m feeling very entrepreneurial. ;-)


Feel free to support the argument that something less than 100% coverage paid for at the cost of electricity instead of the cost of human labor is somehow inferior to the alternative.
There’s as big a difference between “programmer” and “computer scientist” as there is between minor league and major league professional sports athletes. The folks trudging through life who were C-average students generally don’t understand what it takes to do Grade-A work and they certainly don’t put in anywhere close to the level of effort required. If competence were in greater supply, there’d be fewer Enrons. So, let’s be serious about the real capabilities of the average journeyman coder for a minute.
And that’s before we consider the exponential rate at which LLMs are getting better at getting better.
Face it, kiddo. 100% code coverage is now the bare minimum for any new project that wants to call itself “professional grade”. Anything less is an unserious hobby project. Direct your attention at the CVE remediation list for any major project if you need help understanding why. Stare at those graphs as long as it takes for you to understand the new reality you’re living in.
Nobody mourns the out of work ice carvers that the advent of refrigeration caused. The history of automation in the automotive industry has a lot to teach anyone interested in gaining insight useful for grappling with this new technology.


Thank you for confirming that you’re still making incorrect assumptions.
If you understood what I wrote, you’d realize that I didn’t do the thing you’re accusing me of. You just didn’t understand what I wrote. Your misunderstanding is not my error.


I understand what they’re pointing out. It’s the wrong thing to fixate on.
A very common cognitive bias in humans is that we tend to over-estimate our own ability and under-estimate things we have limited expeerience with.
The decision to assume I don’t understand what I’m talking about is based on incorrect assumptions about both of us.


After having been in the tech industry a couple decades, I have experienced a whole lot of people who get very grumpy when they encounter the truth. People like to lash out when they encounter information that challenges their deeply-held beliefs. Cognitive dissonance is often expressed in funny ways.
What you’re seeing is the kind of large-scale existential crises that only once-in-a-generation technologies can cause. A whole industry of individuals who built their livelihoods on being semi-clever for a living are now being outpaced by semi-competently operated LLMs. Nobody is ever happy to find themselves confronted with adapt-or-die circumstances.
And before anybody objects to my use of the phrase “semi-clever” - we wouldn’t be witnessing a vulnpocalypse if the situation were any different. For better or worse, the incompetence on display by the leadership of the US Federal Government isn’t unique. Most middle-management positions are filled with knuckleheads barely more functional than the current cabinet.
Americans working in the tech sector have been short-changing everybody for so long that “quality craftsmanship” is treated as a four-letter word, uttered in front of your boss only if you’ve already secured a position elsewhere.
All of the epithets I hear leveled at AI Slop are criticisms I saw directed towards incompetent coders on websites like TheDailyWTF over a decade ago. The fact is, LLMs have gotten so good at generating code in the last two years that the entire concept of corporate-managed software services is in the process of dying off - its corpse being cannibalized by millions of LLM-powered startups staffed by single-digits worth of humans.
What we do with these tools is a choice.


Every coder trying to justify their jobs brings that up. And they’re all wrong.
You don’t do 100% correctness already. In terms of correctness, LLMs generating code with 100% coverage will run circles around whatever you do write today. Demonstrably.
You don’t have the winning argument you think you do. You may want to re-read the parable of John Henry.


It never needed to be like this.
AI may be exposing and exploiting the world’s tech debt. But AI is also the solution to the problem, too.
LLMs now produce code fast enough to make 100% test coverage achievable for every software project.
There are now zero excuses for having under-tested code in production.


Uh huh. And refrigeration has robbed everyone of essential food preservation knowledge.
Automation does that. Whether it’s a bad thing depends upon many factors.
Current frontier models aren’t guaranteed to last. Commoditization is coming and democritization with it.
If you express childishly naive ideas you can’t justify or support, don’t be shocked when the person with decades of experience clocks your inexperience with the subject they’ve spent a couple decades mastering.
Your first mistake was thinking you were an equal participant in this conversation. This is the third time I’ve said as much, yet you still persist in the delusion that what you have to say matters more than what you could be learning if you were honest about where you are in your learning.