I fucking swear. AI this, new frameworks that, but every fucking company I get hired by has a deluge of files that are thousands of lines long.

It's not a new concept to split up files. It's not difficult to progressively split up files as you work on them. And yet so many programmers apparently can't fucking stop for quarter a second to think "hmmm maybe adding another function to this thing that is already 20 km long might not be the best idea".

Broken window principle.
If it‘s a mess already, it‘s much easier to continue to mess it up.

I wonder if there's repetitive functions in that long ass file, because no one could be arsed to find one already declared.

@Pogromist maybe it’s just one function

... I went back to a company I worked at previously. in one app I made them I needed to pull some trivial data from a database, so I made a query file and it did a generic query object and then the simple look up call. this was java and probably under 50 lines

anyway, when I came back to this place years later... what the fuck. so apparently it never occurred to anyone to uhhh... make a package for queries, much less files. I would've made a package for queries.

anyway that one query file was over 4k lines long and it was horrific

different people just kept adding new lookup methods to it

and nobody ever once thought that maybe you should make a folder and put each domain or lookup in its own file...

... me making a file to do that simple lookup would've been overengineering. I have such mixed feelings about what I did now. WHAT WOULDVE BEEN THE RIGHT CHOICE?!