• @frezik@midwest.social
    11•8 days ago

    If it were a question about the tradeoffs of different sort algorithms and how they might apply to a given problem, I would agree. That’s not what these interview questions are about.

    • @danc4498@lemmy.worldEnglish
      6•8 days ago

      Maybe it’s about being able to communicate an algorithm verbally. Unless these are written interviews, then yeah, probably pointless.

      Also, I do think being able to understand how an algorithm works is probably important on its own.

      • @qarbone@lemmy.worldEnglish
        9•8 days ago

        Then give them some code and tell them to explain it. Having testees regurgitate algorithm implementations from memory is just testing rote memory.

        I thought we had all lived through terrible public schools that just tested memory, and resolved to do better.

        • BombOmOmEnglish
          2•8 days ago

          Yeah, it’s a solved problem. I’m going to call the library’s default sort and move on. If it somehow is a problem, I’ll revisit later.

          Now, optimizing database calls, fixing (and avoiding!) security holes, writing tests that don’t take forever to run, writing functions so they can be easily re-used later, and not duplicating code. Now there are some skills!

          “It’s faster if we make a duplicate of this function and change this section, then we can move onto other things”

          “No it’s much slower, because your code review just came back telling you to throw that idea in the garbage and do it right”