• Godort@lemmy.ca
    link
    fedilink
    arrow-up
    83
    arrow-down
    1
    ·
    11 days ago

    oh thaaat’s why I have a fundamental need to explain the reasons why when detailing a process to someone

    • MelodiousFunk@slrpnk.net
      link
      fedilink
      arrow-up
      49
      arrow-down
      2
      ·
      11 days ago

      And I’ve found that most people do not care, they just want marching orders. Like, I’m not here to give you orders. This is what the goal is, this is how it’s currently done, this is why we do it that way. They want to commit “how it’s currently done” to rote memory.

      And then the first (and second, and third, etc) time something does not go as planned, they’re stopped in their tracks. Context was rejected, preventing understanding, leaving little framework for the unexpected.

      So they ask me to tell him how to fix it. Well, I don’t know how to fix it. This hasn’t happened before. I do not have a step by step committed to memory. But I can probably figure it out if you give me a few minutes. There, should be good now.

      “Jeez, I didn’t want you to do it for me, why can’t you just tell me how to do it?”

    • jlow@slrpnk.net
      link
      fedilink
      English
      arrow-up
      11
      arrow-down
      1
      ·
      11 days ago

      Bit thanks for doing that, I tend to ignore rules completely when there’s no reason given (or I think the reason is bs).