ten-principles — Ten principles for good software

Overview

Ten principles, inspired by Dieter Rams, define what good code looks like. They are a contract for the style of the code: names, comments, structure, tests, and size. They are not a contract for architecture. The repo owns its architecture in ADRs and architectural principles. Follow those first. Do not use these principles to propose a new module, layer, or pattern.

Core principle: less, but better.

Write every response in ASD-STE100 Simplified Technical English. REQUIRED SUB-SKILL: use technical-english for the writing rules. If it is not installed, apply these rules inline: maximum 20 words for each sentence, active voice, imperative instructions, one meaning for each word, no idioms.

The three modes