A software developer explains how AI agents help automate tedious coding tasks, and addresses concerns like hallucinations, job losses, mediocre code, and more
Tech execs are mandating LLM adoption. That's bad strategy. But I get where they're coming from.
FlyThomas Ptacek
Context & Ripple Effects
This is an early practitioner-level counterweight to the push for organization-wide LLM use: the author treats automation of repetitive engineering work as useful while rejecting mandates as a sound deployment strategy. That distinction matters as later coverage shows both productivity anxiety around coding agents and developers describing a shift toward more architectural work.
The stakes extend beyond developer preference because AI adoption has also been invoked in workplace decisions: workers at major tech companies described managers using AI to intensify work and justify cuts. The article centers the unresolved operational question of how to gain automation benefits without treating model output as automatically reliable or substitutable for engineering judgment.
First-order effects
Developers can use agents for tedious tasks, but must retain review responsibility where hallucinations or mediocre output could enter the codebase.
Executives mandating LLM use face a clearer implementation trade-off: adoption targets alone do not address code quality, reliability, or workforce concerns.
Second-order effects
Engineering teams are pushed toward workflows that distinguish low-risk automation from work requiring human validation, rather than measuring success solely by whether an LLM was used.
If this pattern persists, AI coding will be organized less as a blanket tool rollout and more around governed, task-specific agent use with human accountability for production outcomes.
The deeper shift is from judging developers by direct code production toward judging teams by their ability to specify, review, and safely integrate machine-generated work; whether that improves jobs or compresses them depends on management choices.
The trend: AI coding is moving from experimentation toward workplace infrastructure, making governance, review, and labor strategy as consequential as raw automation capability.
Nice take. — As someone who is/was an AI skeptic, I do think think these systems are useful, just like a text editor is useful for writing code, a tool that combined with judgement and effort. It is not a solution all by itself. — It will completely destroy a lot of develope…
You know it's a grift because the hard sell isn't working, so going after people on a personal level is the next move fly.io/blog/youre-a... If AI/LLMs were actually good, this sort of article would never show up. — The URL of this “article” is a good tell, too.
This stuff is frustrating because there are factual assertions here about the state of AI assistance with coding (it's at an interesting, even useful, state), but it's so wrapped in strawmen and bad-faith dismissal that it's lost. fly.io/blog/youre-a... Again, we need better AI c…
“Professional software developers are in the business of solving practical problems for people with code. We are not, in our day jobs, artisans.” — Put another way, a lot of programmers see stuff like Cursor as a tool. — fly.io/blog/youre-a...
A lot of folks struggle to explain why coders generally seem less perturbed about LLMs than most other audiences. — This piece, from a respected programmer and well-known Hacker News regular, does a better job explaining it than most other things I've read. — fly.io/blog/your…
Risky post! — (This is great, fun to read and the frustrated tone throughout really does capture how it feels sometimes to be an experienced programmer trying to argue that “LLMs are actually really useful” in many corners of the internet) [embedded post]
top quote is from fly.io/blog/youre-a... and it's a good reasonable article from a smart person i respect, and honestly i wish i had a little more of the enthusiasm for ai
timely example of the sort of writing about AI I find infuriating: speaking only in broad terms, offering no concrete examples of what using it well looks like, and berating you as an idiot arguing in bad faith if you disagree with any of it fly.io/blog/youre-a...
At this point most of the programmers I respect the most are AI positive and finding a lot of value in it. And of course understanding the limits, as with any good tool. @tqbf, Kenton Varda, @antirez, and many more. This post is mostly perfect: https://fly.io/...
I've mentioned that some of the most talented technologists I know are saying LLMs fundamentally change craft of engineering; here's a recently published example from @tqbf. https://fly.io/...