2 ms·
And I think those “maker” types of roles don’t need a hard C.S. screen. But algorithms aren’t just about reimplementing the classics. There are points even in o
by abalone 7y ago
And I think those “maker” types of roles don’t need a hard C.S. screen. But algorithms aren’t just about reimplementing the classics. There are points even in ordinary “DB front end” type of work where understanding algos will affect how you scale. You may find you’ve just been getting away with brute force approaches because that data sets were small. You can go very far like that but there may come a day when it matters and then it will really matter.
- rolltiide 7y agoI don't disagree with you, and it all comes up after the 20 second standup and in the code reviews, not in the interview, and not in a two week long orientation Overfitting for the possibility that it might be necessary in a design choice is not the way to gatekeep candidates
- kthejoker2 7y ago...and when that day comes you call a specialist to handle the case and let your "ordinary" worker get back to work on the 99% of the job space she's qualified for? I find this very ironic: Hiring for suitability to handle edge cases is also a brute force approach that doesn't scale. A good algorithm optimizes for expe ted inputs and farms out cache misses and unexpected behavior to some other system.