Learning from Mistakes: Understanding Ad-hoc Logs through Analyzing Accidental Commits — mentioned by PaulHoule

Wed, 12 Feb 2025 18:22:41 GMT

Plenty. The difference is I'm using commercial tools (PyCharm, WebStorm, and IntelliJ) that have visual debugging that works. Now gdb from the command line is great for what it is, but a lot of people who use open source toolchains find that "it just doesn't work" when it comes to debugging. Myself, I think tests and debugging go together like peanut butter and jelly. That is, you use tests to set up a situation you want to debug, then you run the debugger. When you're all done you have a test that proves the bug was fixed. It might be less of a problem in the C++ world but I really like…

Paper and discussion history. A mention is not an endorsement.

Learning from Mistakes: Understanding Ad-hoc Logs through Analyzing Accidental Commits — HN submission

Sat, 08 Feb 2025 13:37:02 GMT

Understanding Ad-Hoc Logs Through Analyzing Accidental Commits

1 point; 0 discussion replies on HN. Paper and source history. A submission is not an endorsement.

Learning from Mistakes: Understanding Ad-hoc Logs through Analyzing Accidental Commits · HackerPapers discussions

Learning from Mistakes: Understanding Ad-hoc Logs through Analyzing Accidental Commits — mentioned by PaulHoule

Learning from Mistakes: Understanding Ad-hoc Logs through Analyzing Accidental Commits — HN submission