Every time I see a vibe coder say something along the lines of "if you haven't used these tools over the past five minutes, you don't know what they're capable of, because everything's different now!" I get a little bit perplexed.

You do know that we can see the output without using it ourselves, right? Some of us are still reviewing pull requests and reading through code repositories, y’know?

en

Replying to @⁨baldur@toot.cafe⁩

@baldur This is precisely why I revived KScope for Qt6 after years of it languishing after the Qt4 port bit-rotted. The tool exists to aid human understanding. It is not relevant to any so-called "agentic development paradigm", nor is it intended to be. I continue to be more productive by rejecting LLM driven tools.

It is also 3-clause BSD licensed except for the forward port of KFileTreeView, which is LGPL2. There is no requirement for me to release source code which might be subject to IP theft via "training". A prototype Linux AppImage exists.

Replying to @⁨chapter1@mastodon.social⁩

@chapter1 @baldur I took a pair programming class a couple of weeks ago, and one of the exercises was for two humans to pair with copilot, which I hadn't used before. It was striking how quickly it felt that actually reviewing the code was an unnecessary bottleneck and I was holding things up by spending a couple of minutes reviewing what had been generated in a couple of seconds. I felt like I couldn't justify making the other person wait unless there was an obvious mistake.

Replying to @⁨kinnison@flarn.net⁩

@kinnison @baldur also suffering from this. And I do not know solution. E. g. customer needs feature by tomorrow. I can do it by tomorrow with agents accepting “eagle eye review” and customer happy. Or I can deep dive, understand things, use agents, have clean code and no customer.

As a passionate engineer I HATE it. Only ~10% of tasks I can do maintaining decent output quality.

Sadly, it’s not even about engineering. It’s unavoidable outcome of capitalism+LLMs.

Replying to @⁨petrikas@mastodon.online⁩

@petrikas @baldur

I found myself agreeing, but then I had to stop me, because I think the difference is in the consequences and the cost.

Because in the case of LLMs, it's at worst just a rather cheap waste of time, which is bad, but (in moderate doses) fine, if that means one can end up verdict that is not just based on expectation but actual data collected in an open trial.

Of course, the people referenced here do not mean in that way. They mean it in a dismissive way. But just because they're weak, doesn't mean that we should also counter in weak dismissive ways.

Especially given that an extensive list of all the bullshit one has personally seen the clanker do is an excellent tool to hit tech bros over the head with.

Replying to @⁨petrikas@mastodon.online⁩

@petrikas @baldur

Look man, I'm just saying that to win over people that aren't already aligned, one needs these stacks of empirical data. And especially empirical data that matters to them.

I can also just not reply if that is more wanted, but it showed up in my timeline and I thought there would be some actual interest in doing something about the state of the world being bad.

Replying to @⁨Hypfer@social.tchncs.de⁩

@petrikas @baldur

I mean look at these guys:

__

jamesponddotco 4 minutes ago | root | parent | next [–]

I gave Claude several pieces of writing from myself, from notes to code comments to iMessage messages with my wife[1], and asked it to write skills that match my voice. I also incorporated the humanizer[2] skill into it.

Worked like a charm. This is the prompt I used[3] to write a version for the company I own with my wife, if it helps anyone. The personal version, which lead to the `jamenizer` skill, is very similar, but has some personal details in it.

___

I doubt one can reach them by talking about.. idk the environment or whatever.
If they are even real people at all and not just ghoulish caricatures.

Anyway, I'll leave you alone now

Replying to @⁨petrikas@mastodon.online⁩

@petrikas i credit the fact i haven't been normalizing it in my brain with direct exposure for why im still able to spot the glaring, obvious, intern-level errors it makes when asked to review colleagues' PRs (which is only sometimes, as i become more and more grumpy) that they oftentimes haven't even read themselves

yes, i can quite clearly see what it actually does

@baldur

Replying to @⁨petrikas@mastodon.online⁩

@petrikas @baldur

Been a trope in the AI booster circle for a while.

If LLM coding assistants aren't working for you, you have to be doing it wrong, you must be using an outdated model or you aren't prompting it correctly.

Its all your fault!

And just you wait in 1, 3 or 6 months from now these things will be soooo good it'll be transcendental

From Thomas Ptacek's article "My AI Skeptic Friends Are All Nuts", Published June 2025

"First, we need to get on the same page. If you were trying and failing to use an LLM for code 6 months ago †, you’re not doing what most serious LLM-assisted coders are doing."

Replying to @⁨petrikas@mastodon.online⁩

@petrikas @baldur I've heard this dressed in the scientific method:
"You know, as scientists we need to verify stuff"

But I'm not seeing anyone volunteering to peer review the physiological effects of cyanide through personal verification.

It's all distraction, no amount of evidence is ever going to be enough. Even if you go there and use it, if you don't like, you're just doing it wrong, using the wrong model, not using enough etc etc etc etc

Replying to @⁨baldur@toot.cafe⁩

@baldur What's honestly even worse is juniors using AI making such statements towards experienced devs and countering a:

"I have used it, but I get better results using it as a helper for mundane tasks"

with a simple

"Well, then you just don't know how to use it - my code is better letting it do the job!"

Congratulations; You just highlighted that you didn't learn anything and why people try to replace you with it.

Replying to @⁨baldur@toot.cafe⁩

@baldur Now that we’re a bit into this hype cycle it’s also fun to see that the same people who said something along these lines a year ago are now saying the same thing but just with an updated timeline.

”You don’t get it, everything changed in March 2026, before that I would have agreed everything from LLM’s were shit.”

…said by the same person who praised the progress in November 2025 ”since February 2025” or something 🤷🏻‍♂️

@HaTetsu

Replying to @⁨baldur@toot.cafe⁩

@baldur
On the bigger scale, the claude-reversed engineered AutoCAD and such crafty tools do not make me forego all security, attestation and certification guardrails around large scale construction projects.

If there's technical debt in there (sure there is, it's in human engineered software too, you know) someone will find it. Either it's you, early on, or the bridge comes down in chunks and injures many people who relied on it.

I get the excitement and enablement. But am I going blindly forward? No. :)

Replying to @⁨baldur@toot.cafe⁩

@baldur This happened at work. AI Hyped Coworker: "They set the agenda for the workshop!"
Others: "... yes, isn't that normal?"
AI Hyped Coworker: "The workshop is 2 weeks from now!"
Others "...oki?"
AI Hyped Coworker: "This agenda is going to be completely outdated two weeks from now!!!"

I guess, based on the 5 minute rule, by the time a workshop is over, it will already be outdated, and yet if we don't attend, we will be "left behind".

Can't they just leave me behind.

Please...

Replying to @⁨baldur@toot.cafe⁩

@baldur Aye. There have been meaningful changes, but the way I put it to people is: the November 2025/Opus 4.5 shift was from “the stuff they spit out doesn’t usually work” to “the stuff they spit out usually works… but it still isn’t *good*”.

It’s quite plausible to me that that change has *worsened* the quality of code coming across the line, because “works” is enough for some folks to say “ship it”. When it just didn’t work, you *had* to actually touch it, which may have helped… somewhat.

Replying to @⁨chriskrycho@mastodon.social⁩

@baldur I would say (and in the past *did* say) that this was just a new version of the classic automation paradox, but the *classic* automation paradox involves higher performance than the baseline under normal circumstances. There are axes on which that is sometimes true here—adversarial review, e.g., surprisingly often does better than manual code review given existing code review practices (That’s its own topic of broken engineering practices, of course!) — but it’s not remotely all of them.

Replying to @⁨chriskrycho@mastodon.social⁩

@baldur So it’s often ending up being a *worse* version of the automation paradox: the direct outcomes being anywhere from somewhat to significantly worse and the second-order effect still being deskilling. We tolerate the cost of the automation paradox in aircraft autopilot and similar systems because it significantly improves average outcomes. It doesn’t seem to be doing that here.

Replying to @⁨chriskrycho@mastodon.social⁩

@chriskrycho It's interesting that the human factors paper that originated the automation paradox (en.wikipedia.org/wiki/Ironies_) as well as much of the research that followed didn't focus on the idea of higher performance than baseline. The paradox kicks in as soon as the output is good enough to switch the human participant out of "participation" mode and into "monitoring" which is also more exhausting as it requires heightened vigilance.

en.wikipedia.org/wiki/Ironies_of_Automation

Replying to @⁨argv_minus_one@mastodon.sdf.org⁩

@baldur

And, well, mastodon.sdf.org/@argv_minus_o bots are shockingly negligent. Ask them a question about programming, and instead of giving you one straight answer, they give you a dozen wild guesses and expect *you* to figure out which of them—if any—is correct.

I used to be better off with pre-2024 search engines and Stack Overflow, but now both of those things are full of bot-generated spam!

These bots aren't helpful for programmers. These bots are an unmitigated disaster for programmers.

Replying to @⁨argv_minus_one@mastodon.sdf.org⁩

@baldur

And before anybody says “lol get a real model”, the guy I was talking to in that thread used a real model, and it epically failed too. mastodon.sdf.org/@argv_minus_o

Bots aren't just expensive and proprietary and full of ethical issues. They also don't work as advertised. They're great at generating generic marketing copy and whatnot, but as soon as the bulls**t stops and the actual engineering starts, they fall apart.

Replying to @⁨argv_minus_one@mastodon.sdf.org⁩

@argv_minus_one
@baldur
In my support role, I get support requests "assisted by", and sometimes even fully "agentic" and they are an absolute nightmare to work on.

Issues that aren't real, applied "fixes" that break things, generated fake "sources" for the prior fix or comments.

The back and forth is like communicating while both parties are suffering a watershed stroke.

Replying to @⁨baldur@toot.cafe⁩

@baldur The slop boosters always leave out a crucial part of the phrase because we absolutely know what sloptools are capable of (slop), what they mean by "you don't know what they're capable of" is "you don't know [how smart they make me feel as I accomplish nothing while offloading the real work to other people who have to review my slop]!"

Replying to @⁨baldur@toot.cafe⁩

@baldur They are also so occupied with trying to sell courses and learning material to the others, who they think are simply misinformed about how great this new technology is.

And it's always business school graduates.

Believe me, I've tried this stuff and I spent more time refining prompts into the night than I ever would have spent checking that ticket off myself.

And mind you — it feels amazing and you get instant feedback but the results are overcooked for a lack of a better word.

Replying to @⁨baldur@toot.cafe⁩

@baldur Did you see the Reply Guy lecturing Eugen Rochko (!) for having opinions about vibe coding, despite not having used chatbots himself? Basically everyone made the same point: you don't have to have "experienced" using the tech to assess the quality of its outputs.

Indeed, the elevation of subjectivity in this context looks very much like a form of "AI" psychosis. Of course Eugen is more than qualified to tell if the code is "spaghetti" (as he put it). 🤷🏻‍♂️

Replying to @⁨baldur@toot.cafe⁩

@baldur The every-five-minutes argument coupled with the “embrace now or you’ll be left behind” sentiment obliterate each other in an explosion of pure bullshit for me every time I see them in the same airspace.

Like, if the tools are constantly changing, and there’s close to infinite incentive for the providers to make them as easy as possible to onboard onto (and develop a dependency upon), what possible motivation is there for one to _not_ put off adopting them? Explain with math, if you prefer.