• dustyData@lemmy.world
    link
    fedilink
    arrow-up
    23
    ·
    1 year ago

    Opening a repository for the first time in months.

    Which brainless moron wrote this idiotic code?

    Runs blame.

    Oh, it was me.

    • pjhenry1216@kbin.social
      link
      fedilink
      arrow-up
      22
      ·
      1 year ago

      Fuck, I’ll look at code I wrote like a month ago and be like, “what was I thinking?”. So I try to fix it, run into some stupid issue and be like, “oh, right.”

      And this is why comments are useful on code who’s purpose or reasoning isn’t super obvious or even looks counter intuitive.

      • dustyData@lemmy.world
        link
        fedilink
        arrow-up
        13
        ·
        1 year ago

        A professor used to say, we don’t write code for the machine. The machine doesn’t need code. It would be just as happy whether we hand carve 1s and 0s on ferromagnetic disks or if we wrote a compiler for emojis. Binary is binary. We write code for the humans. So make it legible.

          • dustyData@lemmy.world
            link
            fedilink
            arrow-up
            4
            ·
            1 year ago

            I never said anything about comments. My professor advocated that the code should tell yourself and other humans what it was making the machine do. Comments should document the design and the architecture. Not explain the code. A well designed and correct code needs few comments.

    • 👍Maximum Derek👍@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      8
      ·
      1 year ago

      No one is a real programmer until they’ve experienced that sensation.

      It was more fun before blame, because sometimes it would take 10 minutes to figure out you’re the dumbass.