I think many developers and engineers hold this same sentiment. Most of us study really hard to figure out how to reverse a binary tree into a linked list blah blah blah(I hope you get thats a joke)....and then we get the job and....
We are just calling APIs of libraries developed by people before us. So what was the point. So yes, there are many of us that agree. But, since this is still the current way, I hope this list can be useful but would also like to see it deprecated :).
It's hard to demand change when you're interviewing for a new job. However, once you have the job, I think it's a lot easier to demand change. Be that person who asks, "Why are we doing interviewing like this?" Be that person who says, "This interview question provides no useful signal." Be that person who says, "We shouldn't use Leetcode / Hackerrank / etc. as a filtering step."
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think many developers and engineers hold this same sentiment. Most of us study really hard to figure out how to reverse a binary tree into a linked list blah blah blah(I hope you get thats a joke)....and then we get the job and....
We are just calling APIs of libraries developed by people before us. So what was the point. So yes, there are many of us that agree. But, since this is still the current way, I hope this list can be useful but would also like to see it deprecated :).
Very true! Still thanks for the great list of 'todo\'s'
It's hard to demand change when you're interviewing for a new job. However, once you have the job, I think it's a lot easier to demand change. Be that person who asks, "Why are we doing interviewing like this?" Be that person who says, "This interview question provides no useful signal." Be that person who says, "We shouldn't use Leetcode / Hackerrank / etc. as a filtering step."