'I Can’t Defend My Own Code': Techie Reveals How 3 Years Of AI Dependence Left Him Terrified
A software engineer’s candid confession about becoming increasingly dependent on AI for coding has gone viral on X. The techie admitted that he now struggles to understand some of the code generated for his projects, pro
مصنف Sakshi Arora··81K بار پڑھا
'I Can’t Defend My Own Code': Techie Reveals How 3 Years Of AI Dependence Left Him Terrified
A software engineer’s candid confession about becoming increasingly dependent on AI for coding has gone viral on X. The techie admitted that he now struggles to understand some of the code generated for his projects, prompting fellow developers to share their own experiences and advice.
The techie, who said he has around three years of experience as a software development engineer (SDE), described feeling increasingly disconnected from the code he writes.
In a post that quickly gained traction, he admitted that he now relies on AI for almost every stage of his work and sometimes struggles to understand the architecture and implementation produced by the tools he uses.
Reflecting on his career, the engineer said he joined the corporate world straight out of college around the time large language models (LLMs) were becoming widely popular. Initially, using AI did not feel particularly concerning.
His tasks involved smaller bug fixes and basic features, allowing him to prompt an AI tool, skim through the generated code and still broadly understand how everything worked.
However, he said the situation changed as he began receiving more complex, end-to-end assignments. According to him, his current workflow often involves feeding requirements into Claude, accepting the generated output and pushing the changes. The problem, he explained, is that he does not always understand the architecture or code that has been produced.
That dependence has become particularly uncomfortable during code reviews. The engineer said that whenever senior developers leave detailed comments or ask questions about his merge requests, he becomes anxious because he cannot always explain or defend his implementation without first putting their feedback into an AI tool.
He also acknowledged the irony of his situation, revealing that he had used AI to polish the very post in which he was discussing his dependence on it. He said his focus had suffered, his critical-thinking abilities felt weaker, and he had increasingly struggled to read documentation or manually trace code.
Describing the situation in stark terms, he wrote that “The crutch became the wheelchair” and said he felt “completely useless, fraudulent, and terrifyingly replaceable.” He even worried that without AI, his coding ability could resemble that of “a first-semester freshman.”
The engineer ended his post by asking whether others had found themselves in a similar situation and successfully rebuilt their fundamentals. He also sought practical advice on breaking his dependence on AI and learning to think through technical problems independently before the issue affects his career.
The post prompted a range of reactions. One user questioned the expectations placed on developers, saying, “Senior engineers are so stupid to ask you this stuff cause they want you to work fast using AI and then also expects to give you every detail when they themselves using AI.”
Another commenter suggested that the situation may be increasingly common, writing, “This is far more normal nowadays than you think.”
“You’re going to only get out of this by using AI to critique you by prototyping, you’d need to invest more time into learning by doing smaller problems that’ll help you understand systems better, eventually you can answer things on your own, ask claude why it wrote what it wrote learn from the back and forth, you need to stop worrying because at the end of the day you still have an experience to put on paper, you can justify it by learning daily,” a third user said.
Others recommended going back to traditional learning methods. One user wrote, “Lol. Start learning things maybe.. Therr are 3-4 really good books around system design, backend engineering, software architecture and plan. Order them from Amazon Read them in your free time, and lower down ur dopamine levels….read 2-3 pages then go to sleep.”
Another suggested using AI more deliberately before submitting code for review. “Take the help of ai to understand every bit of the code right before raising the PR. like why this approach only, what could be the other approaches, explain the code changes snippet by snippet!! like these, this will help you a lot! and dont worry this has become a new normal!” the user commented.
One commenter also shared a similar personal experience, explaining, “I’m with you on this one same thing happening with me i started coding using ai and I’m completely dependent on it. I used to be given small tasks but now complete end to end I’m able to handle with ai.
Tho what I do is i use ai to analyse and understand what needs to be done, what’s the existing flow and how it should be done. And then also review all the changes it did and use it understand it before PR. But yeah completely dependent on it. One day one of the tool which I was dependent on stopped working i got so tensed.”
Disclaimer: This article is based on user-generated content. The claims made in the original post have not been independently verified by News18.