Back to Devoured - August 24, 2026
DEVOURED
Vibe Coding and Quality

Vibe Coding and Quality

Design Ilyabirman.net
Ilya Birman argues that achieving perfection in software is now more accessible through iterative AI-assisted development than through traditional human-led programming.
What: The author reports that using AI to build a Mac app allowed for rapid, obsessive iteration on micro-details that would be impractical to demand from a human developer or implement manually.
Why it matters: This shift suggests that 'vibe coding'—iterative prompting—may redefine development by lowering the threshold for refining non-critical software UX.
Deep dive
  • Vibe coding: A development process where a developer guides an AI model to generate, iterate, and refine software behavior through natural language prompts rather than writing code manually.
  • Quality barriers: The author posits that human developers often lack the time or patience to polish minor UI imperfections that an AI can handle on command.
  • Iteration efficiency: The ability to instantly rewrite major components allows for an experimental approach to UX that is impossible in traditional codebases.
  • Maintenance: High-quality software still requires understanding of abstractions and state management, but the implementation speed is accelerated.
  • Collaborative friction: The author highlights that AI eliminates the interpersonal friction of requesting repetitive, minor changes from a human team member.
Decoder
  • Vibe coding: The practice of directing AI models to build software through natural language conversation and iteration, prioritizing subjective quality and speed over manual coding.
Original article

Vibe coding and quality

When you hear that some app was “vibe coded”, how much quality do you expect?

As recently as last year, vibe coding seemed like nothing more than a toy to me. Sure, it was cool that you could tell a computer to build something and it would sort of build it. But the result would be held together with duct tape and only good enough as a prototype. To make something high-quality and reliable, you need to keep the entire codebase under control. You can use AI to write it, but you need to understand what abstractions are being used, how things are connected, how different events are handled, how storage is arranged, and so on.

But now I am developing a Mac app, and I am coming to the opposite conclusion. I started making the app because none of the existing alternatives written by actual Mac programmers satisfied me: the quality was too low. Surprisingly, even the app that Codex wrote for me on the first day (after a week of leisurely conversations to produce the initial spec) already works faster and nicer than all the alternatives. And I can see plenty of directions for improvement.

Now it seems to me that the level of quality I look for is simply unattainable through conventional programming. If I could program something like this myself, I would not have the patience to polish every last detail. If I had an experienced Mac programmer next to me, they would have even less patience for my complaints about imperfections that are visible only when reviewing a screencast frame by frame.

In my experience, most programmers simply do not notice many such details, or do not consider them important. But even if I happened to find someone who did notice and care, I would hesitate to ask them to try rewriting the whole thing in a completely different way just to see whether it might feel a tiny bit better — they are a real human, after all! And the rare programmers with equally high standards of quality are unlikely to be sitting around waiting for me to direct them. They have plenty of ideas of their own.

So now I think that high quality is achievable only through vibe coding.

Explore all 66 articles in today's digest

Fresh dev news, AI-digested daily. Never miss a trend at devoured.fyi