Skip to content

note

Vibecoding Isn’t a Dirty Word

July 3, 2026 · 1 min read

Building real, team-used tools with AI — and why the craft moved from typing to judgment.

AI EngineeringDeveloper ToolsCraft

“Vibecoded” is usually said as an insult — shipped fast, understood never. I build real infrastructure that way and I'd defend it. The dashboard 20 developers open every day, the CLI that runs our builds, the notification bot — all of them were built by pairing with agents at roughly 3x the speed I'd manage by hand. What changed isn't the standard; it's where the work lives. The agent writes the draft. I decide what good looks like: what the architecture should be, which edge cases matter, where to say no. The trap isn't using AI — it's shipping things you can't reason about. The counter is boring and old-fashioned: read the diff, own the design, ship the smallest useful thing. I learned that the expensive way — I once over-built AI features into a tool nobody used, because the team already had their own agents. Smaller, faster, validated. The vibes are fine; the judgment is the job.