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

I can inspect code now — why does complexity still trip me up?

You can already spot a bug. That part of the skill is done. But put a sprawling, tangled change in front of you and your team, and something else happens — everyone goes quiet, or everyone talks in vague feelings, and nobody commits to a clear verdict. That is not a failure of your eye. It is a failure of your method. You are asking your mind to hold ten decisions at once — this function, that dependency, this edge case, that assumption — and a mind that holds ten things holds none of them well. This is fixable today, and it is easier with the people beside you. Stop trying to judge the whole. Split it. Assign the pieces. Judge each one alone. Then come back together and let the parts build the verdict for you.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
Some to learn
1:1 with AureliusWith others (a Pod)
Some one-to-one
Practise with peers
The method itself (breaking complexity into judgeable pieces) takes little explaining; the change comes from practicing it under real pressure with your team until it becomes habit.
How the two dials adapt to you →
What’s really going on

The wall isn't your skill — it's your method. You're trying to judge an entire tangled system in one glance. No mind does that well, yours included. Break the thing into pieces small enough to judge alone, judge each one, then combine the verdicts. Choose the piece in front of you, not the whole.

🔒 What you’ll build togetherUnlock by starting
A moveBefore the pod reviews, break the change into its smallest decidable pieces — one function, one branch, one assumption — and write them down as a list.
A moveAssign one piece per person. Judge only your piece. Report what you actually see, not what you guess about the rest.
A moveThe moment you don't understand a piece, say so out loud. Do not fake understanding to keep pace with the group.
A moveAfter each piece is judged alone, bring the group back together and combine verdicts. Do not re-litigate the whole thing from scratch.
A moveChoose one real inspection this week and run this process start to finish, even if it feels slower at first.
PractiseSplit the Beast · a Pod of 4 · 30 min

What changes unlock by starting

  • You stop freezing when a change is large — you have a concrete first move instead of a blank stare.
  • Your pod inspects faster because judgment isn't bottlenecked on one person holding everything in their head.
  • Your feedback gets specific instead of vague — you name the piece, not just the feeling of unease.
  • You trust your own verdicts more, because you reached them piece by piece instead of guessing at the whole.

Related problems

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.