How to use AI to fix bugs and more with Cursor

View profile for Shrey Sharma

SDE @ Addverb | Full Stack Development | High-Throughput Systems & Event-Driven Microservices | Java, Python, Angular

👀 Ever asked AI to “fix a bug”… and ended up with 10 extra surprises you never asked for? That was my Saturday morning with Cursor. Lesson learned: The prompt is the spec. Chat mode = architect’s desk, Agent mode = builder’s workshop. ⏱️ Benefits: • Less time thinking & implementing • More flexibility in code • AI output isn’t a black box anymore • Your wisdom stays in the decision-making • Easier to modify changes & brainstorm 👉 Do you plan first, write tight prompts, or just throw ideas and debug later? #CodeWithAI #DevLife #WeekendDev #SoftwareEngineering #AItools

  • No alternative text description for this image
Vedanta Patil

GenAI Engineer @Sarvam AI

3w

Very true! Learned it the hard way :)

Karan Samyal

Software Developer | Exploring New Frontiers in Software Development | Leveraging Neural Space for Innovation | Ulip 2.0 & SIH 2023 Winner

3w

New dive into vibe coding

Shaurya Bansal

RCM | LSE Econ '25 | Hindu Econ '23 | Ex CCI | Ex TATA Global Intern | Ronald Coase Fellow | Don Lavoie Fellow | Ex JSW

3w

Fully agreed, though with my skills I can barely vibe code :D

🚀 Adam Pavlát

Repeat until done { Design, Create, Enjoy, Improve }

3w

Great point about prompts being the spec, I've found that adding some structure helps me avoid surprises. Using Todo2 in Cursor as a mini kanban with MCP-driven tasks, research, and comments keeps things clear and iterative. Do you find certain prompts benefit more from this setup? https://todo2.pro

Rohit Prashant

Student at University of Waterloo

3w

This is so true. I just throw ideas and debug it all later. Maybe not the best approach

Like
Reply
See more comments

To view or add a comment, sign in

Explore content categories