Structure before code
Understanding the problem and shaping the architecture come before implementation. Boundaries, naming and data flow are decided on purpose, so the system stays readable and predictable as it grows rather than being untangled later.



