I coded there for three years. I then moved to a program manager role to do some things I wanted to see done… and didn’t code for almost two years. I then interviewed with Facebook as an engineer, and spent a month studying around 20 hours a week.
With that time, I did three things:
- Read “Cracking the Coding Interview”.
- Read a ton on Wikipedia about data structures.
- Solved questions on a whiteboard with a marker.
So the answer here is “a lot of time”. But both times I spent the time, it paid off, so I can’t argue with the results.
My naive thoughts on this topic
I also noticed the issues I have with my practice and my performance on onsite interviews. I spent much more time to study and practice algorithm and data structure compared to the content above.
It is easy for me to get lost on counting how many hours I spent on coding on algorithm and data structure.
It is hard for me to build habit to code every day.
After two onsites in August, I worked on those interview algorithms, and also asked those algorithms on interviewing.io.
But very good coding habit is to code every day, every hour. It is to push myself to train myself, take hard choice, work on something new, move myself outside comfortable zone.
I do believe that it helps me to calm down very quickly. Stay humble. Otherwise, I may end up not efficient at work as well, in my personal business as well.
Problem solving skills need to be worked on more often.
My mark is 421 solved on leetcode.com today.
No comments:
Post a Comment