About
I build software, then keep going.
Into infrastructure, operations, commerce, privacy, incentives, and the consequences that appear once a system becomes real.
I’m Curtis Baldwinson, a software engineer and founder. I tend to follow problems wherever they lead rather than stopping where one discipline ends.
Across the work
Software is rarely only software.
An interface sits on infrastructure. Infrastructure determines where authority lives. Business models create incentives. Operations decide what happens when things fail.
Sometimes the answer is a product. Sometimes a company, a public framework, or writing. The form follows the problem.
Principles
What I don’t leave to chance.
Own the whole lifecycle
Success, interruption, failure, cancellation, recovery, and retirement are all product states. Design for each of them.
Enforce authority at the source
Interfaces can explain permissions. Identity, access, money, and state should be enforced where they are actually controlled.
Design for when things go wrong.
Retries, stale state, partial failure, accessibility settings, and recovery paths reveal more about a system than the happy path.
Keep the language honest
A prototype is not a release. Encryption is not a complete privacy lifecycle. A green check is only as broad as the path it actually observed.
Background
I grew up in Vancouver, Canada, in a family of entrepreneurs. From an early age, I saw businesses as things people could actually create: products to develop, customers to serve, systems to operate, problems to solve, and responsibilities to carry.
I took that instinct into software and followed it well beyond the interface: through products, infrastructure, commerce, finance, privacy, operations, and ventures of my own.
In 2011, I received British Columbia’s Courage to Come Back Award in the Youth category. Resilience has been a formative part of my life, and it continues to inform the value I place on recovery, agency, and things built to endure.
I live in Los Angeles today. My attention is increasingly on what technology becomes once it leaves the prototype behind: a product people depend on, a business with incentives, an institution with authority, or an idea capable of changing how something is done.
The larger project
Build things worth depending on.
Useful enough to matter. Durable enough to last. Clear enough to understand. Honest enough to deserve trust.
Correspondence
What are you trying to make true?
Tell me what you’re building, where it gets difficult, and why it matters. Context is more useful than a polished pitch.
Write to me