Engineering

Engineering is the stream that treats systems-building as a contemplative discipline. The good engineer is a kind of patient reader: of code, of tolerances, of the gap between what was specified and what was actually built. The mistakes a system will make in production are largely visible at the specification stage, to anyone who slows down enough to look.

What Engineering refuses: the productized version of itself, in which any serious problem is presumed to be solvable by a sufficiently clever framework. Frameworks are an inheritance; they encode prior choices, some of which were wrong, and the engineer's job is to know which ones.

The writing under Engineering is in the tradition of the field notebooks and case studies — close to the metal, specific about what worked, specific about what didn't. There is little appetite, here, for the architecture-astronaut register that has dominated software writing for the last decade. A working system is a stronger argument than a clean diagram.

There is a second discipline under Engineering that is harder to name: the practice of choosing, deliberately and well, what not to build. Every system carries a cost the spec does not show, and most of the work of a mature engineer is in deciding, against pressure, what to leave undone.

The stream cross-tags often with Sound (acoustics and instrumentation are engineering problems) and with Mind (specification is a writing problem). The four streams are not partitions; they are angles.