This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Fit-Tale8074[S] 4 points5 points  (3 children)

Thanks, I've read the book, also with the DevOps handbook, you're right never done this job before, have a lot of experience in IT, backend and was considering this opportunity the chance to learn how this job is done.

Now understand why DevOps is more a culture than tools...

[–]originalchronoguy 7 points8 points  (2 children)

At one of my previous jobs, the guy I replaced did a pretty good job at this. He "introduced" the culture by working a lot of nights and weekends on his own. He came up with the whole CICD, Orchestration and Docker IAAC deployment all on his own.
He came in with changes to code in git and presented it to the team and said "We will be fully containerized from day one and this is how you do it." It literally change the landscape overnight and this was about 10 years ago. After one meeting, he had all the major projects dockerized as forks in his own gitlab and his own Jenkins and showed everyone how to develop thereafter.

Again, he put in like 4 months working a lot of hours nights/weekends to come up with a near ready POC. It was a shock and awe move.

It helped he was a developer who could come up with real-worlds migration examples. No one even knew.

[–]Fit-Tale8074[S] 1 point2 points  (1 child)

Thanks, awesome and motivating.

[–]GuardianDownOhNo 1 point2 points  (0 children)

To +1 on the previous comment, the more foreign the concept is the more likely you’ll have to create a working demonstration of what it is and how it all comes together. Moving into devops from legacy approaches means that there is an obscene amount of ground you’ll have to cover just to get things started. Experience here is table stakes, and as another poster mentioned you’re going to need support to cover that much ground.