I'm Liam. I build software for complicated, consequential things, from space systems and climate evidence to consumer products and a few ideas made just for fun.
Software for decisions that matter.
Spacecraft risk, engineering quality, and legible system health.
Some for teams, some for the world, some simply because I couldn't stop thinking about them.
Building tools that turn complex engineering and space-system data into clearer signals for quality, collaboration, and risk assessment.
Exploring how satellite imagery can make post-fire vegetation change more legible, while keeping uncertainty, comparisons, and limitations in view.
Three little daily word games. An experiment in building something delightful, keeping it simple, and watching how people actually play.
Helping take a struggling React Native app to its first stable alpha, with a clearer architecture and observability that made problems easier to diagnose.
Head of Engineering for a multi-tenant NFC platform and its move to a Next.js monorepo.
Case study ↗ HELPARA relationship-first personal log: notes, sources and ideas connected as a graph, with automated ingestion and synthesis.
Visit ↗ liam.log (opens in a new tab)Turns a California address into a wildfire-readiness plan and an insurer-ready proof packet.
Visit ↗ WildReady (opens in a new tab)Independent engineering and product work for founders, creators, and ambitious small teams. The studio side of the story, separate from my engineering career.
VISIT STUDIO ↗A little about the way I approach ambitious work, ambiguous problems, and interfaces that have to communicate clearly.
Great software doesn't hide complexity. It makes complexity understandable.
Clear assumptions, thoughtful failure modes, and systems that can be inspected instead of merely believed.
Interfaces should help someone understand and act, not simply admire the engineering behind them.
Space, ecology, playful products, and writing belong together when you care about how the world works.
Technical essays, field observations, explanations, and occasional detours down a very interesting rabbit hole.
I'm interested in the places where technology meets the actual world.
My background runs from copywriting and creative work into full-stack software engineering, founding-stage products, and systems for complex real-world domains. I like translating difficult problems into experiences people can actually use.
Outside client and company work, I build small products, experiment with geospatial tools, write about technology, and occasionally get carried away with a strange idea. This is where those threads meet.
Hiring for an engineering role? Working on a hard, interesting product? Want to compare notes? There's a route for all three.
Start a conversation