So, I wonder which is harder to understand?

In one corner: A million lines of code from a CMM Level 4 organization generated by Rational Rose.

In the other corner: A million lines of code vibe-generated by four levels of agents.

LET'S GET READY TO RUMBLE!!! .... Ding!

Hearing about developers becoming exhausted by reading the output of LLMs has me wondering if it's exposed the fallacy of that whole "programmers spend more time reading code than writing it" trope.

No, they don't. And they never have.

Oh, sure, developers spend a lot more time "seeing" code than writing it. I'll give you that. Kind of in the same way that someone looking out the window while riding on a train is going to see far more gardens than they'll personally ever plant.

Sometime people ask me why I don't want to do any more "expert witness" gigs. The main reason is that it was entirely focused on reading code. Actually *reading* code that I didn't write and trying to understand what it was doing. It was exhausting as all hell. No. I don't need that kind of day-to-day stress.

This seems interesting and relevant to my exhaustion comment.

Source: https://jenniferplusplus.com/what-is-a-token/

If I install a third party package on a project, I'm probably not going to look at its code at all. Similarly, for a coworker, I'm probably not going to look all that closely at their code either.

In both situations, I'm starting from a place of "trust" which is very different than starting from a place of "suspicion."

In any case, having to keep an eagle-eye on everything all of the time doesn't seem very enjoyable to me.

@dabeaz in my recent experience, we do read a lot of code, based on all the cross reviews we do. This allows us to build that trust (or lack thereof) more rapidly.