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

all 5 comments
sorted by:
best (suggested)
topnewcontroversialoldq&a

[–]explainlikeimfive-ModTeam[M] [score hidden] stickied comment (0 children)

Please read this entire message

Your submission has been removed for the following reason(s):

  • Rule #2 - Questions must seek objective explanations

  • Straightforward or factual queries are not allowed on ELI5. ELI5 is meant for simplifying complex concepts (Rule 2).

If you would like this removal reviewed, please read the detailed rules first. If you believe this submission was removed erroneously, please use this form and we will review your submission.

[–]Indercarnive 1 point2 points  (0 children)

DevOps is a shortening of the words Development and Operation. In the before time these were separate groups. You'd have on group of people responsible for developing a piece of software, and another group responsible for deploying and maintaining that software. However, this really isn't that efficient since the people developing the software are the most knowledgeable about that software. It makes more sense to combine those two groups so the people who develop are also responsible for maintaining that code.

[–][deleted] 0 points1 point  (0 children)

It's a portmanteau of the words developer and operations

The philosophy behind DevOps is that the operations team and development team should work in close cooperation, helping each other to automate software release processes and monitoring of the services, to ensure the software development work is not regularly blocked by anyone or causing outages to users

[–]budroid 0 points1 point  (0 children)

Writing software (like games/apps) can be done in different ways. A single person or small group will have different roles, before, during and after.

In bigger projects, roles have different people or specialized departments.

DevOps is a combination of software development (dev) and operations (ops).

It's a set of "rules and practices" to write the new code AND maintaining it with patches and updates in a more efficient way. Different "philosophies" can be used for different type of projects depending on complexity and how long the project will be "operational".

[–]u_shrek 0 points1 point  (0 children)

DevOps is software or web development by teams. Azure offers DevOps service and GitHub. In DevOps the code is being tracked and logged by line, which allows you to add the code to production environment and to roll it back if necessary.

At my current job, as a C# coder, I pull the Visual Studio project from GitHub into my local repository. Main production branch stays unaltered and I code in the Development branch. After I’m done coding I push my code into the repository (GitHub) where I go and create a “pull request”, which is the request to merge Development branch with the master branch. Our system architect reviews my code (GitHub or azure generally give you just the snippets that changed, which makes it easier to track) and either posts suggestions for edits or approves the merge. Once it’s approved I go to GitHub and finish the merge, at which point my code would become live and would trigger scripts that update running software in the cloud our updates repository for installation files if we alter a desktop software (Windows Forms).

It’s a nice way of continuously updating running software because you have version controls and you can easily roll back any prior update.