← Back to list

Lessons Learnt in 11 Years of IT

“The technologies changed. The mindset didn’t: Learn. Adapt. Deliver.”

Hariramakrishnan B · 2026-06-15 08:36 · 0 claps · 5.9 min read
#it-journey #esqlc-to-ai #decade #it-industry #ai-engineer
Open on Medium ↗

Lessons Learnt in 11 Years of IT

“The technologies changed. The mindset didn’t: Learn. Adapt. Deliver.”

From ESQL/C to AI

On January 8, 2015, I walked into my first IT job as a Programmer Analyst Trainee at Cognizant Technology Solutions.

Like most fresh graduates, I was excited, nervous, and completely unaware of what the next decade would teach me.

If someone had told me then that I would one day build Java backend applications, leverage Artificial Intelligence in software development, create preventive monitoring solutions, and automate engineering workflows using Python, I probably would not have believed them.

This is the story of my 11-year journey in IT — a journey of continuous learning, adaptation, failures, growth, and transformation.

A Decade of Reinvention: Evolving from Legacy Systems to Modern AI-Driven Engineering.

A Decade of Reinvention: Evolving from Legacy Systems to Modern AI-Driven Engineering.

The Beginning: Learning the Foundations (2015–2016)

My career started with technologies that many modern developers may never encounter.

I was introduced to ESQL/C and Informix 4GL technologies that powered critical enterprise applications. While they were not the trendiest technologies, they taught me some of the most valuable lessons of my career.

I learned:

  • How business-critical systems operate
  • The importance of writing reliable code
  • Database fundamentals
  • Production support responsibilities
  • The impact of software on real-world business operations

As a trainee, every bug fixed felt like an achievement. Every successful deployment felt like a milestone.

Looking back, those experiences laid the foundation for everything that followed.

Becoming an Independent Developer (2016–2018)

After transitioning to the Programmer Analyst role, I began taking ownership of development activities.

This phase taught me something that remains relevant even today:

Technology changes. Problem solving does not.

I started writing production-grade code, handling application enhancements, debugging complex issues, and supporting enterprise systems.

During this period, I also discovered automation.

I learned Shell scripting and Bash scripting and began automating repetitive operational activities.

My first realization that code could eliminate repetitive work.

My first realization that code could eliminate repetitive work.

For the first time, I realized that engineering is not just about building software.

It is also about eliminating inefficiencies.

The satisfaction of replacing a manual process with a simple script was immense.

I became fascinated with finding smarter ways to work.

Growing Beyond Coding (2018–2021)

As an Associate, my responsibilities expanded.

I was no longer focused solely on development.

I began understanding the bigger picture.

The goal changed from fixing problems to preventing them.

The goal changed from fixing problems to preventing them.

Questions changed from:

“How do I fix this issue?”

to

“Why does this issue occur repeatedly?”

and

“How can we prevent it altogether?”

This shift in mindset transformed my approach to engineering.

I became more interested in root cause analysis, process improvements, automation, and operational excellence.

I learned that the best engineers are not those who fix the most problems.

They are those who prevent problems from happening in the first place.

This realization would become a recurring theme throughout my career.

A New Chapter: Joining Walmart Global Tech (2021)

In February 2021, I joined Walmart Global Tech India.

This was one of the most significant transitions of my professional life.

I moved from a legacy technology ecosystem into a modern engineering environment.

More importantly, I challenged myself to learn an entirely new technology stack.

I started learning Java.

Initially, the learning curve was steep.

Concepts such as object-oriented programming, enterprise application development, APIs, frameworks, and modern development practices required a completely different way of thinking.

There were moments of self-doubt.

After spending years working with legacy systems, starting over as a learner was not easy.

But growth rarely happens inside comfort zones.

Every day became an opportunity to learn something new.

Reinventing Myself as a Java Engineer (2022–Present)

By 2022, I had fully embraced the transition.

I evolved into a Java backend engineer and began contributing to enterprise-scale applications.

Reinventing myself meant becoming a student again.

Reinventing myself meant becoming a student again.

This phase of my career taught me one important lesson:

Reinvention is possible at any stage of your career.

Many professionals fear becoming obsolete as technology evolves.

I chose a different path.

Reinventing myself meant becoming a student again.

Reinventing myself meant becoming a student again.

Instead of resisting change, I embraced it.

I focused on:

  • Backend application development
  • Building scalable solutions
  • Enhancing operational efficiency
  • Application modernization
  • Continuous learning

The investment paid off.

I was no longer limited by the technologies with which I had started my career.

I had become adaptable.

And adaptability is one of the most valuable skills in technology.

Building Visibility Through Dashboards and Monitoring

One area that particularly interested me was operational visibility.

Many issues occur not because organizations lack talent but because they lack visibility.

To address this, I worked on creating dashboards, monitoring screens, reports, and tracking mechanisms.

Moving from solving problems to preventing them.

Moving from solving problems to preventing them.

These solutions helped teams:

  • Detect issues earlier
  • Monitor key business processes
  • Improve decision making
  • Reduce operational risks
  • Implement preventive controls

The goal was simple.

Move from reactive problem solving to proactive prevention.

This mindset significantly influenced how I approached engineering challenges.

The Rise of AI

Then came one of the biggest technological shifts of my career — Artificial Intelligence.

Like many engineers, I initially viewed AI as another emerging trend.

But the more I explored it, the more I realized its potential.

AI was not replacing engineers — It was amplifying them.

AI became a productivity multiplier rather than a replacement.

AI became a productivity multiplier rather than a replacement.

I started using AI-assisted development tools to:

  • Accelerate coding
  • Improve productivity
  • Generate ideas
  • Explore solutions faster
  • Reduce repetitive work

AI became a powerful companion in my daily workflow.

The engineers who learn to collaborate with AI will likely define the next generation of software development.

Learning Python and Expanding My Toolkit

The desire to automate and innovate led me to Python.

Python opened new possibilities.

Learning Python was less about a language and more about expanding what I could solve.

Learning Python was less about a language and more about expanding what I could solve.

It allowed me to automate tasks, analyze data, generate reports, and experiment with emerging AI technologies.

Every new skill I learned reinforced a belief that has guided me throughout my career:

Learning is not an event, It is a continuous process.

The day we stop learning is the day we begin falling behind.

Lessons From 11 Years in IT — After more than a decade in the industry, a few lessons stand out.

The most important skill I gained was not a technology; it was the ability to keep learning.

The most important skill I gained was not a technology; it was the ability to keep learning.

  1. Technology Will Change

The technologies I started with are very different from the technologies I use today.

Do not build your career around a single technology.

Build it around your ability to learn.

  1. Adaptability Is More Valuable Than Expertise

Expertise can become outdated.

Adaptability remains relevant.

  1. Prevention Is Better Than Resolution

Fixing issues is important.

Preventing them is even more valuable.

  1. Never Stop Learning

Every major career breakthrough I experienced came from learning something new.

  1. Growth Requires Discomfort

Every significant transformation in my career started with uncertainty.

The willingness to be a beginner again is a superpower.

Looking Ahead

As I write this in 2026, my journey is far from complete.

Technology continues to evolve.

AI continues to reshape software development.

New opportunities emerge every day.

The engineer who joined Cognizant in 2015 working on ESQL/C applications could never have imagined the technologies and challenges that lie ahead today.

And that is precisely what makes this industry exciting.

After 11 years, one thing remains unchanged.

I am still learning. And I hope I always will.


메타데이터
post_id
58d5db5c4e34
slug
lessons-learnt-in-11-years-of-it-58d5db5c4e34
url
https://medium.com/@hariramakrishnan.b/lessons-learnt-in-11-years-of-it-58d5db5c4e34
canonical_url
https://medium.com/@hariramakrishnan.b/lessons-learnt-in-11-years-of-it-58d5db5c4e34
author_url
https://medium.com/@hariramakrishnan.b
status
ok
fetched_at
2026-07-10 00:23:36