More philosophical is the book by Martin Fowler: Refactoring.
Not giving hard figures, but more ways of looking at your code base with common sense.
But mind you, AI coding will change all that, AI agents don't need comprehensible code, in fact, they might just make code more 'efficient' (not a variable 'name', but just 'a') in a way that we humans cannot understand anymore.
Maybe agents devise a 'middle language' that only AI coding agents can understand, highly efficient.
And then methods of thousands of lines of code might not be an exception anymore.

I found the Quit ambiguous; it's not very clear what it does.
But especially within nested for-loops, once you found what you were looking for, you needed several Quits (one for each level) and a flag such as 'Found'.
Return is unambiguous and does exactly what it says.
 

Return was implemented in 2012 in the Cache 2013 FieldTest.
I know because I proposed it to ISC in my yearly wishlist to Joe DeSantis and Robert Nagle.
The documentation in that FT was literally the text of my proposal ;-)