4 ms·

This is a great guide, thanks for sharing. Out of curiosity, how do other employed developers allocate time to study this stuff? Immediately after graduating f

by csnewb 10y ago

This is a great guide, thanks for sharing. Out of curiosity, how do other employed developers allocate time to study this stuff? Immediately after graduating from college I could spend 4-8 hours a day most days of the week reviewing algorithms and solving problems without issues. Now, after a full day of coding at work, going to the gym, coming home to prepare dinner and run other errands, I'm physically and mentally drained. I might spend an hour or two before bedtime trying to study this stuff (since I completely forgot it since I last did technical interviews 1+ years ago) but progress is slow. Of course there are weekends, but that's usually the only time I get to relax and go outside to see the sun. I now understand why it takes 6+ months for working professionals to find new jobs.

dlo 10y ago
Another possibility is to work on your ability to work out the different algorithms and data structures on your own with perhaps a minimal specification or statement of the requirements. This would require a focus on understanding as opposed to memorization. Also, this ability has broader application than doing well at interviews.
cs02rm0 10y ago
For the most part as an employee, do it on work time. If you need an important algorithm or data structure, then put extra time in beyond the one you know you can make it work with. Pay as much attention to what's not suitable for the job today as what is. Of course, that means you're to some extent limited by what your work requires, but I think devs should feel not just that it's ok to check out this stuff at work but that they have a responsibility to. The other way around it, depending on your local market, I find is contracting. Then people tend to care less about your theoretical knowledge and rely more on being able to show you the door if you don't produce the goods.
nullundefined 10y ago
Honestly, don't bother practicing "this stuff". Instead, spend your time doing what is important to you (family, friends, side projects, side business, whatever). If you need a job, then practice. While doing your job, do it well. Don't waste your personal time on this "stuff". That's really a waste of time and effort.

by csnewb 10y ago

dlo 10y ago

Another possibility is to work on your ability to work out the different algorithms and data structures on your own with perhaps a minimal specification or statement of the requirements. This would require a focus on understanding as opposed to memorization. Also, this ability has broader application than doing well at interviews.

cs02rm0 10y ago

For the most part as an employee, do it on work time. If you need an important algorithm or data structure, then put extra time in beyond the one you know you can make it work with. Pay as much attention to what's not suitable for the job today as what is. Of course, that means you're to some extent limited by what your work requires, but I think devs should feel not just that it's ok to check out this stuff at work but that they have a responsibility to. The other way around it, depending on your local market, I find is contracting. Then people tend to care less about your theoretical knowledge and rely more on being able to show you the door if you don't produce the goods.

nullundefined 10y ago

Honestly, don't bother practicing "this stuff". Instead, spend your time doing what is important to you (family, friends, side projects, side business, whatever). If you need a job, then practice. While doing your job, do it well. Don't waste your personal time on this "stuff". That's really a waste of time and effort.