Now, my problem would have been that I have, after two decades of experience working with code, no idea how to do this - but more importantly, no idea why I'd ever need to know.
Honestly, it's like this for me:
Interviewer: "Can you describe how a Red Black tree works?"
Me: "Nope. I just use std::map<> or {} or whatever and the nice programming language or library does it for me. But I can list the properties of the tree, the operations I can perform, and the complexity of them."
I can also tell you that while std:map is normally a Red Black tree in C++, it needn't be, and it's instead a weird hybrid thing in quite a few implementations in order to improve the iteration performance, which in a traditional RB tree really sucks.
Of course, none of this is very useful for the traditional dev interview, leading me to believe there's no way I could get an entry-level developer job nowadays...
This is what makes it so frustrating. Forget experience and the projects you've done, if you can't think of algorithm within 30-45 minutes, you're not good enough. Smh. But I'm gonna keep cracking at this thing. Don't give up, man!
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.
Now, my problem would have been that I have, after two decades of experience working with code, no idea how to do this - but more importantly, no idea why I'd ever need to know.
Honestly, it's like this for me:
Interviewer: "Can you describe how a Red Black tree works?"
Me: "Nope. I just use std::map<> or {} or whatever and the nice programming language or library does it for me. But I can list the properties of the tree, the operations I can perform, and the complexity of them."
I can also tell you that while std:map is normally a Red Black tree in C++, it needn't be, and it's instead a weird hybrid thing in quite a few implementations in order to improve the iteration performance, which in a traditional RB tree really sucks.
Of course, none of this is very useful for the traditional dev interview, leading me to believe there's no way I could get an entry-level developer job nowadays...
This is what makes it so frustrating. Forget experience and the projects you've done, if you can't think of algorithm within 30-45 minutes, you're not good enough. Smh. But I'm gonna keep cracking at this thing. Don't give up, man!