Everyone's obsessing over Cursor right now. "It writes code for you!" "It's the future of development!" "You're falling behind if you're not using it!"
Stop. Just stop.
I made a video breaking down why the Cursor hype is fundamentally misguided — and why most people using it are making their code worse, not better.
The Real Problem
The Cursor hype isn't about better tools. It's about developers trying to skip the hard part: thinking.
When you let an AI generate code without understanding what it's doing, you're not becoming more productive. You're becoming a rubber stamp. You're turning your IDE into a Jira ticket and yourself into an approver.
What Actually Matters
Real code ownership means:
- Understanding every line you ship to production
- Making deliberate decisions about architecture, not just accepting what AI suggests
- Knowing when to say no to generated code that "works" but isn't right
The best developers I know use AI as a research tool, not a code generator. They ask questions, explore alternatives, then write the code themselves with full understanding.
The Uncomfortable Truth
If you need an AI to write your code, you probably shouldn't be writing that code yet. Not because you're bad at programming — but because the learning happens in the struggle.
Skip the struggle, skip the growth.
Watch the Full Breakdown
I go deeper on this in my latest video:
The short version: Cursor is a tool. Tools are neutral. But the culture around Cursor — the hype, the FOMO, the "you must use AI or die" energy — that's the problem.
What Do You Think?
Am I wrong here? Is AI-assisted coding actually making us better developers? Or are we just getting really good at generating code we don't understand?
Drop your take in the comments. I genuinely want to hear both sides.
Follow ERR.SYS for more honest takes on the tools and trends shaping software development.
Top comments (0)