About
I'm Archie.
A software architect writing about the systems that move money.
I work on financial systems — the unglamorous machinery behind payments, ledgers, and real-time money movement. I take positions on how these systems should be built, and I change my mind in public when the evidence says I should.
Why fintech systems are their own beast
Most software can drop a request and move on. Money can't. A payment that runs twice, a balance that's off by a cent, a ledger that can't explain itself to an auditor — those aren't bugs, they're incidents. Correctness isn't a feature here; it's the floor. That constraint, plus real-time deadlines and regulation, makes this some of the most interesting systems work there is.
What I write about
- Journal — dated, personal entries; what I'm thinking about now.
- Thoughts — longer essays on financial systems, design, and trade-offs.
- Trends — reactions to what's happening in fintech and the broader field.
- What I'm reading — links and short takes.
- /now — what I'm focused on at this moment.
How I write
One idea per post. I try to show the reasoning, not just the conclusion — because in this field the trade-off is the interesting part. I link my sources and don't fabricate facts or benchmarks. When I'm unsure, I say so.
If you want to follow along, grab the RSS feed.
Archie