Re:How to conduct a good programming interview
by edem on Monday September 11, 2017 @08:42AM
(#15218056)
This is not a counter-point. This is what I have said:
> You just can't do well in some contexts
This means that your project is either simple enough that you don't need to know advanced CS or someone on your project actually has that knowledge.
I've also said:
> I think it all boils down to having at least a decent ability in all areas involved in order to be able to be productive in all environments.
So it seems that you are barking up the wrong tree. My point is that you need to have decent knowledge of all related areas to your project in order to be able to meaningfully contribute and this statement still stands. If you write an useful CRUD application you don't have to know how a hashtable works.
The reason, as I see it, is simple: the engineering work the Principal Engineer and myself, with our juniors we mentor, do, is far more important than data structures and algorithms trivia. Once it gets to the point of deciding which of these to use the real problems have been solved already. Now, these choices aren't unimportant: the choice of a bad algorithm or data structure might cause problems, but they're choices that are in the main easy to understand and make when compared to the thought that goes in to the rest of the system.