Hi, I'm Sidd (and yes, I finally started a blog)
The obligatory first post: who I am, what I build at work and after hours, and why this blog exists when a perfectly good drafts folder was available.
Every developer blog starts with a "hello world" post. I resisted for about three weeks, which is a personal record. So: hello, world. I'm Sidd.
Who is this guy?
I'm Siddhant Singh. Everyone calls me Sidd, mostly because "Siddhant" takes too long to shout across an office. I'm a Senior Software Engineer at Optum (UnitedHealth Group), based in Gurugram, India, and I've been writing production code for 3+ years.
The short version of my career, as an honest stack trace:
Error: Siddhant kept building things
at Optum.intern (django, pandas) // 2022
at Optum.softwareEngineer (spring-boot, kafka) // 2023–2026
at Optum.seniorEngineer (fastapi, agents) // 2026–now
at nights.and.weekends (chrome-extensions) // always
No fix has been found. Maintainers have stopped looking.
What do I actually do all day?
These days I build AI agents that find bugs before people file tickets about them. Which sounds like science fiction until you remember the agents are mostly reading logs, the same way I do, except they don't need coffee and they don't sigh.
Here's roughly how our root-cause analysis workflow fits together:
flowchart LR
A[Something breaks in prod] --> B[GKE logs]
B --> C{RCA agents}
D[Repo context + static analysis] --> C
C --> E[Regression candidates]
E --> F[Incident report]
F --> G[Human reads it before the ticket even exists]It's projected to save $500K–700K a year and cut defect-resolution time by 20–30%. I'd like to say I did this out of a pure love of efficiency. Mostly I just really didn't want to read more logs.
And after hours?
After hours I build small things for myself and then, out of pure stubbornness, ship them for everyone.
| Thing | What it does | Status | Honest assessment |
|---|---|---|---|
| plenz | Rewrites weak AI prompts before you send them | Live, 200+ installs | My prompts are now great. My emails, sadly, are not. |
| admin-boil | An admin dashboard you install with one CLI command | Live | Because I refuse to build the same CRUD table a fifth time |
| SnapNode | Crisp, element-level screenshots of any web page | Beta | "Beta" means "works on my machine, and now hopefully yours" |
There's also a growing pile of free tools on this site: an LLM token cost calculator, a Mermaid previewer (yes, the diagram above is a little self-promotion), a diff checker and a few more. They all run in your browser. Nothing gets uploaded, because frankly I don't want your data.
So why a blog?
Three reasons, in order of how much I'll admit to them in public:
- Writing makes me think straighter. If I can't explain an architecture in a paragraph, I probably don't understand it.
- Future me has the memory of a goldfish. This is a well-indexed, publicly searchable notes app.
CloutSharing what I learn with other developers. Obviously. That's what I meant.
What will I write about?
Roughly this, in no promised order:
- Build a portfolio
- Ship an extension real people install
- Launch the blog (look at me go)
- How the RCA agents work, minus anything that would get me a stern email from Legal
- Building Chrome extensions without losing your mind over Manifest V3
- Notes from shipping side projects as a person with a full-time job and a finite number of weekends
- The tools on this site, and the bugs I'm pretending they never had
- Finally finishing that side project.
This weekendSoon.
Want to say hi?
I'm genuinely open to interesting problems: web apps, AI features, browser extensions or a site that needs to rank. You can book a 15-minute call, email me at siddhant06137@gmail.com or find me on X as @creatorsidd, where I post slightly less carefully edited thoughts.
Thanks for reading the obligatory first post. The next one will have more code and fewer jokes. Probably.