Comment Re: At least half true. (Score 1) 35
At some point being faster is a liability if you feel compelled to "make the most of it". Impossible to apply that 'lot of judgement' when you get a gigantic ball of code submitted within a short window of time. I think pointing fingers at the patch is *absolutely* warranted if it turns out that the slopped up patches end up kneecapping the code more often than it happened before. Yes tighter testing discipline is *absolutely* needed, because the patches have gaps that no one is used to expecting, and certainly not going to find in a multi-thousand line merge request submitted by some entry level guy that asked Claude to add some unasked for feature that he thought was 'neat' that touches just tuns of unrelated code for no sane reason (most recently, the guy seemed to induce it to make every call to an external library only be called from a single place and rework all calls in a file to call a 'helper' to call the function from a library, impossible to review volume of code for zero benefit, and offtopic for the alleged meat of his request).