Hearing the feelings in this rant, which does touch a nerve, I can’t help think about how different the developer community reaction to the LLM push might be if the focus were on quality instead of efficiency.
-
I can’t think of another time when software devs had to be •forced• en masse to use a new technology that was supposed to help them. Usually we’re kind of stupid for the shiny new things: jamming them in when they solve nothing, doing unnecessary rewrites just to use the new hotness because it’s so cool and fun. Usually we’re the one trying to shove it down mgmt’s throat (or sneak it by them) rather than the reverse.
But not this time.
7/
Java?
-
But that’s me; I don’t think my ethical concerns are shared widely enough for companies to have to be ramming AI down developers’ throats the way they are. The token quotas etc are a symptom of something large and deep.
Maybe that post about MTBF vs MTTR helps explain it.
/end
@inthehands that's a very well put thread, thank you for it.
-
@annehargreaves This really bugs me (and makes me infinitely sad), because we *had* good automation tools, concordance tools, terminology tools – a whole bunch of tools that were actually useful and made human translators faster, more consistent and so on, without compromising their own inherent style or flattening the voice of the text. And now, instead, we have shit. @janeishly @inthehands
@herzleid @janeishly @inthehands Yep. Gutted. Gutted to have lost my work after so long.
-
This is, if I understand it correctly, the same contrast that the OP’s distinction between MTBF and MTTR points to:
MTBF = quality (It rarely breaks)
MTTR = efficiency (It breaks all the time but we recover so fast!)
6/
@inthehands Another thing the cloud broke was the idea that MTTR has to be super fast. There are a lot of systems that are resilient and downtime is not a big deal. (Email, for example).
So the reality is that we have some systems that are mission critical and MTBF is the right approach. We can’t recover from failure because failure is unrecoverable. Then there’s a whole spectrum of MTTR where failures can be withstood and repairs have varying levels of urgency. MTTR doesn’t have to be instant for everything, in systems where MTTR is the right approach.
Getting whole generations to think about a problem a certain way is a soft form of monopoly. Look at the push to get LLMs into schools and they’re trying desperately to run the same playbook on LLMs. Raise a generation who know no better.
-
@inthehands His response was "why do you need all that? The AI can validate itself" and I was like "did you not read what I had just said". But it also made me realise we're thinking about what LLMs do in very different ways: I see them as tools for language modelling, with limitations arising from the way they work, while my coworker sees it as the path towards an actual thinking machine
@jmopp @inthehands that OAuth example is particularly apt. As it happens, I used gen AI to help with a fairly complex OAuth integration, and it made plenty of understandable but fatal mistakes - confusing different types of Auth tokens, recommending overly broad scope, etc. to the extent that I'm reasonably sure it would have been quicker to just read the OAuth spec properly.
-
I can’t think of another time when software devs had to be •forced• en masse to use a new technology that was supposed to help them. Usually we’re kind of stupid for the shiny new things: jamming them in when they solve nothing, doing unnecessary rewrites just to use the new hotness because it’s so cool and fun. Usually we’re the one trying to shove it down mgmt’s throat (or sneak it by them) rather than the reverse.
But not this time.
7/
@inthehands You can’t think of another? Microsoft Teams. Microsoft Office. Microsoft exchange. Oracle database. We only use ABC cloud service, etc.
Think of any time executives show enterprise software brand loyalty and you’ll find lots of tools that devs and engineers are forced to use. Where ostensibly it’s the “right tool for the job” but, in actuality, some commercial aspect drove the choice.
-
@herzleid @janeishly @inthehands Yep. Gutted. Gutted to have lost my work after so long.
@annehargreaves
It's so bleak. I'm still clinging on like a fool, but Q1 this year was a disaster so I've had to start looking for other avenues for income as well. -
I can’t think of another time when software devs had to be •forced• en masse to use a new technology that was supposed to help them. Usually we’re kind of stupid for the shiny new things: jamming them in when they solve nothing, doing unnecessary rewrites just to use the new hotness because it’s so cool and fun. Usually we’re the one trying to shove it down mgmt’s throat (or sneak it by them) rather than the reverse.
But not this time.
7/
@inthehands I felt forced to use Windows and internet explorer against my will quite a lot.
You're right though. Everyone else seemed to love it.
-
I can’t think of another time when software devs had to be •forced• en masse to use a new technology that was supposed to help them. Usually we’re kind of stupid for the shiny new things: jamming them in when they solve nothing, doing unnecessary rewrites just to use the new hotness because it’s so cool and fun. Usually we’re the one trying to shove it down mgmt’s throat (or sneak it by them) rather than the reverse.
But not this time.
7/
@inthehands oh come on are we pretending agile development and blockchains didn't happen?
-
I can image a developer parallel to the first, too: the human still using all their skills and experience, but with the machine catching mistakes, providing context and validation and vigilance that is •orthogonal to• testing and type checking and code crafting and — the big one! — actually •thinking• about the problem.
That’s a regime I imagine developers would feel a lot better about. And I know there are people out there pursuing it! But they’re not the ones dominating the conversation.
4/
@inthehands This is the way I get to operate at work, and it's *incredibly* satisfying to have a context aware autocomplete that's mostly helpful (it feels like the good parts of pair programming). Alas, "better code autocompletion" is not the world shattering impact being pitched to investors and CxOs, and the models available (at least from MS) are still the usual moral & ethical tire fires rather than the rare responsibly trained ones.
-
RE: https://hachyderm.io/@mitchellh/116580433508108130
Hearing the feelings in this rant, which does touch a nerve, I can’t help think about how different the developer community reaction to the LLM push might be if the focus were on quality instead of efficiency.
1/
@inthehands this. I am a manual software tester, not even a developer. And the push to go faster all the time is so exhausting. I am seriously consodering leaving tech. I have loved being a tester. But this is getting ridiculous.
-
I can image a developer parallel to the first, too: the human still using all their skills and experience, but with the machine catching mistakes, providing context and validation and vigilance that is •orthogonal to• testing and type checking and code crafting and — the big one! — actually •thinking• about the problem.
That’s a regime I imagine developers would feel a lot better about. And I know there are people out there pursuing it! But they’re not the ones dominating the conversation.
4/
@inthehands I think you'll find the reason centaur programmers don't dominate the conversation is that they self censor, because otherwise they get lynched by the "all AI is inherently evil" voices.
The moderate voice is never terribly loud, but in this space there's just no upside to being the one saying "actually there's a way to use this tool that isn't utterly shit"
-
@jmopp @inthehands that OAuth example is particularly apt. As it happens, I used gen AI to help with a fairly complex OAuth integration, and it made plenty of understandable but fatal mistakes - confusing different types of Auth tokens, recommending overly broad scope, etc. to the extent that I'm reasonably sure it would have been quicker to just read the OAuth spec properly.
@jmopp @inthehands this being said, I did get to something kinda working relatively quickly, which maybe made me more likely to stick with it until I got to where I needed to be.
So, on the one hand, is maybe a short path to a sunk cost trap, on the other, a short cut to 60% of the way there?
-
But that’s me; I don’t think my ethical concerns are shared widely enough for companies to have to be ramming AI down developers’ throats the way they are. The token quotas etc are a symptom of something large and deep.
Maybe that post about MTBF vs MTTR helps explain it.
/end
@inthehands To briefly interact with this, while devs usually do go after something shiny, it is usually the shiny things propped up by major tech corporations that make it through without much resistance - See react, express, angular, etc.
The current state of tech has a serious evangelism problem. I think most people have seen "tech evangelism" in the wild in some form prior but now I feel it reached a new level with the current marketing and push of LLMs, the inherent trust the tech corportions got for free from many of them, the way they focused on management figures to promote it instead of people who would actively scrutinise this.
Given the state where selling software solutions was becoming difficult for many and all the major corporations ensuring that everyone had to race to the bottom or devalue software as much as possible to then ensure that no one competes, it isn't exactly surprising that they wanted to turn the industry into a casino where they benefit from the licensing of the pokies and all the devs have to play the game.
Combine this with an economy that has been cooked by these people, developer distrust andtrust from other organisations only being placed in large tech corporations (or those tech corps will lobby it because they have the means to do so).
Developers who are concerned just don't really have any ability to resist internally or have the bandwidth to do so unless there are financial punishment to organisations that lean into this rubbish (which... there will be but likely for most of them, they will go bankrupt before it is too late).
There is also an asynchronous game as well, if you received slop and have to handle it, you have been given the difficult work that is also not valued and it is now at such a large volume.
-
I can’t think of another time when software devs had to be •forced• en masse to use a new technology that was supposed to help them. Usually we’re kind of stupid for the shiny new things: jamming them in when they solve nothing, doing unnecessary rewrites just to use the new hotness because it’s so cool and fun. Usually we’re the one trying to shove it down mgmt’s throat (or sneak it by them) rather than the reverse.
But not this time.
7/
@inthehands Yep. The fact that AI is being *forced* on people is maybe the biggest red flag of them all how terribly, horribly wrong things are in this bubble. Like you said, people and developers in particular, will flock to a new useful technology on their own, it's more that you might need to hold them back. Now, we're being extorted to use it or lose your bonuses, maybe even your job! It makes no effing sense whatsoever.
-
The trouble is, as Doctorow points out, that this vision makes AI a multi-billion dollar industry, not a multi-trillion dollar industry.
Even if you can claim that your ML / LLM thinger can reduce software bug rates or failure rates by 10x — which would be •wild• — demand for that is simply not going to fund data centers the size of Manhattan.
But make the claim of •speeding up• by 10x — an even wilder claim, but one some people are desperate to believe! — and all the money in the world will beat a path to your door.
5/
@inthehands I have another problem with this vision of the AI-assisted good centaur: It doesn't dilute the costs enough. Even accounting for the highly VC subsidized prices now, people expect that it will be fine to pay $600/month for Claude when price dumping ends, because it will save you more than $601 of work. But that would be only if everyone and their uncle is buying.
The "good kind of centaurs" would not be that many. The price might end up like 10k/m. And then it's just not proffitable
-
@thomholwerda
I refuse to believe that anyone who's actually used google translate before can seriously believe that it can replace human translation. -
The “efficiency” pitch I’m describing upthread isn’t really “go faster;” it feels more like “making good things doesn’t matter, what you cared all along about doesn’t really matter, and we don’t think •you• matter.
We always just wanted to built absolute shit, and you always tried to stop us. But now at long last we can.”
9/
@inthehands This is a big part of it, I think. But also, study after study says the efficiency gains aren't even real, once you factor in review and big fixing and describing the problem in enough precision for the machine, and downtime.
The management class has been trained to not do real work, but to have the appearance of work. LLM code has the appearance of hyper productivity. Whether it does or not is irrelevant to them.
-
Consider those two different versions of the radiologist’s role: one as a valued human augmented by a machine, doing a job they believe in better than they’ve ever done it — and the other as a cog in a corporate process whose job is to perpetually deal with the machine’s mistakes.
Consider the parallels in software development. All vibe coding and “agentic” stuff points to the second: developers as slop wranglers, as accountability sinks, as exhausted and expendable workers on a code assembly line.
3/
@inthehands The "code assembly line" makes me wonder where all that code is going. Is there a breakdown of all those developer hours by whom they're for? Internal financial services apps? The 100th rewrite of thegap.com? Insurance claim processing? I'm constantly amazed at how the quantity of code seems unrelated to the quantity of *real stuff going on*, especially social-value-producing real stuff like making solar panels and batteries. Maybe there's a bubble in the aggregate code factory?
-
@thomholwerda @janeishly @inthehands for sure. Seen similar thing in historic fields. Shared history is going be different in different languages.
