<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Debugging on Jake Worth</title><link>https://jakeworth.com/tags/debugging/</link><description>Recent content in Debugging on Jake Worth</description><image><title>Jake Worth</title><url>https://jakeworth.com/twittercard.png</url><link>https://jakeworth.com/twittercard.png</link></image><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 03 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://jakeworth.com/tags/debugging/index.xml" rel="self" type="application/rss+xml"/><item><title>Get Better at Debugging by Making Predictions</title><link>https://jakeworth.com/posts/get-better-at-debugging-by-making-predictions/</link><pubDate>Tue, 23 Sep 2025 10:16:28 -0400</pubDate><guid>https://jakeworth.com/posts/get-better-at-debugging-by-making-predictions/</guid><description>&lt;p&gt;Shift to a proactive mindset by making predictions before any experiments in a debugging session.&lt;/p&gt;</description></item><item><title>Raise the "I'm Stuck" Flag</title><link>https://jakeworth.com/posts/raise-the-im-stuck-flag/</link><pubDate>Wed, 10 Sep 2025 14:16:30 -0400</pubDate><guid>https://jakeworth.com/posts/raise-the-im-stuck-flag/</guid><description>&lt;p&gt;Consider this scenario. You&amp;rsquo;ve been given some work, and you&amp;rsquo;re stuck. Hours have become days. You&amp;rsquo;ve exhausted the internet. You&amp;rsquo;re starting to backtrack, delete work, and start over. Feeling defeated. To make matters worse, you haven&amp;rsquo;t told anybody.&lt;/p&gt;</description></item><item><title>Debugging Is a Story</title><link>https://jakeworth.com/posts/debugging-is-a-story/</link><pubDate>Tue, 09 Sep 2025 13:27:03 -0400</pubDate><guid>https://jakeworth.com/posts/debugging-is-a-story/</guid><description>&lt;p&gt;Today I want to talk about a way I think about debugging: as a story that we tell to ourselves and each other.&lt;/p&gt;</description></item><item><title>"Don't Stay Stuck" Digital Guide Launch</title><link>https://jakeworth.com/posts/dont-stay-stuck-digital-guide-launch/</link><pubDate>Tue, 12 Aug 2025 09:33:04 -0400</pubDate><guid>https://jakeworth.com/posts/dont-stay-stuck-digital-guide-launch/</guid><description>&lt;p&gt;I&amp;rsquo;m proud to announce the launch of my digital guide to software debugging, &lt;a href="https://jwworth.gumroad.com/l/dont-stay-stuck"&gt;Don&amp;rsquo;t Stay Stuck: A Debugging Guide for Rising Engineers&lt;/a&gt;!&lt;/p&gt;</description></item><item><title>Banishing "Random" for Better Software Communication</title><link>https://jakeworth.com/posts/nothing-is-random/</link><pubDate>Tue, 17 Jun 2025 12:19:04 -0400</pubDate><guid>https://jakeworth.com/posts/nothing-is-random/</guid><description>&lt;blockquote&gt;
&lt;p&gt;&amp;ldquo;I&amp;rsquo;m still getting this random 404.&amp;rdquo;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Want to sound pro? Banish &amp;ldquo;random&amp;rdquo; from your software engineering vocabulary.&lt;/p&gt;</description></item><item><title>Don't Guess</title><link>https://jakeworth.com/posts/dont-guess/</link><pubDate>Tue, 29 Apr 2025 09:30:56 -0400</pubDate><guid>https://jakeworth.com/posts/dont-guess/</guid><description>&lt;p&gt;This is a response to &amp;ldquo;Don&amp;rsquo;t Guess&amp;rdquo; from the excellent &lt;a href="https://endler.dev/2025/best-programmers/"&gt;&amp;ldquo;The Best Programmers I Know&amp;rdquo;&lt;/a&gt; by Matthias Endler. My goal is to crystallize my understanding of this trait.&lt;/p&gt;</description></item><item><title>Your Software Is Confusing</title><link>https://jakeworth.com/posts/your-software-is-confusing/</link><pubDate>Mon, 07 Apr 2025 10:16:44 -0400</pubDate><guid>https://jakeworth.com/posts/your-software-is-confusing/</guid><description>&lt;p&gt;If something in your software is confusing to a customer, it &lt;em&gt;is&lt;/em&gt; confusing.&lt;/p&gt;</description></item><item><title>"I Don't Understand" Debugging</title><link>https://jakeworth.com/posts/i-dont-understand-debugging/</link><pubDate>Thu, 13 Feb 2025 09:52:51 -0400</pubDate><guid>https://jakeworth.com/posts/i-dont-understand-debugging/</guid><description>&lt;p&gt;My definition of &amp;ldquo;I don&amp;rsquo;t understand&amp;rdquo; debugging.&lt;/p&gt;</description></item><item><title>Find Every Debugging Trail Marker</title><link>https://jakeworth.com/posts/dont-skip-debugging-steps/</link><pubDate>Mon, 17 Jun 2024 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/dont-skip-debugging-steps/</guid><description>&lt;p&gt;If you&amp;rsquo;ve ever watched me debug, you might think I&amp;rsquo;m moving slowly. That&amp;rsquo;s
because I try hard to find every marker on the debugging trail. I believe this
is one of the most valuable skills in debugging.&lt;/p&gt;</description></item><item><title>Thinking of Bugs in Classes</title><link>https://jakeworth.com/posts/thinking-of-bugs-in-classes/</link><pubDate>Sun, 03 Sep 2023 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/thinking-of-bugs-in-classes/</guid><description>&lt;p&gt;We spent the time writing tests, and yet, a bug survived. Should we just stop
writing tests? No, but we should maybe write better tests, and think about them differently.&lt;/p&gt;</description></item><item><title>The Case Against "Try This" Debugging</title><link>https://jakeworth.com/posts/the-case-against-try-this-debugging/</link><pubDate>Mon, 26 Jun 2023 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/the-case-against-try-this-debugging/</guid><description>&lt;p&gt;In many group debugging sessions I&amp;rsquo;ve joined, a major technique being
deployed is something I call &amp;ldquo;Try This&amp;rdquo; debugging. In this post, I&amp;rsquo;d like
to talk about this anti-pattern, and consider a better way.&lt;/p&gt;</description></item><item><title>You Can't Change Nothing</title><link>https://jakeworth.com/posts/you-cant-change-nothing/</link><pubDate>Fri, 21 Oct 2022 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/you-cant-change-nothing/</guid><description>&lt;p&gt;I saw a meme this week: a person debugging code, &amp;ldquo;My code doesn&amp;rsquo;t work.
Let&amp;rsquo;s change nothing and run it again.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;This is something that I&amp;rsquo;ve done. It seems pointless. But that&amp;rsquo;s not quite correct.&lt;/p&gt;</description></item><item><title>All My Best Debugging Tips</title><link>https://jakeworth.com/posts/all-my-best-debugging-tips/</link><pubDate>Fri, 05 Aug 2022 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/all-my-best-debugging-tips/</guid><description>&lt;p&gt;This is a list of all the best debugging tips I&amp;rsquo;ve picked up over the years. Some of these might seem obvious, yet we forget them when it
counts. Debugging is a skill. You have to bring every tool you have to the job.&lt;/p&gt;</description></item><item><title>Recognizing and Repairing a Broken Mental Model</title><link>https://jakeworth.com/posts/broken-mental-model/</link><pubDate>Mon, 25 Jul 2022 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/broken-mental-model/</guid><description>&lt;p&gt;Perhaps you&amp;rsquo;re familiar with this scenario: you&amp;rsquo;re debugging and
&lt;a href="https://jakeworth.com/posts/dont-stay-stuck/"&gt;stuck&lt;/a&gt;. You&amp;rsquo;ve Googled, read some blog posts and docs.
You return to your search engine, type some characters, and then something
strange happens: the search engine autocompletes your question, and the results
are all purple because they have been visited by you. I&amp;rsquo;ve come to recognize
this moment as always a symptom of a broken mental model.&lt;/p&gt;</description></item><item><title>Logging an Object in JavaScript</title><link>https://jakeworth.com/posts/logging-an-object/</link><pubDate>Thu, 07 Jul 2022 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/logging-an-object/</guid><description>&lt;p&gt;When printing a JavaScript value to the console, I suggest using an object
literal over the raw value.&lt;/p&gt;</description></item><item><title>How to Write a Perfect Bug Report (With Template)</title><link>https://jakeworth.com/posts/a-perfect-bug-report/</link><pubDate>Mon, 13 Jun 2022 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/a-perfect-bug-report/</guid><description>&lt;p&gt;Bugs are part of software. Reporting bugs well is a necessary skill in an ever-growing number of job titles. In this post, I&amp;rsquo;d like to explain how to write a perfect bug report and offer some bug-reporting best practices.&lt;/p&gt;</description></item><item><title>Make a Prediction</title><link>https://jakeworth.com/posts/make-a-prediction/</link><pubDate>Wed, 08 Jun 2022 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/make-a-prediction/</guid><description>&lt;p&gt;Imagine you&amp;rsquo;re debugging, and you&amp;rsquo;re &lt;a href="https://jakeworth.com/posts/dont-stay-stuck/"&gt;stuck&lt;/a&gt;. I have a technique that&amp;rsquo;s
going to help. Think of an action you might take. Predict what will happen
when you take that action. Take the action. Check if you were right or wrong,
consider that information, and repeat.&lt;/p&gt;</description></item><item><title>How to Identify the Breaking Commit With Git Bisect</title><link>https://jakeworth.com/posts/find-the-breaking-git-commit/</link><pubDate>Tue, 17 May 2022 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/find-the-breaking-git-commit/</guid><description>&lt;p&gt;Some code is broken, and you can&amp;rsquo;t figure out why. Maybe there are a lot of changes, and identifying the breaking change seems impossible. Or, maybe you&amp;rsquo;re curious about how things break in your organization. The tool you need is &lt;code&gt;git-bisect&lt;/code&gt;.&lt;/p&gt;</description></item><item><title>The Problems With Code Screenshots</title><link>https://jakeworth.com/posts/on-code-screenshots/</link><pubDate>Tue, 19 Apr 2022 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/on-code-screenshots/</guid><description>&lt;p&gt;Screenshots of code are common in developer communication, but they come with real drawbacks. Here&amp;rsquo;s why I try to avoid them.&lt;/p&gt;</description></item><item><title>How to Read a Stack Trace</title><link>https://jakeworth.com/posts/how-to-read-a-stack-trace/</link><pubDate>Tue, 05 Apr 2022 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/how-to-read-a-stack-trace/</guid><description>&lt;p&gt;A stumbling block for many people when debugging is reading the stack trace.
Today I&amp;rsquo;d like to discuss this important skill.&lt;/p&gt;</description></item><item><title>How Urgent Is This Bug?</title><link>https://jakeworth.com/posts/the-importance-of-a-bug/</link><pubDate>Wed, 30 Mar 2022 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/the-importance-of-a-bug/</guid><description>&lt;p&gt;I remember the first bug that I shipped to production. I was upset that I&amp;rsquo;d
broken something and was anxious to fix it. But I noticed something curious:
the calm demeanor of a senior mentor helping me. They refused to meet my intensity. While the world burned, they wanted to instead discuss the bug and its relative importance.&lt;/p&gt;</description></item><item><title>Debugging Tip: Learning From Bugs</title><link>https://jakeworth.com/posts/learn-from-it/</link><pubDate>Fri, 25 Mar 2022 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/learn-from-it/</guid><description>&lt;p&gt;You were &lt;a href="https://jakeworth.com/posts/dont-stay-stuck/"&gt;stuck&lt;/a&gt;, and now you aren&amp;rsquo;t. Congratulations! Before you move
on, it&amp;rsquo;s vital to stop and learn from it. It&amp;rsquo;s the best way I know to get
better and spare your mind for increasingly harder problems.&lt;/p&gt;</description></item><item><title>Don't Stay Stuck</title><link>https://jakeworth.com/posts/dont-stay-stuck/</link><pubDate>Tue, 01 Mar 2022 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/dont-stay-stuck/</guid><description>&lt;p&gt;We&amp;rsquo;ve all seen this: a frustrated coworker hunched over a computer after
hours, flailing alone against some impossible bug. Go home, coworker. Don&amp;rsquo;t stay stuck.&lt;/p&gt;</description></item><item><title>Before You Abort, Count to Ten</title><link>https://jakeworth.com/posts/count-to-ten/</link><pubDate>Tue, 15 Feb 2022 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/count-to-ten/</guid><description>&lt;p&gt;Here&amp;rsquo;s a trick that that has helped me as a programmer: before doing anything
major, like killing a process, stop and count to ten.&lt;/p&gt;</description></item><item><title>Why I Don't Point Agile Bug Tickets</title><link>https://jakeworth.com/posts/why-i-dont-point-bugs/</link><pubDate>Mon, 07 Feb 2022 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/why-i-dont-point-bugs/</guid><description>&lt;p&gt;When I create Agile bug tickets, I leave the story points blank. Why? Two reasons: pointing bugs creates the wrong incentives, and bugs are hard to estimate.&lt;/p&gt;</description></item><item><title>Bug Reports Are Gold</title><link>https://jakeworth.com/posts/bug-reports-are-gold/</link><pubDate>Sat, 15 Jan 2022 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/bug-reports-are-gold/</guid><description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Me&lt;/strong&gt;: Hey, I&amp;rsquo;m experiencing an issue with your software. Here&amp;rsquo;s a &lt;a href="https://jakeworth.com/posts/a-perfect-bug-report/"&gt;detailed bug report&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;SAAS Engineer&lt;/strong&gt;: What you&amp;rsquo;re describing isn&amp;rsquo;t possible.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Narrator:&lt;/strong&gt; &lt;em&gt;But it was possible.&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;This is a frustrating, unproductive snippet of a conversation I&amp;rsquo;ve had a few times in my
career. What can we learn? Treat bug reports like gold.&lt;/p&gt;</description></item></channel></rss>