I’m Medhansh — an 19-year-old developer based in Chandigarh, focused on systems and understanding software from first principles.
I scored 97 percentile in JEE and 91% in Class 12 — two years of four hours of sleep a night, studying in the mornings, coding at night. JEE doesn’t reward what you know. It rewards how fast and cleanly you can apply it when the pressure is real and the margin for error is zero. That’s the skill I actually carried forward.
CS50 ran parallel to all of it. That’s where programming stopped being syntax and started being thinking. The first time a framework broke in a way I couldn’t debug — because I had no idea what it was built on — those two things connected. I understood what I needed to go build.
So I built a game engine before using one. Wired a Raspberry Pi instead of simulating it. Wrote the collision detection algorithm from scratch and understood why it worked — not because the docs said it would, but because I could trace every decision back to first principles.
Building things from scratch taught me that every abstraction has a cost. Frameworks don’t eliminate complexity — they relocate it. They hide it in layers you don’t control and failure modes you don’t recognize until things break at the worst possible moment. The engineers I admire most aren’t the ones who memorize tools, but the ones who understand exactly what those tools are trading away.
Building also taught me that most of what separates working code from good code isn’t cleverness. It’s the decisions made before the first line is written — how the problem is framed, what constraints actually matter, where the complexity genuinely lives. I’ve watched elegant solutions fall apart not because they were wrong, but because they were solving the wrong thing cleanly. That’s a harder mistake to catch than a bug.
I’m 18. But abstractions don’t scare me anymore.