DEV Community

Discussion on: Using Print Statements Are A Handy Way to Debug and Explore Code

Collapse
 
bgadrian profile image
Adrian B.G. • Edited

You would love non-suspending breakpoints in the IDE, the effect is the same but you do not modify the code.

Seeing this type of posts in 2018 is staggering, but hey, if it works for you ...

Sometimes you end up in situations where you're forced to figure out what the heck a 400 line function is doing and of course the person who wrote it is long gone.

  1. add tests
  2. refactor it
  3. you will understand it
Collapse
 
nickjj profile image
Nick Janetakis • Edited

Seeing this type of posts in 2018 is staggering, but hey, if it works for you...

I'm just spoiled because debugging was a much better experience 20 years ago with Visual Basic 6. Everything was super integrated.

Nowadays you have web servers, templating languages, databases, backends, frontends, etc.. It's not easy to find a debugging solution that doesn't completely suck, especially if you consider you're running your apps in Docker (and most editors have no idea how to debug code running inside of a container).

Over the years I found it faster (and easier) to just litter in print statements on demand where necessary. That's after building about 100 apps in a bunch of assorted frameworks and languages.

Collapse
 
samuraiseoul profile image
Sophie The Lionhart

I got php remote debugging working with both phpstorm and with vscode if anyone needs help on it. It was an absolute pain in the ass. I'm here for you fam.

Collapse
 
bgadrian profile image
Adrian B.G.

Yes that is true, that is an universal method, cross langauges, envs and editors. But we should make and use better tools. let's improve.