I help ideas turn into software that actually runs.
From a rough concept to a working build — Python, the web, and the debugging in between. I build complete applications, not tutorial-length demos.
A few things I’ve built end to end.
Five projects, five different problems — desktop tools, web apps, and the odd 2am dependency bug along the way.
Card Table
A desktop scoring & ranking app for physical card games like Call Break — built with Flet for a native, game-inspired dark UI, backed by Supabase for persistent match history.
College Sports Management App
A full sports-management platform for GEC Jhalawar’s annual sports event — live scores, rosters, and match history over a FastAPI + React + WebSockets stack.
Synovixura Flask Web App
The application layer behind the Synovixura Tech brand site — a Flask app handling routing, templating, and server-side logic.
Amazon Clone
A front-end recreation of an e-commerce experience — product listings, cart interactions, and a responsive storefront.
Not a sequence — just what I keep coming back to.
I start with the problem, not the stack.
Before picking a framework, I try to understand what actually needs to exist — for the score sheet, the tenant list, the match schedule — whatever the real thing is.
I ship a working version early.
A rough build that runs teaches me more than a polished plan that doesn’t. I’d rather find the real bugs on day two than the imagined ones on day ten.
I don’t stop at “it works on my machine.”
Dependency pinning, environment quirks, and deployment details eat real time — I treat them as part of the build, not an afterthought.
I stay a beginner on purpose.
New frameworks and tools are still the fastest way to find out what’s actually possible — so I keep picking up ones I haven’t used yet.
What I spend my time on.
Complete Applications
End-to-end builds — desktop tools, web apps, and the databases behind them. I’d rather ship one working thing than three half-finished demos.
See the projects →Learning in the Open
Python, web frameworks, UI/UX, and automation — most of what I know came from breaking something and figuring out why.
See the stack →