Principles for designing interfaces — whether REST endpoints, component inputs, or module boundaries — that minimize what callers need to know while keeping implementations free to evolve.

Engineering craft is the accumulated discipline of writing, organizing, and maintaining software well — spanning code design, tooling fluency, communication, and the judgment to know when technical excellence actually changes outcomes.

Software architecture shapes how systems behave under pressure, how teams reason about codebases, and how much complexity accumulates over time — spanning module design, state management, deployment topology, and the feedback loops that keep all three honest.

Software engineering spans craft, process, and judgment — how code is structured, tested, reviewed, deployed, and maintained — and the sources collected here collectively interrogate each layer as AI tooling reshapes who does what and why.