Engineering · Systems · Curiosity
I'm Eeshachandra — a software engineer who likes turning ambiguity into structured, workable solutions. The technical craft is satisfying, but the part I find most rewarding comes earlier: understanding the problem itself — asking the right questions, surfacing hidden assumptions, and weighing trade-offs before a line of code is written. I care about ownership and follow-through, and about building things that keep solving the problem long after they ship.
The most expensive bugs aren't in the code — they're in the problem statement. Why I spend more time understanding the problem than most people expect, and what that actually looks like.
Engineering isn't delivering features — it's building trust. A short note on follow-through, and what 'done' actually means.
Good system design isn't about the best choice — it's about the honest one. Why I try to understand the business as well as the tech before drawing the boxes.
Continuous learning isn't a phase you finish. A note on taking things apart to see how they work — and why I think there's always a better solution waiting.
No schedule, no spam — just new essays when they’re ready. The slow web, delivered slowly.