Skip to content
suus
All insights

Yes, we vibe code.No, we don't ship vibe code.

AI-assisted development is the biggest change to how software gets built in a generation. The teams that win are not the ones that use it least. They are the ones with the strongest standards for what leaves the building.

SUUS5 min

There is a strange anxiety in the industry right now. Everyone uses AI to write code. Almost nobody wants to say so to a client. The phrase vibe coding has become shorthand for sloppy: accept whatever the model produces, run it, hope.

We use AI aggressively. Research synthesis, architecture options, component generation, migrations, test coverage, documentation. It is how a small team ships a flagship platform in weeks instead of quarters. Pretending otherwise would be dishonest and, frankly, uncompetitive.

The distinction that matters

The question is not whether AI wrote the first draft. The question is whether a senior engineer can explain every line that reached production, why it is there, what happens when it fails, and how it is tested. Vibe coding is when nobody can. AI-native engineering is when everyone involved can.

Speed and standards are not in tension here. The standards are what make the speed safe. Every pull request is reviewed by a person. Every system has tests that were read, not just generated. Every architecture decision is written down with its trade-offs. Security is designed, not prompted.

What changes, what does not

  • What compresses: research, exploration, first drafts, boilerplate, refactoring, test scaffolding, migrations.
  • What does not: understanding the domain, choosing the architecture, judging quality, owning security, deciding what the product should be.
  • What gets more important: taste, review, evaluation, and the ability to read code faster than it can be written.

The uncomfortable truth for traditional teams is that AI does not make good engineers redundant. It makes mediocre process redundant. Handoffs, waterfall phases, tickets that describe screens: all of that was compensating for how slow it was to try things. When trying things is cheap, the process can be rebuilt around learning.

Vibe coding is when nobody can explain the code. AI-native engineering is when everyone can.

So yes, we vibe code, in the sense that our first drafts are often written with a model. And no, we do not ship vibe code, in the sense that nothing reaches production without a person who owns it. Those two sentences are not a contradiction. They are the job.

Tell us what should exist.

Bring the brief you are not sure anyone can build.

Start a project