After 20 years of development I still basically suck at coding challenges in interview settings. I've never been a fan of them. The odd thing is that I've probably implemented and designed more algorithms than most programmer's will ever get the chance to. A lot of my work is actually directly related to algorithms. Yet I still suck at the "challenges".
Naturally, given the time to think, and the freedom to work through the problem normally, I can solve any of these interview challenges. But surprise me with a random question, sit my down in a totally new environment, actively watch me, and set a crazy low time lime, then I'll do poorly.
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.
After 20 years of development I still basically suck at coding challenges in interview settings. I've never been a fan of them. The odd thing is that I've probably implemented and designed more algorithms than most programmer's will ever get the chance to. A lot of my work is actually directly related to algorithms. Yet I still suck at the "challenges".
Naturally, given the time to think, and the freedom to work through the problem normally, I can solve any of these interview challenges. But surprise me with a random question, sit my down in a totally new environment, actively watch me, and set a crazy low time lime, then I'll do poorly.