There's a quiet anxiety spreading through engineering teams right now: Am I becoming dependent on AI? Is my judgment atrophying?

My take: that's the wrong question. The right one is whether you're using AI in a way that sharpens your judgment or replaces it. Those are genuinely different modes of use, and most engineers drift into the second one without noticing.

The Dependency Trap Is Real — But Misdiagnosed

The common critique is that AI tools make engineers lazy. I don't think that's it. The problem isn't laziness — it's abdication. When you accept a generated solution without interrogating it, you're not saving time. You're deferring a debt that compounds interest.

The engineer who copy-pastes an AI-generated auth middleware without reading it isn't moving faster. They're moving faster now and slower — much slower — when that middleware silently fails in a production edge case at 2am.

But here's where I'll stake the actual opinion: the solution isn't to use AI less. It's to use it adversarially.

Adversarial Use, Concretely

What does adversarial use look like? You treat the AI output as a first draft from a smart-but-overconfident junior engineer. You don't reject it reflexively and you don't accept it wholesale. You interrogate it.

Here's a prompt pattern I've baked into my actual workflow:

Here's the solution you proposed: [paste output]

Now argue against it. What are the edge cases this doesn't handle? 
What assumptions did you make that might not hold in a production system? 
What would you change if you knew this code would be read by a senior 
engineer in a security audit?

Run that after any non-trivial AI-generated solution. What comes back is almost always useful — missed error states, implicit assumptions about input shape, security surface area that got glossed over. And critically: you are now thinking alongside the tool, not just consuming its output.

That loop — generate, interrogate, revise — is where judgment lives. It's where you stay sharp.

The Real Skill Isn't Prompting

The engineers who will be dangerous with AI five years from now aren't the ones who have memorized the best prompt templates. They're the ones who can look at any generated output — code, architecture diagram, spec, test suite — and immediately ask the right skeptical questions.

That skill is built by practice. Adversarial prompting is one way to practice it deliberately rather than accidentally.

AI doesn't erode engineering judgment. Passive AI use does. The distinction matters, and it's entirely within your control.

I break down one concrete AI workflow like this every week in The AI Leverage Weekly — practical, no fluff, free. Subscribe: https://theaileverageweekly.beehiiv.com/subscribe?utm_source=devto&utm_medium=article&utm_campaign=medium_w3