engineering
keep the user outcome traceable through one current owner, explicit contracts, and the smallest maintained surface. precision comes before brevity.
contents
- engineering judgment
- boundary mapper refactor
- retiring a project's third-party namespace-alias exception
- shortest-domain vocabulary
- reader-first business code
- minimum maintenance surface
- bounded code units
- core engineering mindset
- agentic compounding
- authored code surface
- import composition
- clean code density
- complex conditions use named predicates
- function contracts
- navigational cost
- named type contracts
- one symbol per thing
- mapper extraction
- typescript compiler boundaries
- curly guru coding standards
- shortest exact names
- domain glossary