DUDES / VIBE-CODING

Vibe coding. With grown-up supervision.

Our definition: using AI aggressively enough that writing code stops being the bottleneck. Engineering judgment stays in the loop.

01

A conversation becomes working software

You describe the intended behavior, an AI model proposes changes, and you iterate. This is useful for quickly exploring an idea. It is not, on its own, a release process.

02

Prototype versus production

A prototype asks whether an idea is useful. Production software also needs reliable authentication, correct permissions, failure handling, tests, monitoring and a recovery plan. We make that boundary explicit.

03

Never confuse confidence with correctness

Generated code can invent APIs, overlook requirements or pass weak tests. We check primary documentation, run the system and review critical behavior independently.

04

The human still owns it

We choose the scope, architecture and tradeoffs. Models write and review small changes. Tests and human approval determine what gets deployed.

Got a “could you build…”?

Tell us what to build