3 ms·
I agree with a lot of what you're saying, but I think we probably disagree when it comes to leetcode. One thing I'll note is that in my experience, companies im
by everdrive 2y ago
I agree with a lot of what you're saying, but I think we probably disagree when it comes to leetcode. One thing I'll note is that in my experience, companies implicitly do not _want_ you to work at too high of a level; they fill up your hours until there is no free time, prevent you from returning to older tasks or projects to improve them, and more or less require "good enough" solutions at best.
This isn't necessarily meant as a complaint, but this is yet another way in which leet code may not really fit the job that's being performed; the company is attempting to get as much work done as possible and for whatever reason is not very incentivized to ensure that the work is done to a high standard. In other words, the super complex leet code sorts of techniques will just never in practice be utilized.
Now to your point, whether or not you find yourself in this situation is going to depend on your job and your company.
- sfn42 2y agoI've never really done much leetcode. Might have done a problem here and there for fun but probably less than 10 total. I'm not sure whether people literally mean leetcode when they say leetcode, but I should probably clarify that I'm not specifically talking about problems from the leetcode website. I did once get a sort of quiz from codingame to complete at home(took like 15 minutes or so), but other than that I think my interviewers have made up their own problems. One was a class responsible for storing car data, being able to get them by plate number and stuff like that. Recently I did one where I basically implemented a tax calculator, calculating bracket tax and stuff like that. The general format has been a class with method stubs, and a corresponding test class. The assignment is basically make the tests pass. I think that's a good format. Allows you to write some real logic, sort of similar to what we do in daily work. The tax calculator was a bit math-heavy but still required some logic and some creative use of data structures to store tax brackets without hardcoding everything etc.