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 projects.
I document decisions, trade-offs, and outcomes.
A portfolio built around case studies — not screenshots.
I'm Erland, senior software engineer focused on building systems that move real business metrics.
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.
What People Say
"Erland is easily one of the most thoughtful engineers I've worked with. He doesn't just solve problems; he documents the 'why' behind them, which has helped our team scale much faster and avoid repeating past mistakes."
"His documentation on architectural decisions saved us so much time during recent incidents. Erland has such a clear approach to decision-making that I’ve actually started adopting his methods in my own daily workflow."
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
Let's Work Together
Looking for technical leadership, architectural guidance, or someone who documents their thinking? Let's talk.