How the work actually gets done: project write-ups, engineering decisions and the principles behind them.
This is where the work gets described rather than summarised: what a system had to do, which approach was taken, what turned out to be wrong, and what was changed as a result.
These write-ups exist because most technical marketing describes outcomes and skips the decisions. The decisions are the part that transfers — the constraint that ruled out the obvious approach, the assumption that survived until production, the piece rebuilt once the real data volume arrived.
Where a project is described in full, the corresponding case study carries the client context and the delivered result.
