Software Doug

A software engineer argues that writing code by hand remains valuable even in an era of capable AI coding agents. The core argument is that hands-on coding provides attention, ownership, and architectural understanding that passive code review cannot replicate. AI-generated code accumulates fragility when humans disengage from the details — agents amplify bad decisions conservatively rather than cleaning them up. The author frames software engineers as builders of the 'software factory' (CI, tests, evals, AGENTS.md) but insists that occasionally diving into the code itself — debugging, refactoring, deleting — is essential for maintaining architectural taste and catching systemic weaknesses that agents miss.

Why write code in 2026

Engineers in denial are just coping. Manually typing out syntax is no longer stimulating or efficient. The current era of software development is driven by AI: the AI writes the code, while the engineer inspects the diffs, manages the architecture, and orchestrates the codebase. AI isn’t a threat; it’s the new IDE. It is the new baseline.
Remember when developers had to code without linters or auto-completion? Once those tools dropped, they became mandatory for speed and efficiency. Arguing against AI today is like asking, ‘Why use modern frameworks when you can just code in Assembly?’ The reality is that most AI haters are simply refusing to adapt, holding themselves back from the next technological leap. Writing every line of code by hand is officially old school. Technology is mutating, and developers must mutate with it.

As always, the truth lies somewhere in the middle. Extremes like “wibe coding is crap” or “good code can only be written by hand” are fringe opinions.
Use tools wisely and do not reject technological progress.
<img src="https://media.daily.dev/image/upload/s--3wxsUfe1--/f_auto/v1784209289/ugc/content_05f39a26-51ea-490e-9c85-8412b3a2e970?_a=BAMAMicg0" alt="image.png">