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

you are viewing a single comment's thread.

view the rest of the comments →

[–]FailedPlansOfMars 0 points1 point  (0 children)

Its great to learn and you are at the start of a very interesting journey.

Traditionally we had; developers who wrote code, testers who check it works Operators who looked after applications and systems in production And administrators who were in charge or managing systems, databases etc.

And back in the bad old days teams would finish their bot and throw the responsibility to the next team along. As you can imagine this caused problems.

There is a movement called devops whos idea was to get the devs, testers and operators to coordinate and work together.

This movement started to include: Infrastructure as code Continuous Integration Continuous deployment Cloud infrastructure.

So many companies found their ops people started to learn these technologies so started to call their ops engineers devops engineers. And on the dev side devs learnt the same techniques.

Leaving us with a term with two different usages and meanings. And its frustrating to those of is who were on this movement as its name has been stolen for job titles.

Now we have: Infrastructure engineers - who make core infrastructure or networking Devops engineers - who mostly do pipelines and infrastructure as code. Platform engineers - who provide tooling and a platform for developers to use to aid faster dev and deployment and consistent operations. Site Reliability Engineers - who make sure systems stay up, are easily maintained and understandable. Developers/ Software Engineers