https://upadhyaeeshachandra.com 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. en Mon, 15 Jun 2026 13:33:21 GMT https://upadhyaeeshachandra.com/blog/understand-the-problem-first https://upadhyaeeshachandra.com/blog/understand-the-problem-first Fri, 12 Jun 2026 00:00:00 GMT 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. https://upadhyaeeshachandra.com/blog/ownership-is-the-whole-job https://upadhyaeeshachandra.com/blog/ownership-is-the-whole-job Wed, 10 Jun 2026 00:00:00 GMT Engineering isn't delivering features — it's building trust. A short note on follow-through, and what 'done' actually means. https://upadhyaeeshachandra.com/blog/every-decision-is-a-trade-off https://upadhyaeeshachandra.com/blog/every-decision-is-a-trade-off Mon, 08 Jun 2026 00:00:00 GMT 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. https://upadhyaeeshachandra.com/blog/staying-curious-on-purpose https://upadhyaeeshachandra.com/blog/staying-curious-on-purpose Sat, 06 Jun 2026 00:00:00 GMT 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.