Field notes

Practical notes you can use tomorrow.

Written for someone who has a decision to make. Each note says what problem it helps you understand, who it's for and where it stops being useful.

Start here

Build something that worksLevel: Applied6 min read

A method for turning a tangled operation into something you can build against

Complexity is rarely the real problem. Undefined complexity is. A practical method for mapping a messy operation before you touch architecture.

Useful when: Turning a problem you understand into software people actually use.

What you can do next

Learning paths

All notes

Document before you decide4 min read

Document before you build — or you'll rebuild twice

Documentation is not what you write after the work. It is the work. A short guide for anyone about to start a process nobody has written down yet.

May 2026

Use AI with judgement5 min read

AI as copilot, not as replacement

AI compresses execution time. It does not decide what deserves to be executed. A note on where the leverage actually is — and where it isn't.

Mar 2026

Build something that works5 min read

From technician to systems architect: what actually changes

What changes when you stop fixing problems and start removing the conditions that create them — and how to tell which mode you're in.

Jan 2026

Where this stops: These notes describe how I work. They aren't legal, insurance or engineering advice, and they don't replace an inspection or a professional review of your specific situation.