There's a growing movement of indie makers and engineers who build in public — sharing their revenue numbers, user counts, technical decisions, and even failures. I'm joining that movement, but with an engineer's perspective.
Why Document the Journey?
Three reasons:
- Accountability. Writing about what I'm building forces me to think clearly about why I'm building it. If I can't explain a decision in a blog post, maybe it's not a good decision.
- Knowledge sharing. The Indian indie maker ecosystem is growing. I want to contribute real, actionable insights — not just success stories, but the messy reality of shipping products.
- Personal record. Future me will want to look back and understand why certain choices were made. Documentation is a validation engineer's instinct.
What I'll Cover
This blog will be a mix of:
- Build logs — Technical deep-dives into architecture decisions, tech stack choices, and engineering trade-offs.
- Product thinking — How I identify problems worth solving, validate ideas, and decide what to build next.
- Market insights — Lessons from building for Indian markets: pricing, UX for non-tech users, mobile-first design.
- MedTech × Tech — How my validation engineering background influences how I think about software quality.
The Rules I'm Setting
Be honest. Share the failures. Don't optimize for looking smart — optimize for being useful.
Every post will aim to teach something concrete. No fluff, no motivation porn. Just an engineer sharing what he learned while building products that matter.
Welcome to the Vystra blog. Let's build.