Yagna Kusumanchi was 16 when Telangana State University adopted his Python 3.0 for Beginners as a reference text for their Python Programming course. He’d taught himself the language in 9th standard, after a friend showed him code for the first time. The book started as something for his older brother, who was also learning. It became something a state university handed to its students.
Today, he is in Year 4 at Kalvium, in our four-year B.Tech CSE programme, working as a Software Development Engineer intern at Morgan Stanley. This is the story of why a self-taught teenager who could have skipped college altogether chose a structured undergraduate programme instead, and what it gave him that the book could not.
His father, a government teacher, framed a copy. His mother watched her son sit at a screen for hours, building something he genuinely cared about.
That’s where most stories about teenage coders end. Self-taught. Published. Done.
Yagna’s didn’t.
The thing the book couldn’t fix
There’s a quiet realisation that hits anyone who’s written technical content before they’ve actually shipped working software at scale. You can explain the language. You can answer questions about syntax and idioms. You can hold someone else’s hand through a tutorial.
What you haven’t done is debug a production failure at 2 AM. What you haven’t done is make an architectural call you weren’t sure about and then watch it ripple through three months of work. What you haven’t done is ship something a hundred users depend on, and find out the next morning whether your assumptions were correct.
Yagna knew the gap. He’d built things on his own, but the kind of things you can build alone, in your bedroom, with no users, are different from the kind of things engineers do for work. He wanted the second kind.
How Yagna picked Kalvium
His older brother got there first, three years into the Kalvium B.Tech CSE programme, specialising in AI and ML. By the time Yagna was in 12th, he had already heard the second-hand version: the sprint demos that did not go to plan, the mentor conversations that lasted longer than they were meant to, the projects that broke and the projects that worked. He had watched his brother go from someone learning code to someone building production software.
Yagna read the Kalvium brochure end to end. One thought stayed with him: is there any other programme like this in India?
He didn’t need a place that would teach him what a for loop is. He needed an environment where building things that work was the default, not the exception. Where mentors had been in industry recently enough to know what mattered. Where Year 1 wasn’t a year of waiting for the work to start.
He joined not because he was starting from scratch. He joined because his curiosity needed somewhere harder to go.
Where he is now
Year 4. SDE Intern at Morgan Stanley.
He’s writing code that runs against systems people use. He’s making engineering decisions with stakes attached. The code is reviewed by senior engineers who’ve seen what does and doesn’t survive contact with production.
Some of what he learned writing his book carries over. Clear thinking. The ability to explain a concept simply. The habit of breaking things down into the smallest part that still works.
Most of what he does at Morgan Stanley, he didn’t learn from writing. He learned it from building, repeatedly, under conditions he didn’t control, with mentors close enough to challenge him when his reasoning was off.
The book is still in print. It still teaches what it was meant to teach.
But what Yagna does now is not what the book could have taught him. Not because the book was wrong. Because the next thing was different work.
What we learned watching Yagna’s four years
Self-driven students don’t need to be taught the basics. They need an environment where what they already know has somewhere harder to go.
That’s the thing Kalvium is trying to be. Not a place that turns blank slates into engineers. A place where students who’ve already started can keep going, with company, with mentors, with stakes that match what they’re capable of.
The book Yagna wrote at 16 was about Python.
The engineer he’s becoming at 21 is about everything Python alone could not teach him.