Engineering craft covers the habits, patterns, and safeguards that separate code that works from code that holds up. The sources here approach it from four distinct angles, but share a common thread: precision in design pays forward.

Crafting Interpreters represents craft at its most foundational. Robert Nystrom builds two complete Lox interpreters, one in Java and one in C, and the project’s build system weaves code and prose together into a single artifact. The dual-implementation approach is a deliberate teaching choice: the same language realized in two runtimes exposes where complexity lives and why it lives there.

At the shell level, Shell Tricks That Actually Make Life Easier makes the case that Readline bindings, history search, brace expansion, and script safety flags are not conveniences but safeguards. Knowing set -euo pipefail and process substitution is the difference between a script that fails loudly and one that silently corrupts state.

A Better Way to Build Angular Components applies the same principle to component architecture. Components bloated with dozens of inputs accrete because adding a flag is faster than refactoring, but the Composite Components pattern, moving features into directives and sub-components, keeps each concern encapsulated and the public API legible.

Craft also means understanding the infrastructure you depend on. What Happens If a Merge Queue Builds on the Wrong Commit documents a GitHub merge queue bug that silently rewrote main by constructing temp branches from stale divergence points. The architectural lesson is concrete: never push temp branches to main, and design systems so failure modes are visible rather than quiet.