How I Became DevOps Engineer with no IT Background in under 7 months by Andalusian Horseman TheDevOpsGuy

Then I landed a job in the finance team of a retail company called Selfridges. Now I am touching Docker Swarm (I kind of failed at learning Kubernetes when it came to storage types, so I feel like starting from Swarm is a better way). DevOps’ rise in popularity grew with the publication of books like The Phoenix Project by authors Gene Kim, George Spafford and Kevin Behr. Published in 2013, the https://remotemode.net/become-a-devops-engineer/ book is a narrative-style novel that follows a fictional American company going through a digital transformation. Below is a timeline of the history of DevOps and major moments that have helped develop the concept. So you can of course learn this as I said all by yourself following those steps and put a learning path together by yourself or you can use our prerequisites course when it’s out.

• Another common background people have when transitioning into DevOps is a test automation engineer.
• There are several actions that could trigger this block including submitting a certain word or phrase, a SQL command or malformed data.
• So basically learning Docker and Kubernetes to help your teams deploy and efficiently run the application.
• If you don’t understand those, you won’t know what you’re automating or why you even need DevOps.

This mainly stems from the fact that my father was a software engineer and whatever he did to his computer I did it to mine, albeit in a more chaotic way. For now I managed to setup a good Jenkins pipeline using nested containers across many nodes, it was not that hard except few docker quirks. Once unpublished, all posts by techworld_with_nana will become hidden and only accessible to themselves.

Do most of devops people have a background in being a developer?

So again a part of DevOps skillset is to create a process of handling discovered issues in production instead of having a panic mode. 2.2 – Containers with Docker
And as part of the more modern infrastructure concepts you need to understand how to work with containers and the https://remotemode.net/ most popular container technology, which is Docker. What it means in a nutshell is that you as an engineer will now be doing the work of Developers and Operations. In simple terms, Developers create code and Operations test the code before integrating into the pipeline.

Now here you may have a bit more catching up to do and more skills to learn compared to developers or systems administrators, but you can definitely reuse many of your skills in DevOps. Since I started to learn Docker, during writing any dockerfile I felt like I am doing something that was not a typical developer or devops job; It was something between. While knowing how to run a website using nginx or apache is typical devops, the contenerization aspect feels not as its Software architecture as code and this is relatively new for me. Obviously as a system administrator you would skip that part, but instead you would need to learn Git and how to work with Git workflows, to use it for writing infrastructure as code for example.

Devops Background Vectors

If techworld_with_nana is not suspended, they can still re-publish their posts from their dashboard. Once unsuspended, techworld_with_nana will be able to comment and publish posts again. Once suspended, techworld_with_nana will not be able to comment or publish posts until their suspension is removed. This includes Day 0 activities such as initial setup of the infrastructure, but also Day 1 tasks like maintaining and operating this infrastructure. So these are the fundamental processes and respective tools that are part of DevOps.

So depending on which background and pre-knowledge you have, you need to first make sure to get any missing prerequisite knowledge. This means before you automate processes and tasks that are done manually, you first need to understand what those processes and tasks are in the first place. If you don’t understand those, you won’t know what you’re automating or why you even need DevOps. Finally, we also get many questions about starting our DevOps Bootcamp with very little to no IT background. Which means there are probably many of you reading this article, who are thinking about getting into DevOps without much IT pre-knowledge and want to know what the path is to DevOps.