• GroteStreet 🦘@aussie.zone
    link
    fedilink
    arrow-up
    13
    ·
    1 year ago

    Oh that’s not uncommon in the industry. Especially when dealing with legacy code.

    Personal best was 40k lines in a file called misc.c containing all the global functions that don’t fit anywhere else.

    Runner up was the one where each developer dumped their miscellaneous functions in their own files, so they don’t have to deal with merge conflicts. Which means we had x1.c, x2.c, x3.c … etc.

    • xedrak@kbin.social
      link
      fedilink
      arrow-up
      8
      ·
      1 year ago

      Oh trust me, I know. Personal best is 20k lines in a Java file that served as the main control flow of the entire software. Just because it’s common doesn’t make me any less disgusted 😂

      Thankfully now I’m the asshole senior who gets to prevent this kind of stuff from happening in the first place. But like you said, that doesn’t help with legacy applications lol.

    • YMS@kbin.social
      link
      fedilink
      arrow-up
      5
      ·
      edit-2
      1 year ago

      Best I can offer is a combined UI and logic class with 12,500 lines currently. It started out with less than 3,000 lines in the year 2000 (using the brand new Java 1.3), grew to 14,000 over time and survived our recent project-wide one-year cleanup project with only minor losses of code lines.