I like the advice given here: https://medium.com/@davidbyttow/abc-always-be-coding-d5f8051afce2 https://medium.com/@davidbyttow/abc-always-be-coding-d5f8051...

I like the advice given here: https://medium.com/@davidbyttow/abc-always-be-coding-d5f8051afce2 https://medium.com/@davidbyttow/abc-always-be-coding-d5f8051... I'm thinking about making a move and am slowly prepping algorithms and data structures again myself. Going to focus on studying nuances of the language I'm working with - JavaScript (+HTML, CSS) and the frameworks I'm currently using - Angular & Node. But having seen the other side now, I recognize that you will most likely run into peoples' pet questions that you can't always prepare for. One coworker gets upset when people can't answer his Angular question, another gets upset if the Java isn't idiomatic enough. If they like you enough they'll overlook it. So study what you can, be confident but not arrogant, and recognize luck will play a factor. I'd rather be writing code to build things than for practice, but it is part of the game. And in reality the quizzes should really be a screen and the decision should be based upon the things you've built. So hopefully you have things to show, can talk about what you've done, and the team your looking to join recognizes actual accomplishments are more important than solving puzzles on the spot.