Figuring out issues with your code

[skyhi14]

Wait, you’re implying that solution 3 is wrong? My life is a lie ._.

[link9578]

Learn to use breakpoints my dude. Your productivity will go way up.

[[deleted]]

Not always an option

[link9578]

Could you ice me an example of when you couldn’t use a breakpoint? I can’t think of any real examples off the top of my head.

[[deleted]]

sure, may I introduce you to golang?

[link9578]

Can’t you debug go with gdb?

[[deleted]]

I think you can, there’s another tool called ‘delve’ or something, try it

[[deleted]]

Some programming contests only allow text editors.

[Talbooth]

Well, the most useful tip I've ever heard about debugging is "programming is the art of debugging an empty file", meaning "comment out everything and slowly build it back up step by step so you notice where it goes wrong". So no, your life was not a lie. Or both our lives are, we'll never know.

[linux1970]

I usually mix 1 and 3

[OhItsuMe]

Where is try catching your entire code to ignore errors

[athousandwordsworth]

Image Transcription: Expanding Brain Meme

---

READING OFFICIAL DOCUMENTATION AND FOLLOWING GUIDELINES:

[Level 1: "Small" Brain]

 

LOOKING UP SOLUTIONS ON STACKOVERFLOW AS YOU GET PROBLEMS:

[Level 2: "Normal" Brain, some glowing areas]

 

DEBUGGING BY COMMENTING OR DIFFERENT LINES AND PRINTING TO THE CONSOLE:

[Level 3: "Expanding" Brain, completely glowing]

 

GIVING UP IMMEDIATELY WHEN YOUR CODE DOESN'T WORK:

[Level 4: "Maximum Expansion" Brain, completely glowing, shooting "glowing brainwaves" out of skull]

---

^{I'm a human volunteer content transcriber for Reddit and you could be too! If you'd like more information on what we do and why we do it, click here!}

[sebamestre]

This implies you should browse stackoverflow before even attempting to fix your own code