Four years of building things I wasn't ready for

I entered college thinking there was a correct order: learn theory → pass exams → then build. That order is a lie we tell ourselves so the syllabus feels safe.

Almost everything useful I know came from starting something I was underqualified for and thrashing until it either worked or taught me why it didn’t.

Slightly past comfortable

The retrieval project forced embeddings on me while I was still fuzzy on what a vector space even was. The Flask API taught me REST by breaking REST. Tutorials get you to “it runs.” Midnight debugging gets you to “I understand why it runs.”

That gap is the whole game. You can’t read your way across it.

Contests as forced endings

I did an innovation contest at IIT Kharagpur. Science Day model — EcoFlow Irrigator. Third place both times.

Third is a weirdly good teacher. Close enough to see what the winners did. Far enough that you can’t cope with “I almost had it.” Also: a deadline. Without one, my projects stall at 80% forever and rot in a private repo.

The unfinished ones

My GitHub is not a trophy case. There’s a half game I wrote to understand event listeners. CRUD apps that existed only so I’d stop being scared of ORMs. Things that never booted.

I used to hide those. Now I think they were the point. You don’t pick which attempt teaches you the thing. You just keep attempting.

Job vs college

College hard mode: make it work at all.
Job hard mode: make it work for someone else, next month, when you’re on leave.

The habit that transferred: write down what broke and how you fixed it. Everything else I’m still figuring out in production like everyone else.

Notes to first-year me (and maybe you)

• Read other people’s code earlier than feels polite.
• Ugly and running beats elegant and theoretical.
• Ask the dumb question in the group chat. Half the room has the same one.
• The thing you build badly this month is why you can build it next year without crying.

I don’t have a clean ending for this. I’m a few months into a full-time role and still mostly learning in public — just with better error messages and a laptop that IT actually manages.