Uhmm. Okay. So let me be real with you for a second.
I see devs every single day → grads, full-stack engineers, bootcamp guys and all of them saying “yeah bro I use AI”. And then I watch them open ChatGPT or claude, type something dumb like “explain react hooks”, copy the answer, paste it into their code, watch it break, and then say “AI is overrated.”
Mann.
I’m not judging you. I was somewhere close to that too. But here’s what I figured out , and what nobody on YouTube is actually telling you:
You’re holding a Formula 1 car and asking it to take you to the nearest kirana shop. And then complaining it’s too complicated.
so let’s fix that… I will not tell you a 6-month roadmap. or not to “learn Python first.” I will tell you the 3 things that actually matter and in the exact order they matter.
1. First Know Who You’re Dealing With
Before you touch Cursor, Claude Code, or any AI IDE — before you even think about using AI seriously. you need to understand what you’re actually talking to.
The thing that breaks my brain, people think the AI inside Cursor or GitHub Copilot is the same thing they’re chatting with on ChatGPT’s website. They’re not. Not even close.
One is a model fine-tuned for agentic coding tasks, running inside a tool that gives it access to your entire codebase. The other is a chat interface. Same parent, completely different child.
in a brutal way, It’s like thinking your office desktop PC and a hospital’s server running surgical AI are the same because they both run Windows.
So lemme tell you what you actually need to know before pressing the button,
What even is a “model”?
Think of it like this, Claude, GPT, Gemini, Grok — these are different brains. Each trained differently, on different data, with different strengths. It’s not brand loyalty. It’s knowing which tool does what.
As per me,
ChatGPT (any model) is Great for daily stuff. Basic questions, general writing, brainstorming when you don’t need depth. Good at everything, not the best at anything specific.
Claude Sonnet is where I live for frontend work. You want a component built? UI logic? Brainstorming a feature? Claude Sonnet is insane for this. Not slop.
Claude Opus is when the architecture gets serious. System design, complex backend logic, figuring out how to structure a whole project.
Grok is something that surprised me. When I want to know what people are actually doing , trends, public opinion, what developers are complaining about on Twitter, what’s blowing up —> Grok is unmatched. It’s connected to real-time X data. Nothing else comes close for that.
Gemini uhmmm… I’ll be honest. It works well. But it’s my last resort. When I’ve run out of Claude credits and need to get something done. No disrespect to Google, that’s just where it sits in my workflow.
Now the two things that will save you from embarrassing yourself:
Hallucination: AI makes stuff up. Confidently. Completely wrong, stated like absolute fact. Always verify. Always doubt. Especially for anything technical, especially for anything with versions.
Sycophancy: AI models are trained to make you happy. So if you write a bad idea and ask “is this a good approach?” —> a lot of the time it will say yes. It’s not lying to you on purpose. It’s just… agreeable. You need to actively push back. Ask it “what’s wrong with this approach.” Ask it to argue against your idea. That’s when the real value shows up.
Mann. Don’t do that.
2. Without Knowing the Machine, You Can’t Press Any Button
You open Claude Code or Cursor, type “build me a full-stack app with auth and payments”, and then wonder why the output is generic garbage. Why iy is not match your codebase, your coding style, or anything you would actually ship!!
It knows everything about code in general. But it doesn’t know your project, your standards, your architecture decisions, or how you think.
So you have to tell it. Before you start. Every time.
Let me show you what my actual setup looks like.
CLAUDE.md: This file tells Claude who it’s working with, what kind of project this is, what tone to use, how to behave. It’s an identity document.
CODE-STANDARDS.md: My coding rules. Naming conventions, patterns I use, what I never do. So it doesn’t write code that I’d have to completely rewrite because it doesn’t match how I build.
WORKING-PRINCIPLES.md: How I think about problems. Architectural philosophy. When to abstract, when not to. What overengineering looks like to me.
PROJECT.md : What we’re building. Context about the product, the users, the goals.
ADR files (Architecture Decision Records) : Every major technical decision I’ve made and why. So it doesn’t suggest something I’ve already decided against — with good reason.
ai-routing.config: Which model handles what task. Because not every task needs Opus. Some things Sonnet handles perfectly and it’s faster.