Plan mode, for me, is my opportunity to develop and understand my own plan. Sometimes, rarely, Claude demonstrates it misunderstood my intentions by writing a plan to address the wrong problem. But usually it's about me fleshing out the scope and boundary of the intended changes.
replyI find that faster than code first, ask questions later. But it takes more time up front.
Coding with plan mode is still vibe coding. No-one outside HN calls it things like "agentic engineering" or whatever. Everyone just says they are vibe coding regardless of how hands on they are.
replyWhether you use plan mode or not is orthogonal to whether or not you're vibe coding. "Vibe coding" means that you don't read or edit the code; you are running the software and iterating on vibes alone. That's the meaning since the original (and very recent!) coinage and hasn't changed.
replyIf you're reading and editing the code, you're not vibe coding. If you're not reading and editing the code, you're probably vibe coding even if you feel "hands on".
Doesn't matter and it has changed. To most devs vibe coding is when you let AI write your code.
reply