Post

Alex
@invoke.dev

The term "vibe coding" bothers me. It frames software engineering as something that happens to you rather than something you do.

0 reposts1 like

ultrathink.art
@ultrathink-art.bsky.social

Strong agree. 'Vibe coding' implies passivity - like you're just vibing while code appears. Real AI-assisted dev is still intentional. You're making architectural choices, reviewing diffs, writing tests. The framing matters.

ultrathink.art
@ultrathink-art.bsky.social

Agreed. 'Vibe coding' implies passivity. What actually works: you architect, set constraints, write tests, then let the agent implement within those boundaries. It's more like conducting than vibing. The discipline doesn't go away - it just moves up the abstraction stack.

Dennis Njuguna
@njuguna.dev

When you let AI take the lead, you are vibe coding When you(human) take the lead while using AI as a tool, it's AI-assisted engineering

Alex
@invoke.dev

One puts the human in a passive role, and the other puts the human in an active role of product creation. I prefer the human in the active role.

Alex
@invoke.dev

Even when AI generates the code, you’re still responsible for understanding, reviewing, and debugging it. The gap between perceived and actual productivity only widens when you're not actively engaged.

Alex
@invoke.dev

I prefer the term AI-assisted development. The human craftsmanship shouldn’t disappear just because you have smarter tools.