01
From “it works on my machine” to software that can survive production.
A short statement of the engineering problem that matters most to me: understanding how systems behave when the conditions are real—not ideal.
Writing 01
Notes from the work
behind the work.
Practical observations on software systems, cloud infrastructure, architecture decisions, and the trade-offs that surface when things need to run for real.
What you’ll find here 02
Proof
Lessons and decisions grounded in projects and production work.
Practicality
Useful technical detail over generic takes or empty trend commentary.
Perspective
How I think through constraints when architecture, operations, and business needs collide.
Published notes 03
Archive beginning
02
Removing long-lived credentials from a Google Cloud pipeline.
How Workload Identity Federation and Application Default Credentials replaced a static service-account key in the India Hidden Gems CI/CD pipeline—and why the extra IAM setup was worth it.
03
Building search discoverability into the architecture, not after it.
How India Hidden Gems' SEO requirements shaped rendering, URL structure, and content modeling from day one—rather than being retrofitted after launch.
04
Designing commerce workflows that survive retries and race conditions.
How AP Enterprises' inventory and order systems used reservation and idempotency to stay consistent, even when requests repeat or arrive at the same time.
Coming next 04
Engineering perspective
Trade-offs that change how systems get built
Environments & security
Isolating dev, staging, and production without slowing the team down
Data lifecycle
Soft deletion, anonymization, and what "delete my account" should actually do
A useful conversation starts here 05
Let’s compare
notes on the hard parts.
Have a technical problem, architecture decision, or production lesson worth discussing?
Get in touch ↗