6 months of vibe coding, here's what actually stuck
by•
Stack settled into this after breaking it a few times:
Cursor for IDE work. Claude Code for longer agentic runs when I trust the spec. Codex for boring tickets while I'm in meetings. v0 when a client needs a UI mock in 10 minutes.
The thing that actually changed how I use all of it: stopped treating them as interchangeable and just routing by task type. Refactors go to Cursor. Full feature from a spec goes to Claude Code. Tedious backlog stuff goes to Codex.
Still haven't figured out when to stop letting the agent run and just write it myself. That one's still on me.
What's your current stack?
23 views
Replies
As someone who prefers a lighter, non-technical approach, seeing how you break down different tools for different jobs is super interesting. Finding a workflow that actually sticks and gives you your time back is everything.
@grimloaf yeah, specialised tools are essential for specific tasks