Oh, it's only the files that have over 2k lines of code? Hell, I'll take that over what I'm dealing with now. I've got multiple FUNCTIONS that are over 2k lines. >:(

[–] ripcord@lemmy.world 14 points 2 days ago (2 children)

Yeah, I dont see a big problem with files over 2000 lines in some cases, as long as things remain well writrej, organized, abstractd.

One piece of garbage that I'll never touch again hae most functions this size. One was 50,000 lines! Hundreds.of lines of if/else, half of the functions passed the same 60 arguments because he didn't understand classes or even dictionaries, etc etc. And was used heavily.

[–] funkless_eck@sh.itjust.works 7 points 2 days ago (1 children)

well writrej

oh dear

[–] ripcord@lemmy.world 4 points 2 days ago

Lol I'm leaving it

[–] PhilMcGraw@lemmy.world 1 points 1 day ago (1 children)

Yeah, honestly overly splitting things up is worse sometimes, that's how you end up in Java land. Any time you want to grok a specific function you end up down 30 abstracted code paths. Essentially need a compiler to unroll it all to actually see what it's doing.

[–] ripcord@lemmy.world 0 points 1 day ago

Java was exactly the negative use case I was thinking of. Trying to track down the flow of things for code I don't look at regularly drives me insane.