hn.today

If you stop writing code, you also get worse at reviewing it

cekrem.github.io377 points179 comments
Screenshot of If you stop writing code, you also get worse at reviewing it

Software engineering is often treated as an exception to the basic rule that skills improve through practice. The central argument is that engineers who stop writing code and rely on directing AI tools and reviewing their output will gradually lose the ability to understand code, recognize quality, and reason about architecture. Reading and critiquing others’ work can help, but they cannot fully replace making things yourself. The comparison is to musicians who stop playing or writers who stop writing: expertise depends on actively practicing the craft, not merely supervising it. The concern is not only whether AI-generated code works in the short term, but what happens to an engineer’s own abilities over time.

The piece also argues that every engineer must keep practicing problem-solving, even if hands-on coding is not central to every role. Working through difficult problems builds skill through effort and trial and error; routinely asking an AI to solve them can teach people to avoid that effort. This risks weakening technical judgment and diminishing the learning and satisfaction that come from solving problems independently. The author’s recommendation is straightforward: keep writing code and tackling problems yourself, rather than assuming that reviewing AI-generated work is enough to maintain or improve your skills.

Read on cekrem.github.io179 comments on Hacker News

Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.

More in Programming

The daily digest

Today's best Hacker News stories, summarized and screenshotted, one email a day.