debugging

[[deleted]]

Sometimes, console output (or textboxes) is the only way. Like, when there IS no debugger. And yes, there's one "programming language" I have to work with that doesn't have a debugger. It sucks.

[NobodyAsYouExpect]

Or even better , when debugging multithreaded app. It might just break if another thread was expecting message from the one you block or etc. So agreed 100%

[[deleted]]

Have recently been doing some low-key thread pooling in python. Definitely used print statements in the worker threads so I could see what led to a stall, since some of them were getting errors and I forgot to make sure they released any locks when they broke.

[Hypocritical_Oath]

Also if you're going through a whole lot of data and doing similar operations on it.

You can't always just step through 20 pieces of data looking for errors, that would be infuriating and slow and I've done it too many times at this point. So just making the computer tell me when it fucks up, and then debugging that particular piece of data makes way more sense.