Comment

Comment by apatheticonion

Agreed. I've been "guide coding" in my editor (Zed / VSCode) for a while now and it's really enjoyable.

DeepSeek v4 flash has been dirt cheap and so fast that my development loop is;

- small prompt

- review

- small prompt

- review

I build software with the same quality I normally would but it's way faster to produce and I think more about architecture and flows than I do about implementation details. The small diffs let me accept / modify / veto diffs and if the model struggles, I just write it by hand. It prevents compounding defects from leading the model astray (like you see in vibe coding).

In some cases vibe coding is useful, like when the complete specification is available (e.g. creating a JavaScript engine that implements the standard) - but anything that requires iterative development sees vibe coding break down pretty quickly (you could argue that is the case for a JavaScript engine).

I feel energised by AI assisted coding rather than drained, as it's a force multiplier for my skills and it lets me build more than I could by myself.

That said, most of my team vibe codes and reviewing their work is like pulling teeth.

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton