A quick note on my own toolchain, since people ask. I don't use one AI coding tool I use three, a...A quick note on my own toolchain, since people ask. I don't use one AI coding tool I use three, a...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
A quick note on my own toolchain, since people ask.
I don't use one AI coding tool I use three, and which one I reach for depends entirely on the job in front of me.
For fast inline edits and everyday refactoring, I stay in Cursor. For anything that needs to plan across multiple files, hold context through a long multi-step task, or touch infrastructure I don't want to babysit line-by-line, I switch to Claude Code. And on projects still fully locked into GitHub's ecosystem, Copilot stays in the mix because ripping it out isn't worth the friction.
This isn't indecision it's the same principle behind picking the right framework for a given stack: use the tool built for the job, not the one you're most loyal to.
Recent industry data backs this up: the average experienced developer is now running more than two AI coding tools side by side, not because they can't decide, but because no single tool does everything well yet.
If you're building something and your dev's toolchain looks "messy" from the outside, this is usually why. Messy on the surface, deliberate underneath.
Post image
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started