Urgent.News

What's breaking now, across thousands of outlets.

Editions

AI

I Got Called Out by My Senior — and It Taught Me the Real Cost of "AI-First" Coding

For a while now, I've been quietly embarrassed about something, and I think a lot of junior devs are quietly dealing with the same thing — so let's talk about it instead of hiding it. The Pattern More times than I'd like to admit, I've walked into a task without fully understanding it. Not "I understood 80% and figured out the rest" — I mean genuinely unclear on what was being asked, why it…

For a while now, many junior developers have quietly acknowledged feeling embarrassed about something — they recognize they're not alone. The issue revolves around jumping into coding without fully grasping the task at hand. In the past, I often walked into tasks without a clear understanding and relied on AI to generate code. Although the output appeared complete, I couldn't explain the reasoning behind it.

A senior developer recently called me out during a walkthrough, asking why I approached the task a certain way. I froze because I couldn't articulate my thought process.

The problem wasn't AI itself, but rather using it to bypass the understanding step. When confronted with unclear requirements, natural discomfort arises — a feeling of not knowing what to do. This discomfort should prompt questions, deeper exploration, and a slower approach. However, AI can eliminate this discomfort by providing plausible answers instantaneously, preventing actual understanding from occurring.

To address this, I've started restating tasks in my own words before coding or using AI. If I can't write a concise explanation of the task and its significance, I realize I haven't grasped it yet. Additionally, I ask clarifying questions before beginning tasks, as seniors appreciate proactive inquiries more than questions asked after getting stuck.

I now draft a rough approach first and use AI as a reviewer rather than an author. Before presenting any solution, I conduct a brief self-interview to question my choices and alternatives. If I genuinely lack a solid reason, I openly admit it, rebuilding trust through honesty rather than making up justifications.

While I share this experience, I acknowledge that many others in similar situations might feel the same — proficient at producing output but shaky on the reasoning behind it. The discomfort of being called out can be challenging, but it also serves as the fastest feedback loop, prompting much-needed changes. If you've encountered the same pattern of relying on AI to resolve the discomfort of not understanding, you're not alone.

The solution lies not in abandoning AI but rather in consciously adjusting when and how to utilize it.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in AI

More from Friday 21 August →