• neidu3@sh.itjust.worksOPM
    link
    fedilink
    English
    arrow-up
    36
    ·
    edit-2
    9 days ago

    I might as well go first: Basic troubleshooting and reasoning.

    I mean, we’re not talking debugging assembly language here. But at least you should be able to reply correctly to the question “is it dead or faulty?” when it comes to a computer. And when a your car has a weird noise, at least try to locate it for an obvious cause such as something rolling around under your seat.

    EDIT: And one important aspect of troubleshooting many people don’t get is how to narrow down the problem. Let’s say your wifi isn’t working - have you checked on any other device whether it’s working there? Someone else mentioned binary search which has a lot of overlap with this.

    • GingaNinga@lemmy.world
      link
      fedilink
      arrow-up
      4
      ·
      9 days ago

      This grinds my gears super hard. I’ve had a few new hires come through and they can’t do anything unless someone tells them to do something or if its written out step by step. Absolutely no critical thinking, curiosity or even basic understanding of why we’re doing what we’re doing, the job might as well be severance lol. I have no idea whats going on, they interviewed well, had relevant experience and can do the basics but as soon as we have to troubleshoot or use our brains they just go dear in the headlights. Its something thats difficult to train.