Post

Simon Willison
@simonwillison.net

Vibe coding is irresponsibly building software through dice rolls, not caring what code is produced What about when engineers at the top of their game use AI tools responsibly to accelerate their work? I propose "vibe engineering"! simonwillison.net/2025/Oct/7/v...

simonwillison.netVibe engineeringI feel like vibe coding is pretty well established now as covering the fast, loose and irresponsible way of building software with AI—entirely prompt-driven, and with no attention paid to …
Chris Anderson
@j-chris.bsky.social

Vibecoding is the ability to create software that would’ve been too expensive to create in the past. It opens up a new part of the demand curve for custom software. It’s a mistake to think that it replaces engineering.

Simon Willison
@simonwillison.net

Right - vibe coding is its own thing, great for prototyping and to help non-programmers start exploring what code can do for them But there's also a separate new thing, which is when experienced engineers use sophisticated AI-driven techniques to dramatically accelerate their own work

0 reposts5 likes

Chris Anderson
@j-chris.bsky.social

I’m currently exploring the idea that with the right stack, you can empower vibe coders to work safely and create low maintenance useful tools. This means a constrained environment not just throw everything in a container and hope for the best.

Simon Willison
@simonwillison.net

I'm a huge fan of Claude Artifacts (and ChatGPT's clone of that which they call "Canvas") for that - it's very hard to shoot yourself in the foot with those Problem is they don't have persistence, which limits both the damage but also the utility you can create with them!

Chris Anderson
@j-chris.bsky.social

That’s exactly where @vibes.diy fits in. Artifact levels of complexity, with the persistence and connectivity to make it useful. (Inspired by the CouchApp model of self-contained portable code, but aiming for ease of use for a general audience.)