Programmer Humor

I thought so too until I recently inherited some asp.net code that defies basic comprehension and has existed since well before vibe coding.

Worst I've seen was at an old job. Another team broke up their project so nearly every Java class (file) was a separate Maven module. For folks unfamiliar with Maven, you may think that just means a different folder. That would be a Java package. Maven modules are compilation units with an entire XML file explaining the project with dependencies. So instead of their code being in one or , you know, less than five or so modules there were dozens. I wanna say a hundred but I don't want to exaggerate and don't remember.

Thankfully these were subprojects so they were still in one git repository and could all be built with a single invocation of Maven, but navigating it was a massive pain.

I try not to make assumptions about "bad code" but I can't think of any legitimate reason for that layout of one class per Maven project.