3 ms·
Not every day, but my experience is at least every month-quarter. And since you're not primed like in an interview context these ideas need to be inside your wh
by Hermitian909 5y ago
Not every day, but my experience is at least every month-quarter. And since you're not primed like in an interview context these ideas need to be inside your wheelhouse to spot them within a business context. I would not describe myself as particularly technical for my org and in the past year I've made use of the following at work:
-Depth first search
-Binary Search
-Topological Sort
-Dynamic programming in a graph context
-Union Find
-Merkle Trees
-Fenwick (binary indexed) trees
Maybe I'm in an unusually technical area but it doesn't feel that way talking to my colleagues.
- Philip-J-Fry 5y agoYes, and there's plenty of times in my work where I've put algorithms to good use. But out of all those algorithms how many could you regurgitate onto a whiteboard given 5 minutes to do so? Knowing the use of each algorithm is good enough. You don't need to know the implementation until you want to use it. And nowhere in your day to day work is this going to be with no internet access or reference. So why do interviewers suggest this is the case? Why aren't they just happy with you describing how a Merkle Tree can solve a particular issue. Why do you need to write that down?