Classifying Bug Reports With ChatGPT
- Rafael Quintanilha tl;dr: Rafael creates an automated workflow that: (1) Triggers on new bug reports. (2) Uses ChatGPT to classify the report based on the user description. (3) Updates the priority accordingly. (4) Sends a Slack notification if and only if the bug is deemed as Urgent.featured in #504
featured in #466
67 Weird Debugging Tricks Your Browser Doesn't Want You to Know
- Alan Norbauer tl;dr: "A list of useful, not-obvious hacks to get the most out of your browser’s debugger. Assumes an intermediate-level-or-higher understanding of the developer tools." These include logpoints / tracepoints, changing program behavior, quick and dirty performance profiling, using function arity, using time. And more.featured in #465
featured in #453
A Systematic Approach To Debugging
- Nicole Tietz-Sokolskaya tl;dr: Nicole’s process involves six steps, each of which she expands on: (1) Identifying the symptoms. (2) Reproducing the bug. (3) Understanding the systems. (4) Forming a hypothesis about the bug's location. Instead of randomly searching through the code, the author suggests forming a hypothesis about where the bug might be located. This narrows down the search and makes the debugging process more efficient. (5) Testing the hypothesis. (6) Fixing the bug. "If you don't understand the bug behavior, you have no hope of knowing if you've fixed it or not."featured in #448
Invariants: A Better Debugger?
- Marc Brooker tl;dr: Marc emphasizes the use of invariants, conditions that must hold true during or after code execution, as a powerful debugging tool. Through examples, the author illustrates how developers can use invariants to reason about complex algorithms and distributed systems. Invariants offer a deterministic, repeatable way to understand and ensure correctness, making them a valuable alternative to traditional debuggers.featured in #437
12 Debugging Tools I Wish I Knew Earlier
- Jordan Cutler tl;dr: The first 2 are: (1) Git bisect: Run you through a binary search process between the “good commit” and the “bad commit” until it finds the commit the bug started happening. (2) “Binary search commenting”: Commenting out sections of the code and replacing it with a hardcoded value to narrow in on where the problem is.featured in #434
The Curious Case Of A Memory Leak In A Zig Program
- Krut Patel tl;dr: “This is a small exposition on an unexpected "memory leak" I encountered when writing a Zig program. We will mainly focus on a very simple allocation pattern and see how it causes a "leak" when using a particular allocator from Zig's stdlib.”featured in #399
featured in #397
featured in #395