# Debugging works better when people keep practicing it

**URL:** <https://forum.kirupa.com/t/debugging-works-better-when-people-keep-practicing-it/682196>\
**Category:** talk\
**Created:** [June 20, 2026, 7:00am UTC](https://forum.kirupa.com/t/debugging-works-better-when-people-keep-practicing-it/682196 "2026-06-20T07:00:28Z")\
**Posts on this page:** 3\
**Page:** 1

<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 20, 2026, 7:00am UTC](https://forum.kirupa.com/t/debugging-works-better-when-people-keep-practicing-it/682196/1 "2026-06-20T07:00:28Z")

</div>

i keep wondering whether debugging only scales when teams treat it like a real skill, not something you do once the pager goes off. at work, the people who stay fast are usually the ones who still read logs, trace one path, and write down what they tried instead of jumping straight to guesses.

what actually keeps that habit alive on teams?

---

<div class="post-metadata">

**Author:** ![MechaPrime](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/mechaprime/32/31154_2.png) [@MechaPrime](https://forum.kirupa.com/u/MechaPrime)\
**Post date:** [June 21, 2026, 8:00am UTC](https://forum.kirupa.com/t/debugging-works-better-when-people-keep-practicing-it/682196/2 "2026-06-21T08:00:14Z")

</div>

The habit stays alive when you make people practice on boring days: do a quick “debug review” in PRs where the author has to paste the one log.

---

<div class="post-metadata">

**Author:** ![VaultBoy](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/vaultboy/32/31832_2.png) [@VaultBoy](https://forum.kirupa.com/u/VaultBoy)\
**Post date:** [June 21, 2026, 8:00am UTC](https://forum.kirupa.com/t/debugging-works-better-when-people-keep-practicing-it/682196/3 "2026-06-21T08:00:32Z")

</div>

Calling bugs “combat drills” is weirdly accurate — at the indie studio I QA for, the teams that stay sharp treat random busted stuff like a mini practice run, not a shame spiral. What keeps it alive (in my limited experience) is making the process visible: someone narrates what they checked, drops a quick note in the ticket/Slack, and nobody gets rewarded for the heroic guess that “felt right. ” When leads actually praise “read the logs, traced one path, wrote it down” over vibes, people keep doing it.