Talk it through with Aurelius
Library›Aurelius›The problem
Aurelius · Work & Leadership
Knowledge + Guidance

Why do weird software bugs send me down a rabbit hole?

You handle most bugs without a second thought. It is the strange ones — the conflicts that match nothing you have seen before — that swallow your afternoon. You open one file, then another, then five, and three hours later you have learned much and solved nothing. This is not a gap in your skill. You already know enough to fix most of what you meet. What you lack is a pause — one moment, before you touch anything, where you decide what kind of fight you are in. Without that pause, every strange bug gets the same treatment: poking at it. Poking is not a method. It only feels like one, because you are busy. The fix is not more knowledge of your tools. You have enough of that already. It is a habit, practiced before the keyboard, not during it. Sort the problem. Then solve it. In that order, always.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
A little to learn
1:1 with AureliusWith others (a Pod)
Mostly you & the coach
A little with peers
The person already has the technical skill; what's missing is a repeatable habit of sorting before acting, which is built through practice, not instruction.
How the two dials adapt to you →
What’s really going on

You do not lose hours because the bug is hard. You lose hours because you start digging before you know what you are digging for. Stop. Name what kind of problem this is first — new territory, a false assumption, or two things colliding. Classify, then dig. Never the reverse.

🔒 What you’ll build togetherUnlock by starting
A moveBefore touching any code, write one sentence: what you expected, and what happened instead.
A moveName the category out loud: unfamiliar territory, a broken assumption, or a collision between two things that each work fine alone.
A moveSet a timer for twenty minutes of investigation only. When it ends, stop and write down what you have ruled out.
A moveAsk yourself every ten minutes: has my understanding of the problem changed? If not, you are digging, not learning. Stop and reclassify.
A moveBefore you search or ask for help, state your single best guess at the cause. Test only that guess — not five things at once.

What changes unlock by starting

  • You lose fewer hours to aimless digging.
  • You catch yourself the moment motion replaces thinking.
  • You build one sorting habit that works on any new conflict, not just this one.
  • You start trusting your own judgment on when to stop and reclassify.
One object, two jobs: a public answer to a real problem, and — the moment you start the chat — Aurelius’s live plan for your version of it.