Who uses LLMs? - Neon Vagabond

7 min read Original article ↗

There's this common argument that only those who are bad at coding, or don't care about the craft of it, use AI to code. I think this is pretty clearly false. Let's look at a list, shall we?

More iffy ones:

This refutes a few arguments that I see a lot of people make, especially in places like lobste.rs:

  • "Only bad coders use AI": This is dead. You cannot argue this while Salvatore Sanfilippo is 100% agenticly coding improvements to Redis in low level C code and Guido van Rossum uses Copilot daily.
  • "It's all Clever Hans": The detailed, technical write-ups (Sanfilippo's C conversion, Klabnik's language prototype, Willison's extensive documentation) show these developers understand and direct the output. It is extremely unlikely they'd be fooled by an AI bumbling about doing fully random things until it randomly gets the right answer and they accept it. These systems are steerable. They may not be precise, but they are accurate.
  • "Gambling effect only": Occasional wins don't sustain multi-year adoption across entire workflows. Ronacher's "90% AI-written code" and Klabnik's "most of my code with Claude" show sustained, iterative use, making it seriously hard to claim that it's just jackpot chasing.
  • "Disingenuous hype": Some have financial incentives (Karpathy, Norvig), but most don't. Sanfilippo, Willison, Ronacher, and van Rossum have nothing to sell. More, their views remain credible because they retain critical nuance (e.g., Lattner's craftsmanship warning).
  • "It doesn't make you more productive": I think it's hard to argue that, for instance, Steve Klabnik could've created an entire compiled, low level systems language prototype in about two weeks without agentic help. He's good, but not that good. No one is.

The point isn't to say that you have to use AI, or that it has no downsides or risks, or no reasons to be skeptical, but more to say that at this point it's just not sane or feasible to claim that it isn't useful for anyone. I think it's at the stage now where, like many other development tools — IDEs, debuggers, dynamic vs static typing, high level vs low level languages, OOP vs functional, etc — some people clearly really do get benefits out of them, there's there there, even if it might not work for others; and that it might be valid to say "skill issue" to the people who can't get value out of them.