• xmunk@sh.itjust.works
    512·
    6 months ago

    Ha, you remember 15 year old bugs? I’ve “fixed” bugs that were deliberate decisions because the fix was worse then the bug - so I’ve then unfixed the bug and said “7 years ago xmunk, that was really quite a good decision… SO Y U NO COMMENT!” Of course, since I’ve fixed the same fix twice it’s now burned into my memory so there’s no reason to leave a comment at this point.

        • agentshags@sh.itjust.works
          2·
          6 months ago

          I love living vicariously. I feel this whole situation, and I barely ever did more then the (bare bones) intro to AMOS, or or hello world on c64 basic, but Lemmy and the hard R site (before the API mess) memes make me feel the situations at hand, even with very minimal understanding of coding.

      • Abnorc@lemm.ee
        4·
        6 months ago

        Coding requirements could be a lot less strict if we just solved this bus problem.

    • ExtraMedicated@lemmy.worldEnglish
      4·
      6 months ago

      There’s been a few times where I had to look into an issue and found a comment I wrote much earlier with a ticket number or link to a previous ticket that explains exactly why this new issue is actually the intended behavior.

      It’s really helpful when the product owners clearly can’t make up their minds about what they want their apps to do.

    • Monument@lemmy.sdf.orgEnglish
      17·
      6 months ago

      Only when it’s traumatizing.

      Things that seem to go well and then later need intervention are the worst.
      Suddenly I’m Gandalf: “I have no memory of this place.”

  • ChickenLadyLovesLife@lemmy.worldEnglish
    14·
    6 months ago

    Not a bug exactly, but about ten years ago I was working as an iOS developer and to get around a major problem introduced by the app designer, I made use of a “private method”, which is something an app supposedly gets rejected for by Apple. I came up with a way of hiding it and had to sweat out the approval period before it went live. Ten years later that shit is still there; I’m sure the developers currently responsible for the app don’t even know it’s there. I normally comment my code with an eye to helping future programmers understand what’s going on and why, but this hack was one where I even obscured the comments.

  • homura1650@lemm.ee
    10·
    6 months ago

    Around 2 years ago, I got an email from a products team asking me for urgent help extending a program in time to make a sale.

    I looked over the program and wrote back sonething along the lines of “this program was written almost a decade ago by an unsupervisered highschool intern. Why TF are we still using it?”.

    Of course, I ended up helping them, because that highschool intern was me, and I ended up helping because no one else could figure out what highschool me was thinking.

    • PrettyFlyForAFatGuy@feddit.uk
      3·
      6 months ago

      I sometimes wonder if the spaghetti i wrote when i was still learning to program (on my own, in the corner of the room, ignored by all the “real” devs) is still used by the team i wrote it for.