3 ms·
I think raw DSA has its place but shouldn't be 100% LC style: too isolated and abstract. You can probably learn more by wrapping it as a tiny 'project' note: n
by intelVISA 4y ago
I think raw DSA has its place but shouldn't be 100% LC style: too isolated and abstract.
You can probably learn more by wrapping it as a tiny 'project' note: not a take home -- just a DSA/LC style 'problem' diguised inside a git repo. I'd rather see 2Sum with a Cargo.toml in a repo, seeing them scaffold this in the lang of their choice, or within an existing codebase.
Justifying the full end-to-end "how is this going to be deployed and maintained", "how would you test X" is a bit more informative than "please repeat Djikstra's algorithm into the void".
Of course, being good @ LC in isolation is still a proxy for (math) intelligence perhaps unpopular - but in SWE being smart isn't enough, you gotta grift, ship or hustle your way through; thinking is mostly optional.
- josephg 4y agoYeah I agree 100%. A good technical interview should involve a lot of different parts. Some programming, some conversational. Essentially, there's 100 different things you need to know to do your job well. The job of a good technical interview is to give you a (biased) sample from those 100 elements of knowledge. So, some practical programming work. Some conversational - "how is this going to be deployed and maintained". Etc.