Intent before motion
We ask why before choosing how. Every dependency, abstraction, and service must earn the understanding it consumes.
The way of the craft
The Kode-dō
Software is not mastered through syntax alone. It is mastered through judgment, repetition, failure, observation and transmission.
Kode-dō // The way
Principles for deciding.
Kode-dō guides how software is designed, built, operated, and maintained. It does not provide every answer; it provides direction when answers conflict.
Kode-fu // The practice
Techniques for acting.
Kode-fu grows through repetition, failure, teaching, and deliberate improvement. It turns values into observable habits.
Principles without practice become dogma. Practice without principles becomes chaos.
The complete way
The Manifesto
Not commandments. Commitments to test in the work.
Clarity before display
Code is read under pressure and changed by people not yet present. Legibility is an operational feature.
Evidence before confidence
Tests, telemetry, and review turn personal certainty into knowledge the team can challenge.
Recovery before pride
We plan rollback, contain failure, and protect users before defending an implementation.
Understanding before replacement
Systems that survived know things. We investigate their history before erasing their shape.
Transmission before status
Knowledge gains value when it travels. Teaching is part of completing the work.
Practice without finish
Mastery is not a title. It is the habit of observing, adjusting, and returning to the fundamentals.
Foundational forms
The Seven Forms
Write with intent
Every abstraction, dependency and line of code should have a reason to exist.
Prefer clarity over cleverness
Code is not a contest of tricks.
Test before battle
Tests are training before confrontation with production.
Respect the legacy
Before replacing a system, understand why it survived.
Observe the unseen
Logs, metrics and traces reveal what the code does not tell you.
Roll back without shame
Recovery is mastery, not defeat.
Share the knowledge
A master who does not teach creates dependency, not a team.
The Kode Oath
I will not worship complexity.
I will not hide failure.
I will not blame the user before reading the logs.
I will leave the codebase better than I found it.