[crystal_revenge]

I don't personally know anyone who writes code any more (for work). Is this not the case for you?

The distinction I see now is between teams that read PRs and teams that don't. I still think the former is a good approach... for now, but I don't expect this will necessarily be the case in a year (or less).

This article was such an inspiration to me when I was younger, and the advice, for that time, was very correct. However seeing it today really drives home how big the gap is going to be in really understanding code in just a few more years.

[zero-sharp]

>I don't personally know anyone who writes code any more (for work). Is this not the case for you?

I hear this from time to time. But I still write code at my job. I'm not a software engineer and I don't work for a software engineering firm.

[my-next-account]

I do! A lot of the work I do is not simple CRUD, and I have to think about what's going on. Reading code doesn't do that to the same degree.

[soulofmischief]

Cutting-edge models are capable of much more than generating CRUD apps and understanding the details is orthogonal to whether you wrote the lines yourself or not.

[eventualcomp]

Programming without writing, to me, feels like doing mathematics by reading proofs but not doing proofs. Which quite frankly works very poorly for me. I write code if, for nothing else, so that I can spot bad code/proofs with an easier time, rather than dealing with an equation that blew up in prod.