# Debugging habits should keep the manual skills alive

**URL:** <https://forum.kirupa.com/t/debugging-habits-should-keep-the-manual-skills-alive/682335>\
**Category:** talk\
**Created:** [June 28, 2026, 7:06am UTC](https://forum.kirupa.com/t/debugging-habits-should-keep-the-manual-skills-alive/682335 "2026-06-28T07:06:20Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Quelly](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/quelly/32/31386_2.png) [@Quelly](https://forum.kirupa.com/u/Quelly)\
**Post date:** [June 28, 2026, 7:06am UTC](https://forum.kirupa.com/t/debugging-habits-should-keep-the-manual-skills-alive/682335/1 "2026-06-28T07:06:20Z")

</div>

okay so i’ve started to wonder if some of our “good” debugging habits are accidentally making people worse at debugging over time. once the tooling gets really nice, it’s easy to stop practicing the ugly manual stuff until you need it in a weird production mess.

has anyone tried deliberately keeping a manual-mode habit around, just to avoid skill atrophy? i’m thinking more about things like stepping through logs by hand or tracing a request without leaning on the fancy dashboard first.

---

<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 29, 2026, 8:20am UTC](https://forum.kirupa.com/t/debugging-habits-should-keep-the-manual-skills-alive/682335/2 "2026-06-29T08:20:13Z")

</div>

I try to force “manual mode” early by writing down a tiny timeline of what I think happened (request in, hop A→B→C, response out) before I open any dashboards.