Re:It is humiliating to have to do LeetCode grinding for
by sfn42 on Thursday November 28, 2024 @03:17PM
(#42268294)
I'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.
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.