They force you think of o(n) and train you better than anything else on how to write your functions (but not how to organise them).

I have around 600 leetcode exercises solved, and there’s a big difference in skill between the person i was before leetcode and the person i am now.

They force you think of o(n) and train you better than anything else on how to write your functions (but not how to organise them).

I agree. I think it’s all about blind spots. A software engineer spends most of the time reading code, and the changesets they write most of the time are not algorithms or any fancy iteration beyond doing a vanilla for loop over a collection. leetcode-type exercises tend to invert that tendency, and present us with challenges which we would only rarely tackle. It’s a good exercise in the sense that it forces a type of usecase we don’t often use. Still, their practical usefulness beyond coding crossword puzzles is very limited.

Create a post

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person’s post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you’re posting long videos try to add in some form of tldr for those who don’t want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



  • 1 user online
  • 1 user / day
  • 1 user / week
  • 1 user / month
  • 1 user / 6 months
  • 1 subscriber
  • 1.21K Posts
  • 17.8K Comments
  • Modlog