Web developer for 15 years and still somehow finding new ways to break things. When I'm not in front of a code editor I'm deep in a game or a book. Excited to connect with builders here.
I ve been spending more time vibe coding recently, and I ve started to question something I initially took for granted. Most of the conversation around vibe coding is about speed. Like how quickly you can go from idea to prototype, or how fast you can iterate. And to be fair, that part is real. The barrier to building has clearly dropped.
But the more I use these tools, the more it feels like speed isn t the limiting factor anymore.
The real constraint seems to be taste.
what do you choose to build?
what do you keep vs discard?
what actually feels right vs just working ?
what is genuinely useful vs just impressive in a demo?
A couple weeks ago, Boris Cherny (the creator of Claude Code) shared a bunch of really useful tips on getting the most out of Claude Code. #1 at the top of the list: do more in parallel. He himself runs 10-15 Claude codes in parallel.
His advice and practice makes sense: coding agents give us the ability scale infinitely. At this point, the only real limiter is our own ability to manage all of these agents.
I might be missing some but I've been pretty much in love with @Lovable, @Cursor, @bolt.new and have been trying to use @Replit more and I honestly haven't touched @BASE44 too much but have heard good things. @chrismessina has nudged me to use @Windsurf for whenever I build another Raycast Extension! Currently I use: - @bolt.new / @Lovable - @Cursor - @Warp Curious what everyone thinks is the top one so far!
