iamgr7, a log by Gaurav Raj, making things since 2011
I'm Gaurav Raj, a growth engineer in Stockholm, from Bengaluru. I love electronics and the web, and I have been writing code since 2011, when I started modding Android phones on XDA at 15. For eight years I used that to grow companies. Now I build again, and I keep this log so what I learn stays checkable. Every number in it has a date.
Start here
A round dial with a pointer hand always reads like a wristwatch, even when it is driving software. Breaking the silhouette into a tonneau chassis and a 6 Hz gear train turned a timepiece into an engine.
-
Proof shouldn't look like a card
A certificate that sits in a white rounded box looks like a settings panel. I rebuilt mine from the grammar of security printing, where every line is there to make tampering hard.
-
Aesthetics drift one small exception at a time. I wrote four of mine down as code, and the two that drift fastest now fail the build.
-
I diffed a careful hand check against my agent's log. Every gap was a quiet assumption, not a crash.
-
Red doesn't always mean broken
Two failures in one evening, neither caused by my code. How I told them apart, fixed both, and made CI cheaper.
-
Before you fix the question, check the label
My data said two categories got advice instead of names. The data was wrong, not the questions, and finding that out cost nothing.
-
Every answer costs money, so nothing gets overwritten
When each row is a receipt, upserts are a bug. Three rules that make paid data safe.
-
The model that said no to my forced tool call
Upgrading one step to a newer model broke the trick every step relied on. The fix was better than the trick.
-
2.3 MB per click, and a console that got slower every week
My internal console wasn't slow because of code. It was slow because of what each row carried, and where the server lived.