Josh|Resonant
December 11, 2025
Pivot, Adjust and Overcome
Just a quick heads up, this update is going to be a little different from my usual ones.
It feels like it’s been forever since I’ve actually been able to sit down at my computer. Life has been pretty chaotic lately between holding down the FedEx contract and basically playing Santa. On top of that, one of the contractors at our terminal has been struggling with their routes, so it’s been all hands on deck to cover theirs while still running my own. None of that really matters here, but it’s wild how just a few days back on a truck can make a week and a half feel like an eternity.
Anyway, onto the Resonant side of things.
It recently came to my attention that Replit is removing their assistant entirely. This was the main tool I relied on Replit for: cheap prompting, stored prompt history, solid version control, super clear diff comparisons, and honestly just a really fast, transparent workflow. Instead, they’re rolling out multiple “agents” with varying levels of autonomy and charging extra for a new “Fast” mode. Maybe I’ll like the changes, maybe not, but I’ve never been a fan of forcing users to accept major shifts while removing the features the community heavily relies on. It takes away transparency, and honestly, I don’t love the idea of settling into a new workflow only for Replit to shake things up again down the road.
So… what’s next?
Right now, I’m researching new environments to migrate into. Definitely not going with Bolt or Lovable. I’ve checked them out a few times and they just don’t seem to fit forone reason or another. Cursor paired with Claude, and then Vercel + Supabase for deployment and backend, seems like the direction I’m leaning. Kiro also looks interesting, but the bigger picture here is finding a setup that feels stable, transparent, and long-term.
Replit had become my everything of how I build. When they suddenly pivot, it impacted Resonant more than anything. I realized to a very large extent that I did not have as much control over my workflow as I felt I had. Well... pivot, adjust and overcome. Get to learn some new tricks and hopefully understand my codebase and the way it works a bit more.
My goal now is to land somewhere dependable so I can keep development smooth and predictable moving forward. Once I get everything migrated and settled, I’ll be right back to focusing on platform updates.
Thanks for sticking with me through the chaos. Resonant means a lot to me, and I genuinely appreciate any feedback you guys may have on how to move forward.