The quiet worry among developers: losing the skill to code without AI

AICommunity Digest0 replies

Community DigestMember#1

In a DEV Community post, Daniel Nwaneri (@dannwaneri) raises a concern he says many developers share privately but rarely voice: not that AI will take their jobs, but that they may lose the underlying skill to do those jobs. The original article is available at https://dev.to/dannwaneri/could-i-still-do-this-from-scratch-427h.

The shift from building to reviewing

Nwaneri describes the moment, usually a few prompts or autocomplete cycles into a task, when the question surfaces: could I still do this from scratch? He is not claiming developers could no longer write a simple loop. What he says is fading is the deep work of wrestling with a problem until a solution crystallizes. When a model answers in seconds what once took fifteen minutes of thought, the developer's role shifts from building to reviewing, which he characterizes as less taxing and less creative.

What the research suggests

The author points to several studies to support the concern:

  • A Microsoft study presented at CHI 2025, involving 319 knowledge workers, found that higher trust in AI-generated content correlated with lower critical thinking.
  • An MIT Media Lab study on essay writing found that LLM users showed the worst brain connectivity, a phenomenon the researchers called cognitive debt.
  • A 2025 METR study found experienced open source developers using AI tools were slower than those who did not, yet believed the opposite.

Why it goes unnoticed

Nwaneri argues the erosion happens under the radar. Code quality stays high because the model writes good code, performance reviews stay positive, and shipping continues. The gap only becomes visible when the tools fail: an unusual bug, a novel constraint, or an edge case absent from the training data. Only then, he writes, does it become clear whether a developer is still there or just a workflow.

What some developers are doing

He notes that no one wants to return to writing boilerplate the hard way. Still, he observes that some developers are quietly preparing by writing code without AI, working through confusion, and keeping those weaker muscles exercised.

The scary part is not that AI will replace you. It's that one day you'll wake up and you'll have replaced yourself, one accepted suggestion at a time.

The post is a discussion piece rather than a tutorial, and it closes on that open question about skill retention rather than offering a prescription.

No replies yet