Hi, I’m Nathan.
I’m a Salesforce architect and technical lead in Queensland, working in the kind of organisation where one decision touches a hundred developers and several countries.
I write here about architecture, AI and design, mostly the parts that happen between the strategy slide and the pull request. Expect standards, patterns, agentic engineering, and the occasional complaint about naming conventions. I also run Particle Consulting, for when the essays are not enough.
Views are my own. My employer has enough of its own.
How this site is organised
Every essay is filed by who should read it, not by what it is about. Topics still exist, but the altitude tells you whether an essay was written for you.
10,000 m
The boardroom
For CIOs, heads of, and anyone who signs off budgets.
3,000 m
The architecture
For architects and anyone who draws boxes for a living.
300 m
The delivery team
For tech leads, engineers and whoever carries the pager.
Ground
The code
For whoever actually has to type it.
Reading the gauge
Plenty of essays start high and land low. The little gauge next to each title shows the range, top to bottom. An essay is filed at the altitude where it starts.
Stays at 3,000 m
Written for one audience and stays there.
300 m to ground
Starts with the delivery team, ends in the codebase.
10,000 m to ground
The full descent. A decision made at the top that you will feel all the way down.
Short takes that affect everyone go in Current conditions, because some weather reaches every floor.