Skip to content

I build things.

I question things.

So far nobody has made me choose.

Ujjawal Bansal

Computer Science · Software Engineering · Philosophy

अहं ब्रह्मास्मि

About, more or less

Who am I?

  1. A name.Chosen by other people, before I could object.
  2. A body.Replaced, more or less, every few years.
  3. A collection of memories.Edited on every recall.
  4. A stream of thoughts.None of which stay.
  5. A programmer.Only since 2023.
  6. A student.Ends in 2027.
  7. An observer.Closer. Still a noun.

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

Things that exist

Seven verbs

How I think

01

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.

02

Question

Convention is a cached answer. Sometimes the cache is stale.

Whose decision am I repeating?

Read the source before trusting the docs.

03

Observe

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.

04

Learn

Every project changes what the problem was.

The better question is the output, not the answer.

The second implementation knows what it is building.

05

Simplify

Good engineering is mostly subtraction.

What is essential?

What can be deleted?

06

Accept

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

  • How you think
  • How you design
  • How you debug
  • How you respond to failure
  • Whether you keep learning

Not up to you

  • The network
  • The vendor's status page
  • The free tier that sleeps
  • The deadline
  • Whether anyone replies
There are things which are within our power, and there are things which are beyond our power.
Epictetus, Enchiridion, ch. 1, opening
07

Create

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.

Writing

What actually happened

Journey

  1. 2023

    Started B.Tech, Computer Science & Engineering

    ABES Engineering College, Ghaziabad

  2. Sep 2025 – Present

    Content Lead

    GeeksforGeeks ABES Student Chapter

    Leading the writers now, after ten months of writing for people who had not yet decided whether they liked programming.

  3. 2026

    Core organiser, Stellaris

    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.

  4. 2027

    Graduation

Only what actually happened. The years in between were mostly reading documentation, which does not make a good timeline entry.

Tools, not trophies

The instruments I use to turn thought into systems

  1. Think

    Languages

    Different grammars for the same few ideas.

    • TypeScript
    • JavaScript
    • Java
    • Python
    • C
    • SQL
  2. Show

    Frontend

    Where the system meets someone who did not build it.

    • React
    • Next.js
    • Vite
    • Tailwind CSS
    • Recharts
  3. Decide

    Backend

    Where the rules live.

    • Node.js
    • Express
    • JWT
  4. Remember

    Data

    The only part that remembers anything after the process exits.

    • PostgreSQL
    • MongoDB
    • Mongoose
    • Supabase
  5. Judge

    AI

    Useful for judgement. Kept away from logic.

    • Groq
    • LLM pipelines
    • Zod
  6. Ship

    Deployment

    Where it stops being a branch and starts being someone's Tuesday.

    • Vercel
    • Render
  7. Keep honest

    Tools

    Unremarkable, and used every day.

    • Git
    • GitHub
    • npm
    • Postman
    • VS Code

The rest of it

When I'm not writing code

Reading
Mostly philosophy, and mostly slowly. I re-read more than I read; a book I have finished once I have usually only located.
Thinking about it afterwards
The reading is the easy half. The part that takes the time is noticing, a week later, that something I believed has quietly stopped fitting.
Singing
Badly at first, which was the useful part. It is the one thing I do where there is no way to be clever about the gap between what I meant and what came out.
Listening
Usually while writing something. Music is the only background process I allow myself during work that needs attention, which probably says something.

The end of the scroll

Get in touch

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