Documentation over decoration

Most engineering and technical portfolios reach for the same word: 'passionate.' It shows up in bios, in project intros, in the closing line of a case study that otherwise had nothing wrong with it. The word is doing no work — it's a placeholder for evidence the writer didn't have time to gather.

While rebuilding this archive, I spent a long time with a reference build for a mechanical and systems engineer whose site never once claims expertise. It shows a system diagram, lets you tap a component, and gives you the spec. It shows a before-and-after slider with a diesel-consumption number attached, not a description of 'significant savings.'

The lesson generalises past engineering. A frontend case study that says 'built a fast, accessible interface' is making the same unearned claim as 'passionate developer.' The fix is the same in both cases: replace the adjective with the artifact. Show the filter interaction instead of describing it as intuitive. Show the before-and-after of a cluttered navigation instead of calling the redesign 'cleaner.'

This is why every case study in this archive is built around the same four-part discipline borrowed from that reference: what the interface needed to do, why it was structured that way, what it actually looks like doing it, and what changed. Adjectives are optional. Evidence isn't.