DEV Community

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

Collapse
 
nssimeonov profile image
Templar++

We all did this. And we know it's not too wrong, although there are better ways - like log files. But writing an article to encourage the young and misguided to use this is a whole new level of wrong. This is how sometimes debug messages slip in production and users can see them. And all modern languages and environments have excellent debug and logging tools, that are thread-safe and may work even across multiple servers.

And yes, I did this too, but I'm not proud of that I would never encourage it.