News for hackers. Stuff that matters.
Re:Technical Debt: Why it'll ruin your software by SCHiM on Friday October 23, 2020 @02:34PM (#24872429)
And how about highly congested multi threaded programs?

I've got a program with log statements like that all over the place. Since stepping through it with a debugger would not even be possible. My IDE takes care of hiding the debug statements, since they're all encapsulated in different regions and if-def statements to log different types of things.

Re:Technical Debt: Why it'll ruin your software by coddle-hark on Friday October 23, 2020 @02:56PM (#24872633)
Isn’t that what tracepoints are for though?

Flipping your argument, you’re basically saying that you can’t debug multithreaded code if the program doesn’t log.

Re:Technical Debt: Why it'll ruin your software by SCHiM on Friday October 23, 2020 @03:14PM (#24872797)
I certainly wouldn't want to debug this ball of mud if there were no log statements, no :)

But, I think we're depending on different programs in our workflow. I much prefer a logfile with statements that focus on what I want to inspect at the time.

I'm quite proficient with debuggers on both Windows and Linux, but I tend to use them less when dealing with my own multi-threaded code.

Re:Technical Debt: Why it'll ruin your software by merb on Friday October 23, 2020 @06:53PM (#24875206)
that works maybe with multi threaded code but not with greenthreads that are all over the place. the calls stacks are a pain in the ass.