I’m Tanvi, a mechanical engineering student who spends a lot of time thinking about software infrastructure, developer tools, and how the messy bits behind the scenes shape our daily work. I’m currently building several projects — still very much works in progress — that explore different parts of this hidden terrain.
There’s KurajoCI, my attempt at reimagining continuous integration. It’s designed to make CI smarter and more efficient, so you spend less time waiting and more time shipping.
Then there’s Dodo, which automatically generates GitHub workflows by understanding the modular pieces of your project and how they fit together — think of it as a workflow architect with an eye for detail and incremental builds.
None of these projects are polished or finished products yet. They’re experiments, early drafts, and sometimes even questions encoded in code. Each tries to push the boundaries of what’s possible, questioning assumptions baked into the tools we use every day — defaults, configs, and protocols that often go unquestioned.
bitzany is where I step back from the code and dig into the “why” behind these assumptions. It’s my place to document the oddities, the frustrations, and the little breakthroughs that happen when you look a bit closer. Sometimes that means writing long essays; sometimes it’s quick notes or sketches of ideas that haven’t fully formed yet.
Fair warning: I’m not always consistent. Sometimes I’ll go quiet for a while. Then suddenly, I might flood the blog with multiple posts in rapid succession — those moments when a bunch of half-formed thoughts catch up and demand to be written down before they slip away. If you see a burst of posts, that’s me chasing down the rabbit holes I left open.
If you’re curious about the hidden layers beneath your tools, or if you find yourself wondering why something works the way it does — especially when it feels a bit off — you’ll probably find something here that clicks.