• tslnox@reddthat.com
    ·
    1 year ago

    I'm not really a programmer but when I code something at work to make my job easier and I have to go before I finish it, I write a little comment for my future self to explain how I'm thinking at the moment, to help restore the flow.

    Usually it doesn't work. :-D

    • megane-kun@lemm.ee
      ·
      edit-2
      1 year ago

      Because my work tends to have me working on a wide variety of features, and thus operating on vastly different parts of the codebase, I make it a point to comment out every change I make complete with the ticket that requested the change, and what the intended effect of the change is.

      Cue me returning to piece of code I made (after the inevitable bug has arisen) and me staring at my own code changes in bewilderment, wondering what past me really wanted to do. Hahaha!

    • jazir5@lemmy.ml
      ·
      1 year ago

      Now you can try to get chatgpt to explain what it does. Or Facebooks code llama.

  • FUCKRedditMods@lemm.ee
    ·
    1 year ago

    Sometimes working at something for long enough puts you into like a fugue state. It’s like the opposite of “flow” where you just dumb down.

    ^This happens to me only when I had entered my dumbzone the previous shift

    • hexaflexagonbear [he/him]
      ·
      1 year ago

      I stg sometimes conversations with my coworkers will give me memento disease and I have to go on a hunt for clues I lefy myself to figure out what I was working on 5 mins ago.

  • Okalaydokalay@lemm.ee
    ·
    1 year ago

    My boss has a morning meeting where we tell him what we’re working on for the day. And every Monday, this meeting is at 8:00 when my shift starts. I’m thankful my name makes me further down the list because I would be stumbling to get that.

    He’s a cool guy and not overly micromanager or anything, so it’s not a huge thing, but just reminded me seeing this meme.