- could certainly fix them if paid a Google-sized salary
But he won't dance to the tune of the "Cracking the Coding Interview" juggernaut so to heck with him. Better to spend time memorizing the Floyd Cycle Detection algorithm than produce useful code.
I mean he says he doesn't really know what a b-tree is. That's a pretty basic data structure and kind of table stakes for being a software engineer. Even then, Google gave him a good look with 7 interviews. Just speculating here, but they probably would have given him a chance if he wasn't "often a dick" and "often difficult".
> That's a pretty basic data structure and kind of table stakes for being a software engineer.
It really isn't. You don't need to know what a b-tree is to do most modern software engineering.
> Even then, Google gave him a good look with 7 interviews. Just speculating here, but they probably would have given him a chance if he wasn't "often a dick" and "often difficult".
This is not a good analogy. Most cars work in roughly the same way. Most software does not.
Software engineering is a diverse enough topic that you can have two "software engineers" who, aside from very broad general concepts like control flow and modularity, have very little overlap in their areas of expertise. Developing microcontroller firmware requires a very different set of skills and knowledge to building an ML model in R.
Most pieces of software require zero knowledge of the inner workings of, different implementations of, or even existence of a b-tree structure in order to be able to successfully create, understand and maintain them. Let's not gatekeep by telling people they're not real software engineers unless they understand and can recite an arbitrary set of mostly useless topics.
It's actually not a good analogy because most mechanics nowadays specialize. You don't have an engine guy do an automatic transmission rebuild and you don't have your local car dealer do a coil-over 4 link suspension upgrade on your Jeep.
This is exactly analogous to software in that you don't need to know deep algorithms to build CRUD web apps. They are a different part of the machine and closer to the business domain. Looking for deep CS over skills like requirement gathering, collaboration, information theory gives false signals on competency for the task at hand.
The reality is front end, backend, embedded, desktop etc. etc. all have different requirements on the skill sets they need to be successful. People gain the skills they need via the process of working, then we have this ritual of interviewing where we act like all these things that never get used in their trade are so so important to know.
The direct analogy is I am hiring an engine guy,he will never touch a transmission. The guy knows fuel maps, timing and compression ratios like the back of his hand, but I keep insisting that he tell me how the sun gear of the transmission engages the planetaries and in what sequence because he has to know this to be any good as an engine guy and come to the conclusion in my head that if he does not know transmissions it is a signal that he is not fit to be an engine guy.
>The guy knows fuel maps, timing and compression ratios like the back of his hand, but I keep insisting that he tell me how the sun gear of the transmission engages the planetaries and in what sequence because he has to know this to be any good as an engine guy and come to the conclusion in my head that if he does not know transmissions it is a signal that he is not fit to be an engine guy.
Sure, but that's not what happened. The real story, in contrast to the tweet, is that he didn't really know what a b-tree was. And if you're hiring an engine mechanic and they tell you they don't really know what a transmission is, well, that's a pretty big red flag.
Agreed and I don't know what he was applying for, I was just highlighting that this happens a lot in our industry where we misapply (not saying everyone in the tech industry) what we do with the ritual of insisting that applicants are worthy via a cargo cult process of ensuring that they too have the smartest guy in the room mentality.
I hate to entertain this bad analogy further than necessary, but knowing what a gearbox is in the field of cars is not even remotely near the same level as knowing what a b-tree is in the field of software engineering.
I guess we'll just have to disagree. They're a pretty basic data structure that's used quite often to solve a class of problems. And they're not that hard to learn. How they work is pretty simple and the reason to use them is pretty easy to grasp. I would say that there are few good software engineers out there that aren't clear on what they are at a basic level.
You don't need to know what a b- tree is, just a binary tree.
The question was about a simple binary tree, which is really trivial, even you have no idea of b-tree's and you never inverted a binary tree yet.
The dick part might be true, esp. after getting 7 interviews.
so I doubt the knowledge of b-tree's are that important for 90% of the users/people/developers.
heck I know how to write a multipart parser/formatter, which I doubt that many people do. especially people who know how a b-tree works. well most people which do know how a b-tree works, do not know when to use it.
- acknowledges and understands the problems and
- could certainly fix them if paid a Google-sized salary
But he won't dance to the tune of the "Cracking the Coding Interview" juggernaut so to heck with him. Better to spend time memorizing the Floyd Cycle Detection algorithm than produce useful code.
( OK, I may be a bit bitter )