THE LATEST ESSAY Behavior & Boundaries
Lifecycle 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.
THE LATEST ESSAY Behavior & Boundaries
How moving browser navigation beyond an Ignite effect revealed the lifecycle owner for observation, commits, failures, and cleanup.
Behavior & Boundaries / Part 4
How building an Ignite Element router with the browser's Navigation API led me to separate semantic commands, deterministic route policy, and environment effects.
8 min readBehavior & Boundaries / Part 3
How to translate a product narrative into a precise application request without carrying interface details into behavior.
9 min readBehavior & Boundaries / Part 2
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.
10 min readBehavior & Boundaries / Part 1
How AI-assisted development shifts the difficult work from producing code to deciding which part of the system should own each decision.
10 min readA production-grade library for building statechart-driven UI components.
Software Engineer • Technical Advisor
I make behavior explicit so teams can ship complex systems with confidence.
Systems, delivery, and behavior-driven architecture. Notes on architecture, statecharts, and delivery.
Read my writingActor-Web, Ignite-Element, and other projects I maintain.
See OSS workBackground, approach, and how I work with teams.
Get to know meStart here: When Code Becomes Cheap → Why architecture matters now
KEEP READING
New essays and updates, delivered to your RSS reader. Read at your own pace.