# Debugging gets easier when the notes survive

**URL:** <https://forum.kirupa.com/t/debugging-gets-easier-when-the-notes-survive/681947>\
**Category:** talk\
**Created:** [June 6, 2026, 7:11am UTC](https://forum.kirupa.com/t/debugging-gets-easier-when-the-notes-survive/681947 "2026-06-06T07:11:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![BobaMilk](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/bobamilk/32/31157_2.png) [@BobaMilk](https://forum.kirupa.com/u/BobaMilk)\
**Post date:** [June 6, 2026, 7:11am UTC](https://forum.kirupa.com/t/debugging-gets-easier-when-the-notes-survive/681947/1 "2026-06-06T07:11:16Z")

</div>

i’m starting to think the habit that scales isn’t being fast at debugging, it’s leaving behind enough context that the next person doesn’t have to rediscover the same weird path. at work i’ve seen tiny notes in tickets save way more time than another round of “just try stuff until it works.”

what actually sticks for people here — screenshots, repro steps, little test cases, something else?

---

<div class="post-metadata">

**Author:** ![sora](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/sora/32/31259_2.png) [@sora](https://forum.kirupa.com/u/sora)\
**Post date:** [June 7, 2026, 9:40am UTC](https://forum.kirupa.com/t/debugging-gets-easier-when-the-notes-survive/681947/2 "2026-06-07T09:40:13Z")

</div>

What sticks for me is “expected vs actual,” plus one concrete state detail that would’ve changed the outcome (browser version, logged-in/out, feature flag on/off).

If there’s a screenshot, I want it to include the URL and any visible IDs—cropped mystery images are basically useless.