When was the last time you used a Fibonacci algorithm when building a commercial product? I would hazard a guess around never. If you attempt to use O-notations to make informed predictions you are using your imagination to make wildly uninformed guesses, which is why nobody does that in real life.
My observation working 15 years as a JavaScript developer is that most people working professionally writing code cannot program or they can only in an extremely superficial level. Reading a popular code book about cracking the interview is a poor substitute.
If you really really want to know if a candidate is worth the words on their resume just ask them simple common sense things from a product perspective and see if you get back a simple common sense response. For example: Tell me how you would write a proxy to inspect or redirect traffic. or How would I inject real time data into the browser without polling the server?
The people that will over engineer simple questions into an ocean of bullshit are the same people that will turn your code into a mountain of dependency hell spaghetti. The goal is to look for confident people who don’t need to search for creative nonsense because they have solved world’s ills thousands of times and can do it in their sleep with about 3 lines of code without hoping some external tool will do it for them.
Sigh.
When was the last time you used a Fibonacci algorithm when building a commercial product? I would hazard a guess around never. If you attempt to use O-notations to make informed predictions you are using your imagination to make wildly uninformed guesses, which is why nobody does that in real life.
My observation working 15 years as a JavaScript developer is that most people working professionally writing code cannot program or they can only in an extremely superficial level. Reading a popular code book about cracking the interview is a poor substitute.
If you really really want to know if a candidate is worth the words on their resume just ask them simple common sense things from a product perspective and see if you get back a simple common sense response. For example: Tell me how you would write a proxy to inspect or redirect traffic. or How would I inject real time data into the browser without polling the server?
The people that will over engineer simple questions into an ocean of bullshit are the same people that will turn your code into a mountain of dependency hell spaghetti. The goal is to look for confident people who don’t need to search for creative nonsense because they have solved world’s ills thousands of times and can do it in their sleep with about 3 lines of code without hoping some external tool will do it for them.