Hi everyone. I’m relatively new here and mostly lurking, but I had to ask about this.
I see a lot of posts here about using Cursor for complex refactors or generating whole features, which is amazing. But for me, coming from a background of migrating old on-prem systems to Azure, I find myself using Cursor differently.
Most of my day is spent staring at legacy stored procedures or figuring out how to untangle a monolith for a lift-and-shift. I get stuck *constantly*. My usual workflow now is to open a chat in Cursor, paste a chunk of confusing code or describe a gnarly dependency problem, and just… talk it out. I don’t even always run the code it suggests. Just the act of explaining the problem to Cursor and seeing its breakdown often makes the solution click in my head. It’s like a super-powered rubber duck that sometimes whispers hints.
Does anyone else use it primarily this way? Especially when dealing with legacy migration work, where the path forward isn’t always clear and you need to think out loud? I worry sometimes I’m underutilizing it, but this method has saved my sanity on more than one Azure migration project 😅
One step at a time