you’ll see that he doesn’t like functions to be very long. I think his rule is no more than 4 lines.

Four line functions? Sounds like a codebase adhering to that rule would end up as a nice thick function soup. It feels like..... I dunno, those database programmers that like normalising databases to the Nth degree.

If you put your loops into functions then you can just use return instead of break.

And that just sounds like abusing the concept of functions to replace standard flow control that your language provides.

I mean, sure, if I find repetitive chunks of code popping up I'll break them out into functions, but - generally speaking - I do functions that translate into discrete real-world or UI tasks. I'm opening and parsing a text file into internal structures, I'm doing the reverse to go back to a data file, I'm cycling through the data to update UI components, etc etc.

But hey, I use C and on the rare occasion I sneak a goto in there, so I'm not qualified to pass too much judgement.