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

Why can I read PLC code but not write it myself?

You can trace a ladder diagram someone else built. You understand why each rung fires. But the moment the screen is empty, your mind goes empty too. This is not a knowledge gap. You have the knowledge. What you are missing is practice at the harder act. Deciding what the machine should do, step by step, before any code exists. Reading rewards patience. Writing rewards decision. You have trained one skill and not the other. No framework will do this for you. You close the gap by writing badly, many times, until writing stops being frightening.

◆ 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
This is less a missing-facts problem and more a missing-habit problem, so coaching toward action outweighs instruction.
How the two dials adapt to you →
What’s really going on

You already know the logic. What you lack is the habit of starting. Reading shows you someone else's choices already made. Writing forces you to choose first. Stop waiting to feel ready. Open a blank rung and write one true condition. That is the whole skill.

🔒 What you’ll build togetherUnlock by starting
A movePick one small machine function you understand well — a conveyor start/stop, say — and write its logic from a blank screen, no reference open.
A moveWrite one rung at a time. Finish it, test it in your head, then write the next.
A moveWhen you freeze, write the plainest rule first: 'if X, then Y.' Refine it after, not before.
A moveKeep a file of five rungs you wrote yourself. Read that before new work, not someone else's code.
A moveSet a 20-minute timer and write without stopping to make it perfect.

What changes unlock by starting

  • You start writing logic without reaching for a reference first.
  • You finish small programs end-to-end, not just pieces.
  • You trust your own first draft enough to test it.
  • You feel steady opening a blank program file.
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.