• kamen@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    1 month ago

    If you hand out a problem and only accept one solution out of multiple valid ones, you’re part of the problem.

    • SkaveRat@discuss.tchncs.de
      link
      fedilink
      arrow-up
      1
      ·
      1 month ago

      When I interview (experienced) devs, I often ask way too generic questions. Something along the lines of “can you explain what a hash is?”, without stating what kind of hash and in what context

      The primary goal isn’t really to explain it in detail, but to see if they get confused and ask for clarification. Way too many people just start assuming something, when a task is not defined properly. I need coworkers that push back on bullshit, and not blindly implement whatever runs along their desk, no matter how little sense it makes

      If I don’t hear at least one “it depends” during an interview, I don’t have high hopes

      • zalgotext@sh.itjust.works
        link
        fedilink
        arrow-up
        0
        arrow-down
        1
        ·
        1 month ago

        Your candidates aren’t mind readers though. If you want people to ask clarifying questions, you have to ask them things other than comp sci trivia questions.

        • CanadaPlus@lemmy.sdf.org
          link
          fedilink
          arrow-up
          1
          ·
          1 month ago

          It could be on a different subject, but it has to be a trick question. If they were prompted to ask more, that would undercut the whole point of the test, since OP wants employees that always ask or question.