I don't read code anymore

colesantiago

Then the software you're writing isn't at all critical to justify keeping your job. You're just standing in the way of business margins by being an unnecessary expense. Or for lack of a better word, a meat proxy.

pavel_lishin

One might wonder what value he's bringing to the business, then, but it's hard to parse out much information from three sentences.

krapp

>Disagree or debate me all you want, but soon you'll realize and admit I was right. Right about what? Your own irrelevance? Fine, I won't disagree. Your mind, your skills and your talents no longer matter to anyone. Not even to you, apparently. I don't know why you're so proud of that, or why you think anyone would care.

andersco

Agents write my code but I still read and make sure I understand it, like I would read the code written by a junior dev. If I don’t understand it, or if I don’t agree with the approach, I ask questions and those questions often lead to better code. More importantly, it helps ensure I remain “connected” with the codebase which in turn informs future requests and discussions with an agent.

alasr

> I don't read code anymore First one need to define what they mean by "read" and clarify the context its being used in; then we can talk about agreeing/disagreeing part. Otherwise, we all will be playing/participating in some sort of a language game.

beybol

I've stopped reading all lines but I read very carefully specification and read/create proper ADR-s - this is crucial for me. In addition I plan strict automated tests (unit and functional) + I run mutation tests to check tests quality and find gaps. Moreover after every stage of development (not task, but several ones) I perform security review.

malux85

I very much would like to stop reading the code, but when I read it, I see insidious problems - not at the lowest level but at the medium and high level abstractions. For example - we have an internal system for tracking the staus of jobs - draft, ready, waiting for hardware, running, complete, error ... its used across some 15 different task types in our codebase. The non-code reading engineer submitted two new modules and their prompts, the prompts were specifically told to examine the other modules and follow the architectural patterns. The two new modules worked in the sense that they ran to completion, however once I looked at the code I see it had implemented new staus objects rather than reuse our internal task system, and worse it had implemented custom task objects twice, each for the two modules, each with a different set of possible statuses. The AI psychosis people will say "YoU cAN fIX tHaT bY pROmtiNG iT" which of course is true and it totally, utterly not the point here - these sorts of problems are only discovered by reading the code. Worse, if we had merged it in, (because by visual inspection it executed fine) we would only realize after 5 or 6 more merges like this when the codebase quality has severely degraded and then things like every single task having a different set of statuses and status transitions would make understanding system problems a giant mess of spaghetti. I know that reading code is hard (for intermediates and juniors) and the idea that you dont need to is alluring, but the reality is that you still need to (for now) because lurking skin deep below that code that appears to be working is a dragon that WILL bite you later. Can the LLM get rid of the dragon, of course it can, but my point is that unless you actually read the code, you wouldn't have even known it was there.

nelsonfigueroa

i was poking around your site and went here https://blog.duyet.net/2026/07/anyrouter/ and ran into an error: "Something went wrong! Minified React error #300; visit https://react.dev/errors/300 for the full message or use the non-minified dev environment for full errors and additional helpful warnings." Perhaps you should read your code just a little bit?

parsatomosu

which code reviewer are you using?

g-b-r

We desperately need some personal responsibility for the software you distribute. If you think that AI can do it all, fine, but you should spend some time in jail when the code you didn't read wreaks havoc.

abstractspoon

I suspect you never really read code in the first place, to see so little value in it now