Build
An idea that stays an idea is indistinguishable from one that was wrong.
An untested idea is a belief.
Ship it and let it disagree with you.
About, more or less
Or something beyond all of these?
The boring answer is the useful one: a Computer Science student at ABES Engineering College in Ghaziabad, graduating in 2027, who writes software and cannot leave a question alone once it has been asked.
The less boring answer is that those are not two things. I build systems that run in the real world: a queue running in a working eye clinic, an auth flow that assumes it will be attacked, a grading pipeline that refuses to guess. And I read philosophy for the same reason I debug: to find the assumption underneath the thing everyone already agrees on.
I also sing, which has nothing to do with any of it, and everything to do with why I do not mind being bad at something for a while.
None of that answered the question. It rarely does.
Proof
Queue management for small clinics
An OPD queue system running in a working eye clinic.
Read the case study
One origin, three surfaces on three different clocks, and a snapshot cache so a full waiting room costs one database read. Connections: Staff desk to Vercel (10s); Waiting board to Vercel (10s); Patient tracker to Vercel (10s → 2m40); Vercel to Express 5 API (same origin); Express 5 API to Snapshot (serve); Snapshot to PostgreSQL (1 read); Express 5 API to PostgreSQL (writes · invalidate).
Personal finance, typed end to end
A full-stack expense tracker for personal finance.
Read the case study
One package of Zod schemas that the client, the server and the OpenAPI document all derive from, so none of the three can drift. Connections: @savoney/shared to React 19 client (forms); @savoney/shared to Express 5 API (validates); @savoney/shared to /api/docs (generates); React 19 client to Express 5 API (REST); React 19 client to /api/auth (rotate); /api/auth to MongoDB 8 (token family); Express 5 API to MongoDB 8 (aggregation).
Essay feedback that refuses to guess
An AI feedback pipeline for student essays.
Read the case study
Four stages, a Zod gate after every model call, and one database transaction that either takes the whole result or none of it. Connections: Next.js 15 to Stage 1 · Groq; Next.js 15 to Stage 3 · Groq (later); Stage 1 · Groq to Zod gate; Stage 2 · Groq to Zod gate; Stage 3 · Groq to Zod gate; Zod gate to Stage 2 · Groq (dedup first); Zod gate to One transaction; One transaction to PostgreSQL; PostgreSQL to Stage 4 (aggregates).
Seven verbs
An idea that stays an idea is indistinguishable from one that was wrong.
An untested idea is a belief.
Ship it and let it disagree with you.
Convention is a cached answer. Sometimes the cache is stale.
Whose decision am I repeating?
Read the source before trusting the docs.
Debugging is mostly looking. So is the other thing.
Watching a reaction is not the same as being it.
Read the logs before you read the code.
Every project changes what the problem was.
The better question is the output, not the answer.
The second implementation knows what it is building.
Good engineering is mostly subtraction.
What is essential?
What can be deleted?
Some of it is not up to you. Rather a lot of it, actually.
Sort the world into what depends on you and what does not.
Set a timeout, handle the failure, move on.
Up to you
Not up to you
“There are things which are within our power, and there are things which are beyond our power.”
Eventually thought has to become something.
Thought that never lands was entertainment.
Close the loop. Write it, ship it, sing it.
Reading, thinking and arguing are all enjoyable enough to become a substitute for the work. At some point the loop has to close, or you have merely been entertained by your own mind.
What actually happened
2023
ABES Engineering College, Ghaziabad
Sep 2025 – Present
GeeksforGeeks ABES Student Chapter
Leading the writers now, after ten months of writing for people who had not yet decided whether they liked programming.
2026
ABES Engineering College
Pan-India: 1,600+ registrations, a $19,000 prize pool, GitHub as a gold sponsor. Running one is a different skill from winning one, and considerably less glamorous.
2027
Only what actually happened. The years in between were mostly reading documentation, which does not make a good timeline entry.
Tools, not trophies
Think
Languages
Different grammars for the same few ideas.
Show
Frontend
Where the system meets someone who did not build it.
Decide
Backend
Where the rules live.
Remember
Data
The only part that remembers anything after the process exits.
Judge
AI
Useful for judgement. Kept away from logic.
Ship
Deployment
Where it stops being a branch and starts being someone's Tuesday.
Keep honest
Tools
Unremarkable, and used every day.
The rest of it
The end of the scroll
Let's turn a thought into something that exists.
That is the whole pipeline, and the only part I cannot do alone is the first bit. If you have one, I read everything.
ujjawalbansal.tech@gmail.com