Coding with LLMs? Flip the Script
If you're not enjoying coding with LLMs in 2025, flip the script.
If You're Not Enjoying Coding with LLMs in 2025, You're Using Them Wrong
The Common Mismatch
- Junior developers try to vibe code their way to expertise — skipping the fundamentals, failing to truly learn, and stalling on real bugs.
- Senior engineers expect a peer, but end up with a cookie-cutter typing assistant.
Flip the Script
Where you're an expert, treat the LLM like a rookie. Where you're a rookie, treat it like an expert.
For Senior Engineers
Think about it: as a senior engineer, you rarely agree with someone’s hot take on architecture or design patterns. Why would you expect to love a bunch of weights’ opinion on it?
Your style has been battle-tested and delivered results. What you need is a fast, eager junior who can crank out features while you set the direction.
Your role: Write clear docs, set coding standards, and delegate execution to your LLM agents.
For Junior Developers (or When Learning Something New)
If you’re a junior developer — or picking up a new framework — treat the LLM like your company’s staff engineer.
You wouldn’t dump an entire feature on them to code for you. But you’d absolutely:
- Ask for advice
- Get feedback
- Request code reviews
The best part? You can ask as many “dumb” questions as you want — and never get a smirk in return.
Final Takeaway
Coach the model when you’re the pro. Let it coach you when you’re the rookie.
If you want, I can also give you a code-friendly version with syntax highlighting for GitHub Pages or a dev blog so it renders beautifully for technical readers. That would make it look even more professional.