I like the layer underneath, the part that has to be fast and correct when nobody is looking at it.
BITS Pilani '27 · Bengaluru
Almost everything I know came from open source. I did not plan any of it in advance; one repo led to the next, and the things I got interested in are the things I kept showing up for.
Sugar Labs, Music Blocks. This is the one I care about most. I am a maintainer, working across both the original codebase and the v4 rewrite: how it loads, how the bricks are drawn and snap together, how the palette is put together, and reviewing pull requests from other contributors so they do not sit around waiting. It is software children learn music and programming with, which makes the small details feel worth arguing about.
Hyperledger Besu. Where contributing started for me. I went in thinking it would be Java plumbing and ended up in modular arithmetic, chasing client speed through the 256 bit math sitting under every EVM opcode. That was the project that taught me most performance work is really a maths problem in disguise, and I have been happily stuck on that idea since.
Kubescape, CNCF. Kubernetes security. I am still very much learning here, and that is the point. Reading how real clusters are attacked and defended is teaching me a whole vocabulary I did not have a year ago.
WasmEdge, CNCF. WebAssembly, in C++. This is my weekend thing. I pick it up when I feel like it, mostly because the runtime is small enough to actually read end to end and I wanted to understand what happens between a .wasm file and something running.
mandate · a small enforcement layer that decides what an agent is allowed to do from a schema, before it does it, with no model in the loop.
schemago · a Postgres migration runner in Go. One binary, one transaction per migration, safe when two deploys start at once.
note: the contribution graph below is generated by GitHub and cannot be turned off. It counts days I pushed, which is a much smaller set than days I did any work.