Building, Breaking, and Learning Along the Way

I've always believed that the best engineers are the ones that ask why things work the way they do, and aren't afraid to break them to find out.

This blog is where I document that process.

Over the past few years, I've worked on products that scaled across continents, and systems that barely held together until they didn't. During all of that, I learned that real engineering isn't about writing perfect code, but rather writing code that survives bad assumptions, time pressure, and your own future self.

Most of what I share here comes from trial, error, and way too many late-night debugging sessions.

---

Why This Blog Exists

I wanted to create a space that's honest about the trade-offs behind every engineering decision.

---

The Bigger Picture

At the end of the day, building software isn't just about clean commits or elegant diagrams. It's about impact: shipping something that makes a user's day a little better, or a system a little faster.

That's the balance I'm still chasing - between code quality, scalable system design and delivery.

If you're someone who loves building, breaking, and learning along the way, welcome. You'll fit right in.

---

• Lakindu Hewawasam | Technical Lead @ Surge Global