I build software, experiment with ideas, and collect things worth remembering.
I'm an engineering student from Bengaluru, India who enjoys moving between software engineering and creative work.
I like taking an idea from:
"What if...?" → prototype → broken build → debugging → working system
My interests sit somewhere around full-stack development, AI, systems, IoT, UI/UX, photography, editing, automobiles, and cinema.
I don't really want to put myself into one box.
I want the things I build to feel like they came from me.
- 🧩 Full-stack web development
- 🤖 AI / Machine Learning
- 🧠 Reinforcement Learning
- 🌐 Backend systems & APIs
- 📦 Offline-first applications
- 🔌 IoT & embedded systems
- 🎨 Interaction design & visual interfaces
- 🧪 Building things simply to find out if I can
|
A full-stack doctor appointment ecosystem with patient, administration, backend and cloud workflows. React · Node.js · Express · MongoDB · Mongoose · Cloudinary |
An exploration of AI-assisted resume understanding and analysis. AI · Document Processing · Web Development |
|
Exploring private document workflows and AI-assisted interaction with documents. |
A project built around a real-world business context rather than a purely academic problem. |
One of my current builds is an offline-first billing system for agricultural stores.
The idea goes beyond billing:
CUSTOMERS · GST · INVENTORY · PURCHASES · PRINTING · INSIGHTS · OFFLINE
Useful software shouldn't stop being useful when the internet does.
Exploring dynamic matching optimization in ridesharing systems using reinforcement learning.
Experiments around:
ESP8266 · MQTT · Mosquitto · Arduino · BH1750 · SQLite
I care about the parts that are easy to ignore.
Does it actually work?
Does it survive deployment?
What happens when the network disappears?
Can someone understand the interface without being taught?
Does the error message actually help?
Can the whole workflow be tested?
Does the design have a reason to exist?
That is slowly changing how I approach engineering.
I'm less interested in simply making a feature and more interested in understanding the system around the feature.
🎓 Engineering Student
Rajarajeswari College of Engineering, Bengaluru
VTU curriculum
Also completed:
- Full Stack Web Development — Agrtas Edu Tech
- NPTEL coursework
My preferred learning loop:
learn → build → break → debug → understand → build again
My portfolio isn't designed as a traditional résumé.
It's a collection of worlds:
CODE · FRAME · CUT · DRIVE · SCREEN · LAB
Built with:
Next.js · React · TypeScript · Tailwind CSS · Framer Motion
The idea is to show not only what I build, but also what I notice, what I enjoy, and what keeps me curious.
A project doesn't have to be revolutionary to be worth building.
A good interface should make sense before it explains itself.
Offline is a feature.
The best way to learn a system is sometimes to break it.
Technical and creative aren't opposites.
Your GitHub can be a record of your evolution.
| Repository | What you'll find |
|---|---|
| HealthHub-frontend | Patient-facing healthcare application |
| HealthHub-backend | Backend APIs and data layer |
| HealthHub-admin | Healthcare administration |
| AI-Resume-Analyzer | AI-assisted resume analysis |
| privatedoc-ai | Private document + AI exploration |
| sri-kaveri-ice-plant | Real-world business project |
| web-dev | Web development experiments |
| vishwas-archive | Personal digital archive |