7+ years shipping production systems. Now going deeper into why systems break, slow down, and fail at scale. Focused on distributed systems, event-driven architecture, and the kind of engineering that handles hard problems, not just working ones.
After 7 years shipping features, I became more interested in the infrastructure beneath them. This is an intentional, documented transition, not a career change, but a depth change.
How does a service behave when it's receiving 10x expected traffic? When a dependency is slow? When a node disappears? I'm engineering for those questions.
Moving beyond REST-only thinking into event streams, message brokers, and async patterns that decouple services and handle partial failure gracefully.
You can't fix what you can't see. Building systems with structured logging, distributed tracing, and meaningful metrics from day one.
Every experiment, insight, and system failure I encounter is documented publicly. On GitHub as code, on Medium as write-ups, on LinkedIn as milestones.
7 years deep across the full stack. Narrowing focus toward backend systems, but the breadth is a feature, not a bug.
Service decomposition, inter-service communication, consistency patterns.
Async architectures, message brokers, event sourcing, CQRS.
Database internals, query performance, replication, and sharding.
Go goroutines, worker pools, thread-safe design, race conditions.
SLOs, error budgets, tracing, structured logging, on-call readiness.
Auth patterns, secrets management, supply chain security, threat modeling.
I document this transition publicly. Code on GitHub. Long-form writing on Medium. Milestones and insights on LinkedIn.