>Memorizing stuff that any reference book can tell you is a waste of time and skill.
If you are ill, would you prefer a surgeon that will search on Google doing surgery, ore or one that knows how to do it?
Would you be happy to fly with a pilot that will search on Google how to land?
>And rest assured, there is no value in writing a binary tree for the business. As a matter of fact if one of my dev doesn't use off the shelf components for these kind of things they'd get a stern talking about time efficiency, security and the likes. Why would I go and stress that at a interview?
Of course, for trivial stuff you won't need binary trees. But you're wrong in assuming all software is trivial and all problems are solvable with library calls.
And even for trivial stuff it's important to know and understand the underlying principles and how software and infrastructure works. Otherwise you will take bad decisions like searching lists instead of hash maps. And bad decisions will cost your employer money. Sometimes a lot of money.
So yes, knowledge matters. And experience matters. And problem solving skills matter.
First of, you don't have the same urgency as a surgeon. Management might want you to think you do, but it's all smoke and mirrors. If you don't have equity and stakes aren't people lives, it's not even close.
Second, surgeon do spend time before surgery to freshen up procedures from references, as they see a lot of different things, and while the gist of everything are in memory, the specifics are reviewed with the team before operating.
Are you doing equivalencies out of TV show knowledge by any chance?
If you are ill, would you prefer a surgeon that will search on Google doing surgery, ore or one that knows how to do it?
Would you be happy to fly with a pilot that will search on Google how to land?
>And rest assured, there is no value in writing a binary tree for the business. As a matter of fact if one of my dev doesn't use off the shelf components for these kind of things they'd get a stern talking about time efficiency, security and the likes. Why would I go and stress that at a interview?
Of course, for trivial stuff you won't need binary trees. But you're wrong in assuming all software is trivial and all problems are solvable with library calls.
And even for trivial stuff it's important to know and understand the underlying principles and how software and infrastructure works. Otherwise you will take bad decisions like searching lists instead of hash maps. And bad decisions will cost your employer money. Sometimes a lot of money.
So yes, knowledge matters. And experience matters. And problem solving skills matter.