A portfolio built around case studies — not screenshots.
I'm Your Name, 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 journeyDedicated focused effort to improve system design skills after struggling in senior engineer interviews. Studied real-world architectures, practiced with peers, and started documenting design decisions systematically.
Hit a wall after months of unsustainable pace. Learning to recognize burnout signs and establish better boundaries was crucial for long-term sustainability in this career.
"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."
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
Looking for technical leadership, architectural guidance, or someone who documents their thinking? Let's talk.