AI Catastrophe Without Consciousness
Reconciling insider AI doom with skeptic autocomplete reality: why catastrophic risk stems from execution harnesses, not synthetic consciousness.
I’m a software architect and engineering leader. I focus on system design, architectural decoupling, and building engineering environments where autonomous teams ship with clarity and velocity.

Core principles and architectural practices that guide my work.
Designing distributed systems and modular architectures that scale cleanly without unnecessary complexity. I prioritize clear domain boundaries, verifiable interfaces, and practical decoupling so systems stay maintainable as teams grow.
Building engineering teams that own their services from design to production. I focus on high-trust cultures, clear ownership boundaries, and removing surveillance metrics in favor of genuine delivery.
Treating test-driven development and automated verification as architectural tools rather than compliance chores. Fast feedback loops and high test confidence let teams ship steadily without fear.
Eliminating architectural friction, technical debt traps, and heavyweight ceremonies. Good engineering practices don’t slow teams down—they provide the guardrails that make fast, continuous deployment reliable.
Essays on software architecture, engineering leadership, and systems design.
Reconciling insider AI doom with skeptic autocomplete reality: why catastrophic risk stems from execution harnesses, not synthetic consciousness.
Why a technologist traded digital apps for a physical GTD system. Exploring the engineering behind a low-latency, analog productivity workflow.
Stop using your Sprint Board for surveillance. Learn how shifting from developer swimlanes to story-centric lanes reclaims team sovereignty and transforms your stand-ups.
Stop treating Story Points like fixed units of time. Learn how points function as categorical data and how plotting them against velocity reveals your team's size-specific Cone of Uncertainty for realistic estimation.
The ultimate resilience strategy? Knowing when to stop. This AoC retrospective explores TDD as governance, strategic prioritization, and true architectural discipline.
Whether you’re working through an architectural challenge, scaling an engineering organization, or want to discuss ideas from my writing, I’m always open to connecting.