The Code Worked Differently When The Moon Was Full
tl;dr: Scott walks us through "an interesting and insidious bug," based on a time calculations. This type of bug "can often show themselves later when view through a longer lens and scope of time," and "can show up a lot later than expected."
featured in #256
Should You Estimate Bugs?
tl;dr: There are a few methods of bug estimation, e.g.: (1) Dedicated time per sprint (2) Default estimation, e.g. 1 day/bug (3) Estimation with historical data (4) No estimation. Author argues that company size should affect which approach to go for.
featured in #238
Reasons Why Bugs Might Feel "Impossible"
tl;dr: Julia outlines 5 reasons why bugs might feel impossible to solve, each of which is explained in detail: (1) The bug is hard to reproduce. (2) You don’t understand the overall system well. (3) It’s hard to get data about the bug. (4) One of your assumptions is wrong. (5) The bug is really complex.
featured in #233
The Weirdest Compiler Bug
tl;dr: "There are approximately 7.5x10^18 grains of sand on Earth. This story is about finding changes in an equation that has a difference of approximately 1e-18 out of hundreds of billions of calculations."
featured in #224
Ultimate Guide To Python Debugging
tl;dr: Using print statements is "far from ideal and there are much better ways to find out what's wrong with your code," explored in this article.
featured in #186
When Debugging, Your Attitude Matters
tl;dr: Julia started to believe that it was impossible to understand basic CSS concepts, impeding her own ability to learn. After shifting her attitude, she saw a major difference in her ability to learn.
featured in #179