Vibe coding

The loop is prompt, run, look, correct. You hold the intent and the judgement about whether the result is right; the model handles most of the typing. It is fast for greenfield work, prototypes and internal tools, where being roughly right today beats being perfect next month.

It falls apart without review. Generated code can be plausible and wrong, dependencies drift, and a codebase assembled by prompts with no architecture becomes hard to change. The teams getting real value pair it with the ordinary disciplines: version control, tests on anything that touches money or data, and a human who can read what shipped.

For client work we treat it as an accelerator inside a normal build, not a delivery method. It shortens the distance from idea to a working MVP you can put in front of users, then the parts that survive get built properly.