• brokenneon@kbin.social
    link
    fedilink
    arrow-up
    2
    ·
    2 years ago

    I always say I write throwaway code that never dies. I shutter to think how many pieces of code I wrote 10+ years ago are still buried deep in systems running today. Shutter.

  • celipon@kbin.social
    link
    fedilink
    arrow-up
    1
    ·
    2 years ago

    It is always the worst code you wrote that survives. There’s a terrible university dorm management software I wrote eight years ago as a student. They still use it. The crazy complicated test framework wrappers for some hardware I wrote five years ago. They still use it. The godawful and crazy complicated communication protocol I whipped up four years ago, still used in medical equipment today.

    • masterspace@kbin.social
      link
      fedilink
      arrow-up
      1
      ·
      2 years ago

      The crappy scripts that I wrote while teaching myself to code at an electrical engineering / architecture firm are used more often than the professional software I’ve built for FAANG and Fortune 500 companies since.

  • Emi@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    1
    ·
    2 years ago

    I have a mental image of 50+ lines that could be replaced with 15 if someone just used a loop.

  • alp@kbin.social
    link
    fedilink
    arrow-up
    1
    ·
    2 years ago

    I really think that optimization courses should have a special lecture in the optimization of optimization…

  • nobodyspecial@kbin.social
    link
    fedilink
    arrow-up
    1
    ·
    2 years ago

    As with relationships, if you make a mistake you’ll wind up supporting it for life.

    I kid, I kid. We all know to job hop every 2 years for better compensation. It’ll be someone else’s problem after that.

    • mfz@kbin.social
      link
      fedilink
      arrow-up
      1
      ·
      2 years ago

      Yes, yes, and someone else’s problem will be your problem after the job hop! :)