The 42 Principles · Principle X
Readability Is Reliability
Clear communication, understandable systems, maintainable work, and respect for the person who comes next.
Readability Is Reliability
Code is read far more often than it is written.
Every engineer becomes a teacher the moment they commit code.
Readable systems reduce mistakes.
Readable documentation prevents outages.
Readable architecture shortens learning curves.
Write for the next engineer.
One day, that engineer may be you.
In Practice
- Prefer descriptive names.
- Document intent, not the obvious.
- Keep functions focused.
- Let structure explain itself.
Ask Yourself
Would someone unfamiliar with this system understand my intent?
Related Principles
Continue the idea.
These Principles share themes with Principle X.
Principle XVI
Documentation Is a Feature
Documentation as institutional memory, teaching, repeatability, recovery, and reduced dependence on individuals.
Read Principle XVI →Principle VIII
Practical Beats Clever
Clarity, maintainability, service, and choosing solutions people can understand and sustain.
Read Principle VIII →Principle XVIII
Respect the Next Engineer
Empathy, maintainability, context, clarity, and considering the person who will inherit your decisions.
Read Principle XVIII →Principle XXXVI
Every Product Should Teach
Products, tools, documentation, and interfaces that leave users more capable and less dependent.
Read Principle XXXVI →