DevOps journey and regrets

1. DevOps journey and regrets I have been involved with DevOps in some form or another since around 2019, and I have learned so much over this period. Looking back at myself five years ago, I can’t believe how much I’ve grown as an engineer and a person. I wish I had taken a different route with all of this growth. Things that I advise people not to do when it comes to DevOps. I also feel strongly about many other pieces of advice that I feel strongly about after having experienced them firsthand. Take notes because here are my DevOps Confessions from my personal life. Not using Docker

2. I’ve done programming for a long time, and I was never really interested in containers. My work was on the backend, but as my team got more involved with Docker, I was dragged into the container world. Docker Hub is great and all, but it’s not what made me want to adopt Docker - it was docker-compose. I always liked the idea of containerizing my applications, but I needed more to make me want to use Docker. It’s been many years since we adopted Docker, and our team has grown from just one person working on backend stuff to three people with some experience with containers. We’re able to work much faster because of this change. I recommend all developers out there learn how to use Docker and docker-compose. The learning curve is steep, but once you get it, it’s one of those things that will make you work much more efficiently. So now, when I look back on my old career, a small change could have made everything better. Switching to Docker earlier would have pushed me into a better position. In addition, playing around with containers was an essential part of preparing myself for a new future. A future where we not only write applications but also build infrastructures where those applications can be deployed into production easily using containers and automation software like Docker Hub or Kubernetes. When I see containers today and see how easy they are to set up, I regret ever having thought they were too complicated. All the work, my team, did with containers would have saved us so much time if we had started sooner. And instead of struggling with Vagrant, Ansible, Chef or Saltstack while setting up environments manually over ssh and doing backups every night - imagine if we had started by building images containing application dependencies (think Dockerfile) and then built an automated workflow around that image? Not learning AWS Cloud. In my personal life, I regret not learning AWS Cloud sooner. When we were first working with DevOps and containers, I wanted to learn something other than AWS Cloud because it was different from the servers I was used to. With the momentum of containerization and microservices becoming so prevalent, it seems like a mistake that I should have gotten on board with what seemed like the future of IT. We were also adopting containers at the time. Meanwhile, I didn’t want to focus on multiple things.DevOps journey and regrets Not using Python and NodeJS I wish I had learned Python and Nodejs instead of merely focusing on Java and other JVM languages. I would have been more effective and my code more elegant with these two languages. These languages are more popular today than they were when I started programming at 18 years old. Not automating deployment The spouse of one of my friends called him one day, worried whether she was the problem or something else, explains My friend, who is dealing with the aftermath of not automating his deployment process. She cried, confessed to how resentful she had felt lately with his long hours and lack of intimacy.

3. Not learning of Ansible in early years I found out about Ansible and thought What a great tool! It was the first thing that made my life easy, and I wish I had discovered it earlier. Ansible is an IT automation tool that allows me to manage my IT infrastructure easily. I can create playbooks from my laptop, then run those same playbooks on any of my servers. Not trying DevOps soon I thought being a developer was what I wanted to do, but I was unaware of the life of being a DevOps or SRE person. Since I am working in DevOps, I love it more than any other position. Not committing code early and often Committing code early and often is crucial to the success of any developer’s work. It allows you to have an immediate effect on what you are building. Furthermore, it forces you to think about your changes and how they will impact your project. What can they do? Commit early and often! Conclusion When do you scream at the horror of your confessions because you don’t want to tell people that you’ve done this wrong in life? Remember Murphy’s law which states anything that can go wrong will turn out wrong. Website: https://karandeepsingh.ca/post/devops-confessions- devops-regrets-in-personal-life/