What I care about
- Making complicated systems easier to understand.
- Building tools that solve real problems.
- Writing to explain what I learn.
- Good design and a thoughtful user experience.
- Always learning, always curious.
About
The story of how curiosity across layers became a way of building, thinking and explaining.
the technology changes.
the curiosity stays.
the curiosity stays.
Somewhere between pixels and architecture
I started much closer to the interface. Design, frontend work and understanding how people interact with software were some of my earliest interests.
Over time, building interfaces led to building applications. Applications led to APIs, integrations and increasingly complicated systems. A large part of that journey happened around digital commerce, where a seemingly simple customer interaction can involve caching, APIs, search, checkout, third-party integrations and several layers of application logic.
Eventually I found myself spending more time thinking about the system as a whole - architecture, boundaries, performance and how the pieces affect each other. More recently I've been exploring AI systems, agents and developer tooling.
The common thread hasn't changed much: I like understanding how things work.
1 · DesignPixels, interface, visual communication
2 · FrontendInteractive experiences in the browser
3 · ApplicationsSolving bigger user problems
4 · APIs / ServicesPowering products behind the interface
5 · ArchitectureFlows, trade-offs and system boundaries
6 · AI & ToolsExploring new layers and building for developers
Beyond the code ♡
- Sketching and visual design
- Manga and anime
- Developer side projects
- Learning unfamiliar technical ideas
Design never really left.
Before spending most of my time thinking about systems and architecture diagrams, I spent a lot of time thinking about pixels. Iconography and interaction design still influence how I build software - particularly developer tools.
Complicated systems become easier to understand when you can make them visible.
