I lost him at: "I think homebrew is an awful piece of software that should never be used by anyone."
I Don't Want to Hire You If You Can't Reverse a Binary Tree
31–40 of 115 posts
Re: I Don't Want to Hire You If You Can't Reverse a Binary Tree
#32It did however make me think of an almost opposite activity for the next time I interview someone:
Pick a difficult trick question (like Binary Tree reversal but harder/arcane) that neither of us can solve, and spend some time working on the problem together with the candidate.
After all, solving problems together (directly, or indirectly) is what we'll be doing day to day.
This might not be a good idea, but I'll definitely try it out once and find out.
Re: I Don't Want to Hire You If You Can't Reverse a Binary Tree
#33Couldn't disagree more with the author. How many developers need to implement their own binary-tree? This is why code-bases become convoluted with six different implementations of standard data structures.
That's missing the point of the article. The author says that the candidate's thought process behind arriving at the solution provides insight into the candidate's skill. There's no reason to implement your own binary tree, but knowing how to devise algorithms to accomplish a given task is a necessary competency.
Re: I Don't Want to Hire You If You Can't Reverse a Binary Tree
#34I lost him at: "I think homebrew is an awful piece of software that should never be used by anyone."
Re: I Don't Want to Hire You If You Can't Reverse a Binary Tree
#35Sigh. If you hire using know it or not questions about binary trees, then you finally get to hire people who can study up and answer that specific question in a manner Pavlov would approve of. That does not mean the candidate will be able to design clean APIs, know how best work with different types of data, or even how to troubleshoot existing code. Still, pat yourself on the back, I mean, your entire team can answe…
Re: I Don't Want to Hire You If You Can't Reverse a Binary Tree
#36Couldn't disagree more with the author. How many developers need to implement their own binary-tree? This is why code-bases become convoluted with six different implementations of standard data structures.
That's missing the point of the article. The author says that the candidate's thought process behind arriving at the solution provides insight into the candidate's skill. There's no reason to implement your own binary tree, but knowing how to devise algorithms to accomplish a given task is a necessary competency.
Re: I Don't Want to Hire You If You Can't Reverse a Binary Tree
#37> "Just about everything you do in your programming career will be related to trees." I've never knowingly used a tree structure since college, everything is abstracted away from me. Now whether this is a good thing or a bad thing remains to be seen, but it has not been a problem yet.
Re: I Don't Want to Hire You If You Can't Reverse a Binary Tree
#38Couldn't disagree more with the author. How many developers need to implement their own binary-tree? This is why code-bases become convoluted with six different implementations of standard data structures.
Well, to pick on Valeri, this is simply wrong Trees are the single most important data structure in computer science. Just about everything you do in your programming career will be related to trees. Trees are a horrid data structure for any modern processor. Pointer chasing thrashes caches. The actual most important data structure is a hashmap. The same speed in theory, much faster in practice.
Re: I Don't Want to Hire You If You Can't Reverse a Binary Tree
#39I lost him at: "I think homebrew is an awful piece of software that should never be used by anyone."
Re: I Don't Want to Hire You If You Can't Reverse a Binary Tree
#40Also, way to back up your claim that Homebrew is bad software by pointing to another guy not explaining anything about Homebrew but just dogpiling on Howell again.