About
ekam (एकम्) is Sanskrit for “one.” The number, the whole, the thing that isn’t divided. It’s also the name I’m giving to something I’ve wanted to do for a long time: study Advaita Vedanta, rooted in the Upanishads among the oldest philosophical texts we have, and see what it says about the way we build software. Its core claim is that reality is non-dual. One thing, appearing as many.
I’m not a scholar. I’m a software engineer. I build CLI tools, proxies, and agents: systems that move data, make decisions, and occasionally fail in production. I ran into Advaita Vedanta years ago and it lodged somewhere. Not as religion. As design. The Upanishads, read carefully, are systems thinking in the language of metaphysics. They ask what’s real, how we know it, and what happens when we mistake one thing for another. Every senior engineer I know asks the same questions. They just don’t ask them in Sanskrit.
This project is my attempt to bridge that gap: 12 essays, 12 principles from Advaita Vedanta, each mapped to a software idea it clarifies in a way conventional thinking doesn’t. Some mappings are tight. Debugging as the method of negation is straight out of the Upanishads, and git bisect could have a Sanskrit name. Some are looser, and I’ll tell you which is which. The essays run in three phases: the Practice (concrete and immediate), the Design (structural), and the Ground (metaphysical). You can enter anywhere, though they build on each other.
I’m writing for peers. Senior engineers who think about design, curious builders open to finding truth in odd places, anyone who suspects that a 2,500-year-old tradition of systematic inquiry might have something to say about distributed systems. Each essay stands on its own and carries its own source references and further reading. No comments, no likes, no newsletter. A quiet place to read. If something here lands, or doesn’t, write back: ekam@1mb.dev.