Sweet 15: Growing Up With Code, One Chapter at a Time

Fifteen years ago, I didn’t begin my software journey with passion, clarity, or a carefully crafted plan.

I began it to stay out of trouble at home.

Back then, software was just a course—an excuse, really. A way to avoid getting bashed for not knowing what to do next in life. Today, fifteen years later, that same decision has taken me across continents, into massive digital transformation programs, and into platforms that quietly impact hundreds of thousands of people every single day.

Somewhere between struggling to understand class vs object and watching AI generate applications in minutes, software didn’t just become my profession.

It became my life.

The Accidental Beginning

My journey formally started with a LAMP (Linux, Apache, MySQL, PHP) course at CDAC. At the time, I was a hardcore Electronics guy, unsure if software was even meant for me.

That single decision changed the direction of my life.

Soon after, I joined a small service firm with fewer than 10 people. It was my first real exposure to PHP-based web development. I was fascinated—not just by writing code, but by the browser itself and the untapped potential it offered as a platform.

I’ll always be grateful to the CEO who took a chance on me. That trust didn’t just give me a role—it laid the foundation for everything that followed.

Falling in Love With Learning (and Sharing It)

My next move was into a startup of around 30 people, which quickly grew into 150+ within two years. This phase was intense, fast-paced, and transformative.

I worked across:

• PHP frameworks like CodeIgniter, Yii, Zend
• E-commerce platforms such as OpenCart, X-Cart, ZenCart
• CMS ecosystems including WordPress, Drupal, Joomla

During this time, I began contributing seriously to open source, publishing numerous OpenCart plugins—one of which crossed 100,000 downloads.

This was also when I discovered something unexpected: I loved writing about technology.

Over the years, I’ve published 100+ technical blogs and 5 whitepapers, sharing lessons learned from real-world projects—architecture decisions, performance pitfalls, scaling challenges, and best practices. Writing became a way to reflect, clarify my thinking, and give back to the community that taught me so much.

I never monetized my open-source work. In hindsight, charging even a dollar might’ve changed my financial story—but back then, curiosity and learning mattered more than revenue.

I grew into a Team Lead, managing 30+ engineers, took on freelance work, and collaborated with clients across industries and geographies. Every project brought something new. Every challenge pushed me forward.

This phase felt less like a job and more like an ongoing adventure.

When Structure Met Curiosity

The next chapter brought me to a mid-sized organization with a presence across multiple cities. This is where I began to truly understand engineering maturity—the discipline required to deliver consistently, not just creatively.

I’m especially grateful to the CTO here, who encouraged experimentation and trusted the team to choose the right tools. Around that time, a close friend mentioned an emerging framework gaining attention at Google—Angular.

We explored it. We adopted it. We committed to it.

From that point on, Angular became a defining part of my professional identity.

This phase was rich with strong mentors, thoughtful leaders, and deep technical conversations. Every discussion sharpened not just my skills, but my perspective.

The MNC Chapter I Never Expected

I never imagined myself working in an MNC.

I was drawn to startups—the autonomy, the flexibility, the controlled chaos. But life had other plans, and I eventually found myself in one of the largest MNCs in the world.

The early days were overwhelming:

• Massive campuses
• World-class facilities
• Layers of security I had never encountered before

After years of Linux and macOS, I was handed a locked-down Windows laptop. I couldn’t even connect to the internet initially, let alone clone a repository. It took nearly a month just to feel operational.

The freedom I once enjoyed was replaced with defined processes and structured paths. At first, it felt limiting.

Over time, I realized it was discipline—not restriction.

Choosing Depth Over Breadth

This phase demanded something different.

Until then, my strength had been breadth—many frameworks, many stacks. Here, the expectation was depth.

I’m deeply thankful to the Senior Manager and Senior Architect who welcomed me into the account and trusted my abilities. We went all-in on Angular, intentionally avoiding third-party libraries to reduce security risks and long-term maintenance overhead.

Over the years, I worked extensively with:

• Angular 1.3, 1.5, 1.7
• Angular 2, 4, and subsequent releases
• Right up to Angular 20

Angular stopped being just a framework—it became second nature.

Beyond technology, I learned how large-scale programs are executed, how strategic decisions are made, and how systems evolve when longevity, security, and scale truly matter.

I embraced the AI wave, leveraged unlimited learning resources, and continued publishing and learning—because in software, stagnation is the real risk.

And along the way, I built friendships that will last a lifetime.

Sweet 15

Fifteen years later, I don’t see a straight career path.

I see uncertainty. I see risk. I see people who believed in me before I fully believed in myself. I see late nights, broken builds, tough calls, and quiet wins.

And most importantly, I see growth.

From an electronics student trying to figure life out, to someone contributing through code, architecture, and written thought leadership—this journey has shaped not just my career, but who I am.

There isn’t a single day I regret.

At fifteen, you’re supposed to be curious, hopeful, and excited about what’s ahead.

Turns out, at sweet 15 in software, I still am.

And I can’t wait to see what comes next.