• ayyy@sh.itjust.works
    link
    fedilink
    arrow-up
    36
    arrow-down
    1
    ·
    1 day ago

    Where i used to just walk to the other room and ask something from my collegue i now need to message them in our internal and hope they notice it. Getting answers for questions have turned from 5 minute thing to 10-40 minute things.

    Those rude shoulder-tap interruptions may have only taken you 5 minutes, but they ruined half an hour of productivity to the person you were interrupting. This is the whole reason people can be more productive at home without annoying bosses blathering at them.

    • sunbytes@lemmy.world
      link
      fedilink
      arrow-up
      15
      ·
      1 day ago

      Yeah every programmer I know loves not being exposed to the manager who just “has a question” or just want to “check in”.

      • MrFinnbean@lemmy.world
        link
        fedilink
        arrow-up
        3
        arrow-down
        1
        ·
        1 day ago

        Nah. Coders get slack messages. Only exception is if something is truly fucked and it needs to be fixed asap and for some strange reason i notice it before they do. Mosty happens when they push from test to production.

        We have biweekly check ins with code team and thats enough.

        • insaneinthemembrane@lemmy.world
          link
          fedilink
          arrow-up
          2
          ·
          edit-2
          14 hours ago

          Anyone in focus on anything will have 20m ruined at minimum by your 5m interruption. It doesn’t have to be coders. Your 5m interruption is one big reason a lot of people love wfh.

    • rumba@lemmy.zip
      link
      fedilink
      English
      arrow-up
      8
      ·
      1 day ago

      The immediate interruption is good for management, but bad for the company overall.

      That’s why we still have Jira/email.

      Critical importance: slack/in person

      Can wait but important: high importance email, P1 Jira

      Not important: Low impotance email, P2 Jira