3 ms·
A lot of people say that they never encounter leetcode-like problems in real life and therefore they are silly. Am I an outlier? I feel like I actually encount
by Kim_Bruning 4y ago
A lot of people say that they never encounter leetcode-like problems in real life and therefore they are silly.
Am I an outlier? I feel like I actually encounter these kinds of things fairly often, or at least the insights that they represent. (Eg: this week I'm implementing a simple path-finder to deal with a sliiightly overgrown state machine from a vendor. )
So - at least because of that - I tend to think of leetcode problems as more or less a slightly harder and more practical fizzbuzz. Complaints about leetcode do tend to mirror complaints you read about fizzbuzz.
Am I being strange here? Perhaps not. I figure there's at least two or three ways to pass a leet-code-like test: Either you just happen to have just done a bunch of marginally interesting programming somewhere in your past (which is probably what the test was designed for?), OR you did a study in college that ideally allows you to avoid the worst parts of the school of hard knocks (also ~fine), OR you explicitly practice for the test.
I suspect Goodharts law might be at work here: In some cases the measure has become the target.
- urthor 4y agoThey occur primarily in certain types of performance intensive back-end programming. What do you tell a React developer? You're going to need Knuth-Morris-Pratt to center a div? 95% of software jobs involve using a library for algorithm problems.
- 331c8c71 4y agoThe history has it that the git prototype was written in about a week. If everyone is so familiar with algos and data structures nowadays why don't I see good and novel solutions popping up here and there? Is that I'm blind? Or is it that the set of approachable impactful problems has been exhausted? Or all the innovation happens in closed source/saas space?