Why I build with Claude Code

A year ago "vibe coding" sounded like a shortcut for people who didn't want to learn to code. In practice, for me, it's the opposite: it's how I get to spend almost all of my time on the decisions that actually matter — what to build, how it should feel, what the edge cases are — instead of on boilerplate.

What the workflow actually looks like

1. Describe the feature or fix in plain language, with as much real context as I have (the actual error, the actual file, the actual constraint).
2. Let Claude Code draft the change.
3. Read every diff. This part doesn't get skipped, ever.
4. Run it, poke at the edge cases myself, and iterate.

The speed gain isn't "I don't write code anymore." It's that the loop between idea and working code is minutes instead of hours, so I can afford to try more ideas and throw more of them away.

Why I'm writing about it here

I'm building products like Invomly this way, in public, partly to keep myself honest about what actually works and what's just hype. More posts coming as I ship.