I have completed a streak of 1000 days on Leetcode.

Username checks out.

And you're still a crappy programmer

@atheist cope harder

Hey! Not a total ass kisser. Also, no copium, just skill.

Has it helped you on anything that isn’t interviews?

@ars1 Is it supposed to help anywhere else? It's very clear in it's objective to only help in interview, and as long as companies keep hiring like this, people will use this shortcut, People do lot of useless things in life but suddenly when it comes to grinding these puzzles they start looking for usecases.

@asskisser but why would you do it for 1000 days in a row? Are you in a perpetual cycle of changing jobs?

@ars1 These are daily challenges that leetcode provides, so just like you drink your coffee every morning, you can also solve these, I get it people find it daunting to solve these but as a Tsoding once said, you don't need to enjoy what you do, do it so often that it doesn't feel like chore anymore. So as I said, my life doesn't revolve around it, I do it to not lose touch.

kitty?

@asskisser Can we please change this ?

If the ceo of Microsoft Belgium uses copilot to do her job. (preparing presentations and stuff like that) Why would we as programmers not use any of that and google and stackoverflow during the interview ?

Chances are today that even the person that is doing the interview has used ChatGTP to make the questions.

Would you also hire a charpenter by his ability to put a nail in a beam without hammer or tools ?

@Grumm There are good ways to hire, like pair programming or debugging session or design discussion round, problem with those are they only work for experienced roles and require lot of investment into each candidate, if you want to do that you need to filter people who will reach that stage, filtering based on resume is hard, if everyone has required skills whom to chose, then it becomes a game of who can design better resume, or you give them some assessment, again you can't give take home assessment, so only remaining thing is random coding puzzles. I am not saying it's ideal to ask puzzles, but for companies with lot of bad applicants and for less experienced roles you can't judge based on aforementioned ways, For experienced roles I agree these puzzles have no place.

Interview will never reflect real job, you can have rounds where you can research online to find solution, which requires designing good problems as all basic ones will be leaked.

Don't Hate The Player Hate The Game

You must be pretty leet now

@asskisser But again, that is just crap and someone who can memorize leet code could potentially go to next rounds without knowing how to code.

At some point, the skill is how you as a programmer can see a problem and translate that into a working piece of code.

I have never done an interview where they asked to solve a leet code puzzle. (Ok, I haven't changed a lot) The first one hired based on a IQ test and I had the highest they saw in years.

The second one hired based on a real example. They didn't have a programmer in house. They asked to come and look at the code and see if I liked it or not :D

@Grumm Then both your experiences don't justify it's bad, IQ test is clearly worse way and calling everyone to see code is also not scalable. While it is possible someone memorizes 3000 problems without knowing how to code, a good interviewer should catch the bluff, it's not that hard, Interviews have always been about throw a problem and see how candidate reacts, Except some problems which are impossible without knowing particular trick, most should be approachable by someone who took CS class seriously, which is again why it shouldn't be asked to senior roles, it needs exposure which isn't there in daily job.

@asskisser Yes, I understand your point of view.

I have looked for fun to some 'google code interviews'... Is it really relevant that a candidate can code a full sorting algorithm from scratch and requires O(n) complexity. Compared to when you work, you just find the best sorting function of your language and use that. I have done some leed code, most I can manage it. But other not because in my work, it is very unlikely to have such situations.

But leed code challenges are fun :)

Same with school, we learned to code in Java and some patterns and stuff. Then you come in the real world and you use maybe 30% of what you learned. The other 70% you still have to do research, and find ways to do it. (I am still glad because we are not locked on a particular language. We learned how to program. Is it in python, c#, java, c++ ? that is no problem)