Writing

Notes on frontend architecture, statecharts, and the actor model.

Series

Behavior & Boundaries

Essays on responsibility, boundaries, and why architecture matters when code is cheap.

Part 1AI-Generated Code and Software Architecture: Why Ownership Matters
How AI-assisted development shifts the difficult work from producing code to deciding which part of the system should own each decision.
Part 2Product Framing Before Software Design: Deciding What to Build
How I use a product frame as the maintainer of Ignite Element, and how developers can apply the same questions to problems for their own clients and users.
Part 3Semantic Commands: Translating User Intent into Application Behavior
How to translate a product narrative into a precise application request without carrying interface details into behavior.
Part 4Functional Core Architecture: Where Deterministic Decisions Belong
How building an Ignite Element router with the browser's Navigation API led me to separate semantic commands, deterministic route policy, and environment effects.
Part 5Lifecycle Boundaries in Actor and State Machine Architecture
How moving browser navigation beyond an Ignite effect revealed the lifecycle owner for observation, commits, failures, and cleanup.