I’m Bruce. I design software systems for a living, mostly around distributed architectures, payments, performance, and the occasional problem nobody particularly wanted to inherit.
What I enjoy most is understanding how things work — especially when they don’t. I like taking complicated systems apart, finding the assumptions hidden inside them, and putting them back together in a form that is easier to reason about.
Systems
I automate what deserves to be automated, optimize what actually needs optimizing, and try not to confuse technical elegance with usefulness.
For me, architecture is less about imposing structure from above and more about understanding relationships: where complexity really lives, which constraints matter, and which ones only exist because nobody has questioned them yet.
Fractal Architect
“Fractal Architect” is a name I use for the way I tend to work.
I often move between very different scales: from system boundaries and architectural models down to a slow query, an awkward protocol detail, a race condition, or a single line of code.
The scale changes, but the habit stays the same: look for patterns, understand the constraints, and reduce confusion without pretending complexity can always be removed.
Machines must be optimized.
Dreams must not.
Beyond the machine
Outside of work I write, build small and occasionally unreasonable software projects, study whatever has caught my attention that month, and spend an unhealthy amount of time thinking about motorcycles, books, plants and systems in general.
I’m interested in technology, but even more in what people do with it. Machines are there to remove friction, not to make life resemble one.