Talk it through with Aurelius
LibraryAureliusThe problem
Aurelius · Work & Leadership
Knowledge + Guidance

My code works, so why can't anyone else understand it?

You solved the problem. It runs. You call this done. But someone else — maybe you, in six months, half asleep — has to open this file and know what it does without asking you. That person is not in your head right now. You wrote for yourself only. This is not a skill you lack. You already think clearly enough to make the logic work. The missing piece is smaller and more honest: you have not yet chosen to serve a reader who is not you. Stop asking 'does it work.' Start asking 'can a stranger follow this fast, with no help from me.' That question changes what you write, line by line.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
Some to learn
1:1 with AureliusWith others (a Pod)
Mostly you & the coach
A little with peers
The person needs a few concrete habits (naming, structure, comments) plus real practice noticing their own blind spot toward the reader — so coaching carries slightly more weight than teaching.
How the two dials adapt to you →
What’s really going on

You are writing for the machine, not the person after you. That is the whole gap. The machine already understands you — it ran your code. Write your next function for a tired stranger at 2am. Name things plainly. Cut cleverness. That is the entire skill.

🔒 What you’ll build togetherUnlock by starting
A movePick one function you wrote this week. Read it out loud as if explaining it to someone who has never seen your code.
A moveRename every variable that does not say what it holds. If you hesitate on a name, that is the sign it is wrong.
A moveDelete every comment that explains 'what' the code does. Keep only comments that explain 'why' you chose this way over another.
A moveBefore you call anything finished, hand it to no one — imagine handing it to someone. Ask: what would they have to ask me? Fix that before you ship.
A moveSet a rule: no function longer than fits on one screen. If it does not fit, you are hiding decisions inside it. Break it apart.

What changes unlock by starting

  • You catch confusing code before someone else has to ask you about it.
  • You write names and structure that explain themselves, without extra documentation.
  • You build the habit of writing for a reader by default, not as an afterthought.
  • You finish work faster over time, because less of your future gets spent explaining your past.
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.