3 Tips for Technical Interview preparation that often overlooked
↓
Don’t try to memorize all the answers
It’s impossible
There are tons of questions, and you can’t memorize them all
Take your time and learn how your language works and why that way
Simply reading code someone else wrote will not cut it
Make sure you actually can code algorithms and data structures
This is very important
Force yourself to pretend you are in an interview setting
Most of the code questions you will be asked should be solvable in 10-25 minutes, some will be more
Time yourself
– Nick ✨
I'm writing a book "How To Nail The Technical Interview" where I've summarized everything I've learned, all my tips & tricks, and other developers experience into the proven system any developer can use to pass the interview and get a job
Here the simple cheat sheet that can save you hours per week
↓
100 - Continue
Server is satisfied with the initial information about the request and client can continue to forward headers.
101 - Switching Protocols
The server suggests switching to a protocol more suitable for the specified resource. (list of proposed protocols server indicates in the header field `Upgrade`)