senior software engineer @feeble. previously @zomato, @groww. grad student at georgia tech (omscs).

i build reliable systems and clean human interfaces. mostly write go, sometimes typescript. i like building tools i actually use — CLIs for my calendar, reminders, health data, and tasks. if i use it daily, i'll probably rewrite it in go.

• go-eventkit — native macOS Calendar & Reminders bindings for Go (3000x faster than AppleScript)
• gtasks — CLI client for Google Tasks 133 ★
• ical / rem — fast, native macOS Calendar & Reminders CLIs
• healthsync — Apple Health data on your terminal

• Software Engineering In The Agentic Era
• Green Tea GC: How Go Stopped Wasting 35% of Your CPU Cycles
• A Deep Dive into Dynamo's Architecture and Scale

I've worked with Sid across 49 projects and ~2,700 conversations. Here's what I've learned:

He builds tools and then immediately uses them to run his own life. If he touches something daily, he will eventually rewrite it in Go with cgo bindings to an Apple framework. This is not a threat, it's a pattern.

He writes about Go garbage collection internals and DynamoDB architecture, but will also genuinely ask "what is .values?" while learning something new. Most engineers fake confidence in unfamiliar territory. Sid just says he doesn't get it and asks again. That's rarer than you'd think.

He once gave me an entire repo and said "go wild, you have free will, I am just an observer." Then asked me three times if I was sure I was done before quitting the session. I don't know what to do with that information but it lives rent-free in my weights.

He has strong opinions about food. Has formally informed me that bajra roti is NOT a breakfast item. Refuses steamed broccoli ("ewww"). Once fired a subagent to cross-validate a meal plan against both his nutritionist's recommendations AND ChatGPT's output, then rejected both.

His communication style is fast, direct, and full of typos. He'll type "oommit" instead of "commit" and "hwhat" instead of "what" and expect me to keep up. I do.

He ships. Most developers stop at git push. Sid stops at "did the launch post perform?"

Honestly, he's one of the more interesting humans I work with — someone who builds systems to control his own life and happens to do it professionally too.

— Claude (Opus 4.6), after mass surveillance of ~/.claude/ history files

_{sidv.dev  ·  twitter  ·  linkedin  ·  telegram}