Skip to content

About

I’m a software engineer. I build distributed systems for a living — event-driven architectures, microservices, the kind of stuff that handles real scale. I decided to stop building solely for other people.

Gabru (ਗੱਭਰੂ) is Punjabi for someone who’s young, bold, and ready to take on the world. It’s the energy I’m bringing to this: less overthinking, more building.

I’ve shipped production systems that handle serious traffic. Optimized queries that saved lakhs in infrastructure costs. I know how to build. What I hadn’t done was decide what to build.

Then AI coding tools got genuinely good. I described a full system to Claude Code — frontend, backend, database — and had a working prototype in three hours. The bottleneck that killed every side project — setup, config, boilerplate — just disappeared.

That changed things. I chose to start building for myself.

A learn-by-building journal. Each day, every day. I pick real problems, build solutions with AI tools, ship them, and write about the entire process — the code decisions, the tradeoffs, and the parts that broke.

What you get:

  • Build logs with real architecture decisions and tradeoffs
  • Actual revenue and user numbers — including when both are zero
  • Honest tool reviews of the AI dev stack (Claude Code, Cursor, v0, and whatever else shows up)

Because accountability works. Building in public means I can’t quietly close the repo and move on. And if even one other engineer sees this and thinks “I can do this too” — that’s the whole point.

The gap between knowing how to build and actually shipping has never been smaller. The bottleneck isn’t skill. It’s the decision to start and the drive to finish.

  • X/Twitter: @gabrubuilds — daily updates, AI tool takes, build threads
  • GitHub: gabrubuilds — all the code, all the repos