My first blog

Few months ago, I made a decision that felt both exciting and uncomfortable.

After 25 years in telecommunications, I decided to expand my horizons and move toward Infrastructure and Cloud technologies.

This blog is a record of that journey.

Where I’m Coming From

My career began as a field engineer. Over the years, I moved into configuration and troubleshooting of TDM and VoIP systems, working extensively with CUCM, CUC, and SBC technologies.

Telecommunications taught me discipline, structured thinking, and the importance of reliability. When communication systems fail, businesses stop. That responsibility shapes how you think about technology.

But the industry is evolving. And so I also should develop myself.

Why DevOps? Why Linux?

The more I looked around, the clearer it became: modern infrastructure runs on Linux. Automation is not optional. Containers and orchestration are standard, not advanced topics.

I realized that if I want to stay relevant and continue growing, I need to deeply understand:

  • Linux (currently focusing on Arch and Ubuntu)

  • Docker

  • Kubernetes

  • Infrastructure concepts in cloud environments

My previous Linux experience was minimal. In many ways, I am starting from zero.

And that is both humbling and motivating.

Skills Over Certificates

Certifications may come later. They are valuable, but they are not my priority.

My priority is understanding.

I want to know how things work under the hood.
I want to break systems and fix them.
I want to build labs, automate tasks, and truly understand infrastructure.

A certificate without skill is paper.
Skill without certificate is still skill.

Why Document This Publicly?

Three reasons:

  1. Writing helps me structure knowledge.

  2. It forces consistency.

  3. It might help someone else considering a similar transition.

Changing careers after 25 years is not common. It raises questions:

  • Am I too late?

  • Can I compete with younger engineers?

  • How steep will the learning curve be?

I don’t have all the answers yet.

But I do know this: growth stops when comfort begins.

The Plan

My goal is to transition into an Infrastructure/Cloud role by the end of this year.

On this blog, I will regularly document:

  • What I learn about Linux (commands, system internals, troubleshooting, scripting)

  • Docker experiments and practical use cases

  • Kubernetes concepts and labs

  • Automation attempts (and mistakes)

  • Lessons learned from building my own lab environments

Expect practical notes. Expect mistakes. Expect progress.

If You’re on a Similar Path

If you’re transitioning from telecom, networking, or another technical field into DevOps or Cloud then you’re not alone.

Experience does not disappear. It transforms.

Troubleshooting mindset transfers.
Understanding of networks transfers.
Responsibility transfers.

Now it’s time to add new layers.

Let’s see where this goes.