My path into systems architecture was non-linear. I started in hospitality and customer operations, where success depended on choreography under pressure: handoffs, timing, clear ownership, and fixing bottlenecks before they became failures.
SaaS made that pattern explicit. Revenue, onboarding, support, retention, and expansion are all connected systems. If the interfaces between teams are weak, outcomes decay no matter how hard individuals work.
That is why I focus on deterministic execution. I prefer constrained, observable workflows over fragile complexity. I use AI as a force multiplier, but the responsibility model stays human: architecture, validation, and boundary decisions remain mine.
My tooling and environment choices follow that logic. I run Linux-first systems (Bazzite and TUXEDO OS), test local-plus-cloud orchestration, and favor infrastructure that can be audited and reproduced. The stack should serve the operator, not lock in the operator.
This is not a pivot away from commercial work. It is a compounding strategy. I continue targeting senior architecture and system design roles while building Hubsays Studio in public. Every experiment should become a shipped artifact, a reusable pattern, or a written lesson.
The objective is simple: no zero-output months. Whether the immediate result is a role, a tool, or a studio milestone, the system keeps compounding.