Comments by "Vitaly L" (@vitalyl1327) on "Algorithms In Interviews SUCK | Prime Reacts" video.

  1. And those business requirements are algorithms. Your working applications are built of algorithms. But these algorithms are high level, big and complex. You cannot ask to "translate business requirements into working applications" in a 40 minutes interview. So the only way to assess if you can do it is to ask you to construct some small and simple algorithm instead, more fit for the time scale of the interview.
    5
  2. It's very easy to see if the answer was memorised or invented on spot.
    2
  3. Also, allows to weed out bootcamp "graduates".
    2
  4. And know what? You're right. Not necessarily Haskell, of course, but I tend to significantly downgrade my opinion of people I'm interviewing if they do not have at least some knowledge of a wide range of languages and paradigms. And if they do - I give them a chance to show off.
    2
  5. Well, you're among those who's going to be replaced by stochastic parrots and then whine about it. If you did not use the knowledge of algorithms in your job, you, most likely, were doing it wrong.
    1
  6. There is a good reason for algorithm questions in interviews: real-world algorithms are extremely complex and convoluted. No way one can build or analyse such an algorithm in any reasonable time-frame for an interview. So the only way to assess an ability to construct and to analyse algorithms is to use those simple, basic ones. If in process people who cannot even handle simple algorithms will be weeded out - that's a cherry on a top, but not a goal per se.
    1
  7.  @xybersurfer  you cannot test for the ability to construct and analyse algorithms that are "actually part of the job". They are too big and complex. So there's no choice but to test on simple ones.
    1
  8.  @xybersurfer  there are no programming jobs that do not require algorithms. But for most of the jobs algorithms are very high level and complicated, so they are not fit for the interview time scales.
    1
  9. Frankly, there should not be any frontend jobs. Glorified Markov chain can do this crap better than humans anyway.
    1