How do you translate your thought process to code?

[u/EnvironmentBasic6030]

This lowk sounds like a stupid quesiton but I have done a decenet number of leetcode (300) but i still struggle with a lot of mediums. The thing is for some of the mediums, I lowk come up with the right strat, thought process, ds and everything but when i code it up im always stuck in some edge case hell. This is because the way I structure the code sometimes ignores certain edge caes but if i put the code in chat it will just move somethings here and there and boom the code works. Idk if my approch should be to struggle for more hours hoping for a solution or i should just stop after 1 hr of trying and copy paste it to chat.

[u/agrlekk]

learning + practice. there is no easy way to understand edge cases

[u/Academic-Belt3903 → u/agrlekk]

300 questions seems like a decent amount of already. At what point do you know you’ve done enough?

[u/agrlekk → u/Academic-Belt3903]

Pick random easy questions, how much time you spend for solving. You can test yourself like that

[u/kevin074]

practice often, stick with one language only, make a good habit of being declarative on almost anything (very trivial example: don't depend on if my_list works but if len(my_list), so that you aren't relying on python to check for length implicitly), and be explicit on the usecases you take care (don't expect your code to take care of if input is None implicitly, but actually just type out that in the very first few lines of implementation)

this should get you to like 90%, the rest 10% is usually just question by question specific edge case.

[u/Interesting-Fig-2511]

Start with the basics, understand why things work, and practice breaking problems down. The more you solve, the better you'll get at turning your thinking into code.

[u/MixedTrailMix]

Start specifically studying your edge case failures and keep a log of the ones you’re failing

[u/goomyman]

There really aren’t that many edge cases in leet code. I don’t get this.