Negationist's blog

Any advice on how to get better at reducing solutions?
By Negationist, history, 12 months ago, In English

By reducing solution, I mean taking some solution which is hard to code and turning it into something which is easier to code, or at least harder to mess up? I'm pretty good when it comes to getting hard ideas, but when the problem is easy but has cancer implementation/debugging if not well thought out before coding, I often end up idea solving a long time before getting ac. I've also noticed on OAs the problems that take me the most time are the implementation ones no matter how easy the idea is maybe 5-10x the time of idea problems, and on some OAs I've bombed just because I couldn't find a bug or something. Any of you guys have any problem lists that would help and/or advice on doing this type of thing better?

  • Vote: I like it
  • -1
  • Vote: I do not like it

»
12 months ago, hide # |
 
Vote: I like it 0 Vote: I do not like it

I know exactly what you mean brother.. I used to face same problem.. what has helped me a lot is writing the steps down like the algo on my notebook.. then write pseudocode.. and only THEN write the code for it.. It's time taking but helps a lot.. I make much less mistakes now.. I also always try to use functions wherever I can and try to reduce things using math formulas but you probably already know that. Once I have figured out a solution I try to sit back and stay calm and try to think of an easy step by step implementation instead of jumping right at coding. Untill I figure out an easy enough way I don't start coding.

→ Reply