The 40k lines of code a day crows are amusing. In solving any problem solvable by code, there's a ratio of non-coding work to coding work, and codex et al all help immensely with the coding work but help less with the non-coding work.
Non-coding work is thinking about the system architecture, thinking about how data should flow, thinking about the problem to be solved, talking with people who will use it, discovering what their objectives are.
Producing 40k lines a code per day simply means you're not doing any of that work: the work that ensures you're building something worth building.
Which is why the result is massive, pointless things that don't do the things people actually need, because you've not taken any time to actually identify the problems worth solving or how to solve them.
It's a form of mania that recalls Kafka's The Burrow, where an underground creature builds and builds an endless series of catacombs without much purpose or coherence. When building becomes so easy when it was so hard -- and when it becomes more fun to build and watch codex's streams of diffs fly by, than to plan -- we forget the purpose of building, and building becomes its own purpose, which is why we usually so little actual productive impact on the world from the "40k lines of code a day" cohort.
I agree with your point that the original claim is unlikely to be true (and would be extremely foolish behavior even if it were true). I don't think it's good to flame people though, even if they did say something unreasonable.
> "I am able to push 30-40K lines of nearly perfect code a day now."
It is physically and physiologically impossible for anyone to be reviewing "30-40K lines of nearly perfect code a day" to the extent needed to push it with confidence in a sensible development process.
Why do you and many of your industry friends conveniently never actually post their 'perfect code' when asked for proof? I've asked like five different people now that make these claims and they just vanish into the ether.
mediaman|4 days ago
Non-coding work is thinking about the system architecture, thinking about how data should flow, thinking about the problem to be solved, talking with people who will use it, discovering what their objectives are.
Producing 40k lines a code per day simply means you're not doing any of that work: the work that ensures you're building something worth building.
Which is why the result is massive, pointless things that don't do the things people actually need, because you've not taken any time to actually identify the problems worth solving or how to solve them.
It's a form of mania that recalls Kafka's The Burrow, where an underground creature builds and builds an endless series of catacombs without much purpose or coherence. When building becomes so easy when it was so hard -- and when it becomes more fun to build and watch codex's streams of diffs fly by, than to plan -- we forget the purpose of building, and building becomes its own purpose, which is why we usually so little actual productive impact on the world from the "40k lines of code a day" cohort.
rawling|4 days ago
ozgung|4 days ago
_se|4 days ago
bigstrat2003|4 days ago
ericmcer|4 days ago
Otherwise his entire team must collectively groan when a Slack message appears: "Got a new PR ready for review everybody!"
ThrowawayR2|4 days ago
It is physically and physiologically impossible for anyone to be reviewing "30-40K lines of nearly perfect code a day" to the extent needed to push it with confidence in a sensible development process.
vor_|4 days ago
fzeroracer|4 days ago
throw10920|4 days ago
Are we experiencing a huge influence campaign on HN?
gib444|4 days ago
Bnjoroge|4 days ago