Transitioning to Remote-First Team Structure
Post-pandemic, our team was split between office and remote workers. The hybrid model created two classes of employees and made collaboration inconsistent. We needed to decide on a deliberate approach.
I don't just ship features.
I understand business goals, document decisions and trade-offs, and record outcomes.
I also capture what could be improved — to make better decisions next time.
I understand business goals, document decisions and trade-offs, and record outcomes.
I also capture what could be improved — to make better decisions next time.
Every major decision is documented—because great engineers don't just build things, they explain why.
Read my journeyRecent Decisions
View allAdopting Event-Driven Architecture for Order Processing
Our synchronous order processing pipeline was becoming a bottleneck. Long-running operations blocked the checkout flow, and failures in downstream services caused cascading issues.
Problems I Enjoy Solving
How to scale systems without scaling complexity · When to choose consistency over availability · Making legacy codebases maintainable · Designing APIs that last · Building teams that ship · Turning technical debt into technical investment · Documenting decisions so future-you understands past-you