THE ARCHIVE
Writing.
Notes on frontend architecture, statecharts, and the actor model.
Ideas developed in practice.
Essays on what software does, who owns it, and how we make it easier to reason about.
A READING PATH
Behavior & Boundaries
Essays on responsibility, boundaries, and why architecture matters when code is cheap.
Start at the beginningALL ESSAYS / 05
Most recently updated firstBehavior & Boundaries / Part 5
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.
8 min readBehavior & Boundaries / Part 4
Functional 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.
8 min readBehavior & Boundaries / Part 3
Semantic Commands: Translating User Intent into Application Behavior
How to translate a product narrative into a precise application request without carrying interface details into behavior.
9 min readBehavior & Boundaries / Part 2
Product 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.
10 min readBehavior & Boundaries / Part 1
AI-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.
10 min read
KEEP READING
A place in your feed.
New essays and updates, delivered to your RSS reader. Read at your own pace.