Skip to main content

Command Palette

Search for a command to run...

Day to Day activities for a DevOps Engineer

Published
โ€ข3 min readโ€ขView as Markdown
P

๐‘ช๐’๐’๐’–๐’… ๐’‚๐’๐’… ๐‘ซ๐’†๐’—๐‘ถ๐’‘๐’” ๐‘ป๐’†๐’„๐’‰ ๐‘ช๐’๐’Ž๐’Ž๐’–๐’๐’Š๐’•๐’š || ๐‘ท๐’“๐’๐‘ซ๐’†๐’—๐‘ถ๐’‘๐’”๐‘ฎ๐’–๐’š ๐Ÿค– https://t.me/prodevopsguy ๐Ÿ‘‹ Hi there! We are ProDevOpsGuy, a passionate DevOps enthusiast Tech Community with a strong belief in the power of automation and collaboration to drive innovation. ๐Ÿš€ I thrive in bridging the gap between development and operations, creating seamless and efficient software delivery pipelines. My journey in the world of DevOps has allowed me to blend my technical skills with a knack for problem-solving, enabling me to contribute effectively to agile and dynamic environments. ๐Ÿ’ก With a keen interest in continuous integration, continuous delivery (CI/CD), containerization, and orchestration, I've had the privilege to explore cutting-edge technologies like Docker, Kubernetes, Jenkins, and Ansible. I find joy in designing scalable and resilient infrastructures that enable teams to deploy applications faster and with greater confidence. ๐ŸŒ Beyond the tech realm, I'm an advocate for DevOps culture, emphasizing collaboration, communication, and a relentless pursuit of improvement. I'm always eager to connect with fellow professionals, exchange insights, and explore opportunities to collaborate on exciting projects. ๐Ÿ“š When I'm not tinkering with the latest DevOps tools, you can find me indulging in books on technology trends, hiking to rejuvenate, and occasionally experimenting with new coding challenges. ๐ŸŒŸ Let's connect! Whether you're looking to discuss DevOps methodologies, explore partnership opportunities, or simply share experiences, feel free to reach out. I'm excited to be part of the DevOps journey, driving excellence together.

  1. Make sure that the pipeline is running smoothlyโ€Šโ€”โ€ŠThis is one of the most important tasks of a DevOps engineer to make sure that the CI/CD pipeline is intact and fixing any issue or failure with it is the #1 priority for the day. They often need to spend time troubleshooting, analysing and providing fixes to issues.

  2. Interaction with other teamsโ€Šโ€”โ€ŠCoordination and collaboration is the key for DevOps to be successful and hence daily integration with the Dev and QA team, Program Management, and IT is always required.

  3. Work on Automation Backlogโ€Šโ€”โ€ŠAutomation is the soul of DevOps so DevOps engineering need to plan it out and I can see DevOps engineer spending lots of time behind the keyboard working on Automating stuff daily.

  4. Infrastructure Managementโ€Šโ€”โ€ŠDevOps engineers are also responsible for maintaining and managing the infrastructure required for the CI/CD pipeline and making sure that itโ€™s up and running and being used optimally is also part of their daily schedule. Working on Backup, High Availability, New Platform setup etc.

  5. Dealing with Legacy stuffโ€Šโ€”โ€ŠNot everyone is lucky to work on the latest and newest things and DevOps engineers are no exception hence they also need to spend time on legacy i.e., in terms of supporting it or migrating to the latest.

  6. Explorationโ€Šโ€”โ€ŠDevOps leverages a lot from the available various tools, there are many options as open source, so the team needs to regularly check on this to make sure the adoptions are as required, this is something that also requires some effort not daily but regular basis. What are open-source options available to keep the cost at a minimum?

  7. Removing bottleneckโ€Šโ€”โ€ŠDevOpsโ€™s primary purpose is to identify the bottlenecks / Manual handshakes and work with everyone involved (Dev / QA and all other stakeholders) to remove them so the team spend a good amount of time in finding such things and build the Automation Backlog using this. How we can get builds faster?

  8. Documentationโ€Šโ€”โ€ŠThough Agile / DevOps stresses less on the documentation, it is still the important one that DevOps engineer does on daily basis, Be it Server Information, Daily Week chart, Scrum / Kanban board, or Simple steps to configure / backup or modify the infrastructure, you need to spend a good amount of time in coming up these artefacts.

  9. Training and Self Developmentโ€Šโ€”โ€ŠSelf-learning and Training are very useful in getting a better understanding and many organizations encourage their employee to take the time out and do some of these and same holds for DevOps folks as well, So learn something new every dayโ€ฆ

  10. Continuous Improvement as Practiceโ€Šโ€”โ€ŠLast but not least, Itโ€™s up to the DevOps folks to build awareness of the potential of CI/CD and DevOps practices and building a culture of leveraging it for doing things better, reducing re-work, increasing productivity and optimizing the use of existing resources.

If you find this article helpful then you can buy me a coffee

Follow for more stories like this ๐Ÿ˜Š/ GitHub

More from this blog

P

ProDevOpsGuy Tech Community

73 posts

Home of DevOps Best Blogs/Series

Day to Day activities for a DevOps Engineer