Also, assuming this kid gets weekends off, he would be writing 12k lines of code each day. I don’t think the average programmer could even review that number of lines in a day
I usually estimate that it takes 1-2 hours of highly focused work to review 1k lines of code well (this is not even considering that this is AI-generated mess that probably requires a lot more attention). A typical developer is capable of ~6 hours of focused work per day (8-10 with a lot of caffeine). So no, according to my estimates at least there’s no way in hell this gets any review at all.
Ok, sure, for low-level C/C++ code with memory management and such it takes a lot longer than 2h per 1000 lines. For business logic in higher-level programming languages it’s usually fine.
I usually estimate that it takes 1-2 hours of highly focused work to review 1k lines of code well (this is not even considering that this is AI-generated mess that probably requires a lot more attention). A typical developer is capable of ~6 hours of focused work per day (8-10 with a lot of caffeine). So no, according to my estimates at least there’s no way in hell this gets any review at all.
In what world? 1k lines is a lot… Even a few hundred can take hours if everything is unknown, code is legacy, and naming is bad.
Like if there is a line like this
memcpy(ptr, src, 4 * 6 * sizeof(real));What’s that 4?
What’s that 6?
Is real a float? A double?? What are we copying, where, why???
This is a line I saw recently. 1k code is huge even if readable.
Ok, sure, for low-level C/C++ code with memory management and such it takes a lot longer than 2h per 1000 lines. For business logic in higher-level programming languages it’s usually fine.