A collection of stated truths

An axiom does not prescribe behavior. It names what is true. Because it is declarative, it does not need to persuade with force. It stands. The posts beneath each axiom are consequences, not categories.

Read each path in sequence: foundational claim first, implications next, sharpest edge last. The structure is deliberate so understanding can accumulate rather than scatter.

  1. 1

    The cost of software is comprehension.

    Code that compiles is easy; understanding it is the hard part. Every line you write is a permanent tax on everyone who reads it. The measure of good code is not elegance or brevity. It's how quickly a new person can build a mental model of what it does and why.

    9 readingsEnter Axiom 1
  2. 2

    The value of software is optionality.

    Software is worth building because it lets you change your mind later. Every architecture choice should be made assuming you're wrong about what comes next. The purpose of design is not purity. It's keeping your options open so you can adapt when the world surprises you.

    5 readingsEnter Axiom 2
  3. 3

    Software takes the shape of the people who build it.

    Your architecture will mirror your org chart. Your team's communication patterns will become your codebase's structure. You cannot design your way out of a people problem. The hard constraints are not technical. They're human.

    7 readingsEnter Axiom 3
  4. 4

    Work in progress is not progress.

    A half-finished feature sitting in a branch is debt, not an asset. Finished work teaches you what's real. Only completed, deployed, measured work tells you whether you were right. Flow is more valuable than throughput.

    7 readingsEnter Axiom 4
  5. 5

    Action brings clarity.

    Speculation ends when you build something. Every guess remains a guess until it touches reality. The shortest path to understanding is the thinnest viable slice deployed and measured. Planning is useful; doing is essential.

    7 readingsEnter Axiom 5