My Journey from Electronics Repair to DevOps Engineering
LinkedIn
Facebook

I’ve always been fascinated by technology. My career started as an Electronics Repair Engineer, with a huge passion for anything computers related. Over the years, I transitioned through various roles, each adding a layer of expertise and experience, ultimately leading me to my current position as a DevOps Engineer. 

 

In this article, I will share my experience of moving from electronics repair to IT support and finally to DevOps. I hope my story will inspire and guide those who are contemplating a similar career path or are simply curious about the world of DevOps. 

From IT Support to DevOps: The Beginning 

My professional journey began in the world of electronics repair. I was always fascinated by how things worked and enjoyed the challenge of fixing them. This passion led me to start my own electronics repair business, where I honed my technical skills and learned the intricacies of managing a business. During the Pandemic, everything changed. I transitioned into managing the service and repairs department for a big computer retailer. This role was pivotal as it allowed me to bridge my electronics knowledge with computer systems and networks. My curiosity and desire to delve deeper into IT led me to join the support department of a gaming company, where I went deeper into networking and on-premise server management. 

Working in IT support was an enriching experience that provided me with a strong foundation in troubleshooting, customer service, and technical problem-solving. However, I soon realised that I wanted to be more involved in the development and operational aspects of IT, which led me to explore the field of DevOps. The more I read and learned about it, the more it fascinated me. 

Acquiring the Right Skills 

I knew I wanted to move into DevOps, so I made sure everyone around me knew it too. One day, I got a call from a former colleague, who works at BoatyardX. He told me their DevOps team was growing rapidly and needed someone to handle support tasks. He asked if I would be interested in taking over those tasks and gradually transitioning to DevOps. I jumped at the opportunity. 

While performing IT support at BoatyardX, I was introduced to the world of DevOps by my colleagues. I had some basic knowledge of Linux, but it was here that I really dove into it, learning the ins and outs of  bash and bash scripts. Once I had a solid foundation in Linux, I moved on to learning virtualisation (VMware ESXi and NSX-T), Ansible, Docker, and eventually cloud technologies like AWS and Azure. As I progressed, I tackled Terraform and Kubernetes. 

I also learned about the myriad of in-between technologies, like web servers (Apache and NginX), certificates, monitoring tools (Nagios, Prometheus, Grafana) infrastructure access platforms (Teleport), and so many more. Additionally, I was exposed to the full spectrum of working methodologies, from traditional Waterfall to Agile and Scrum. This experience broadened my understanding of project management and team collaboration. 

The Challenges 

At first, the plethora of projects and technologies my colleagues were working on was overwhelming. I was 42 when I joined BoatyardX, and my concern was: when will I have the time to learn all these? Did I make a mistake? Am I too old for this? Here is where my previous electronics repair experience kicked in: in electronics, to be proficient, you have to understand the basics, from the laws of electricity to basic electronic components and circuits. To fix something, you have to know how it works, in detail. 

 

My Eureka moment in DevOps was when I realised that I needed to understand the software development processes. How a web application is coded, how it is built, how it is deployed, how it communicates with various databases, and how it is maintained and updated continuously. Understanding these fundamentals was key to overcoming the initial overwhelm and mastering the tools and technologies in DevOps. And for me there was no other way, than hands-on trial and error, built on lots of documentation reading. I started by coding my own simple app in Python, then I ran it locally, containerised it, deployed the image manually to a container registry, and so on and so forth, until I had my own infrastructure up and running, in AWS and in Azure.  


It was funny for me how I found the time for all these experiments. I love PC strategy games, and I spend a big chunk of my free time lost in them. I treated the entire app deployment and infrastructure building process as a strategy game, and my play switched from Sid Meyers Civilisation to Microsoft Azure Cloud, and from managing virtual empires to managing virtual infrastructures. 

A Day in the Life of a DevOps Engineer and Its Impact

Transitioning into the DevOps role at BoatyardX has been transformative, with collaboration at the core of my daily work. Unlike previous individual-focused roles, DevOps thrives on teamwork and constant communication. This dynamic has strengthened my relationships and fostered camaraderie among my colleagues.

My days are a mix of maintaining systems and experimenting with new tools, ensuring a continuous learning experience that keeps me engaged. I’ll never forget the thrill of launching my first pipeline—it was like winning the lottery. Alongside technical work, mentorship has been a significant part of my journey. I lean on experienced colleagues for guidance, while also sharing my own insights with newer team members. This exchange highlights the flexible, problem-solving nature of DevOps, where there’s often no one “right” solution.

 

Balancing work and personal life is key to maintaining my enthusiasm, and time with family and hobbies help me recharge.

 

 

Reflecting on my achievements, building relationships and trust with my team has been the most rewarding. Celebrating successes, learning from failures, and the support of my team have made this journey fulfilling, underscoring the value of resilience and continuous growth.

Advice for Aspiring DevOps Engineers 

Transitioning into DevOps has been a rewarding journey, and I’d like to share some advice for those considering a similar path. This isn’t just about the technical skills; it’s also about the mindset and approach to learning and growing in this field. 

 

  • Embrace Continuous Learning The world of DevOps is vast and constantly evolving. Don’t be afraid to start small and gradually build your knowledge. Take advantage of online courses, tutorials, and certifications. More importantly, learn by doing. Hands-on practice is invaluable. 
  • Leverage Your Background No matter your previous experience, it can be relevant. My background in electronics repair and IT support gave me a unique perspective and problem-solving skills that proved beneficial in DevOps. Identify and leverage your strengths. 
  • Seek Mentorship and Community Find mentors who can guide you through your learning curve. Join DevOps communities online or in-person to connect with others in the field. These relationships can provide support, knowledge, and encouragement. 
  • Be Patient and Persistent The transition to DevOps can be challenging, especially if you’re learning new technologies. Be patient with yourself and persistent in your efforts. Every mistake is a learning opportunity, and perseverance will pay off. 
  • Focus on Fundamentals Understanding the basics of software development, networking, and system administration is crucial. These fundamentals will help you grasp more advanced concepts and tools used in DevOps. 
  • Balance Work and Life It’s easy to get consumed by the demands of the job, but maintaining a healthy work-life balance is vital. Make time for hobbies and relaxation. This balance will keep you motivated and prevent burnout. 
  • Communicate and Collaborate DevOps is a collaborative field. Develop your communication skills and work effectively with others. Being able to explain your ideas clearly and listen to feedback is essential. 
  • Stay Curious and Innovative Always be curious and look for innovative solutions. The field of DevOps thrives on creativity and innovation. Experiment with new tools and techniques to find what works best for you and your team. 
  • Reflect and Celebrate Progress Regularly reflect on your journey and celebrate your achievements, no matter how small. This reflection helps you recognize your progress and stay motivated. 

For me, the main aspect of these achievements lies in the relationships and trust built along the way. Working closely with my team, we celebrated our successes together and learned from our failures. The camaraderie and shared sense of purpose created a supportive environment where everyone felt valued and motivated. These experiences have taught me the value of resilience and continuous learning. The support from my team, the satisfaction of solving problems, and the thrill of learning new technologies have made this journey incredibly fulfilling. 

In conclusion, transitioning to DevOps is a journey of continuous learning and personal growth. Embrace the challenges, seek support from your community, and always keep a positive attitude. Your unique experiences and skills are your greatest assets in this field. I hope my story inspires and helps you on your own path to becoming a DevOps Engineer. 

Read more tech topics