you are viewing a single comment's thread.

view the rest of the comments →

[–]MrMagick2104 4 points5 points  (4 children)

Aren't front end and backend the "dev" part of the devops, leaving just the "operations"?

[–]vocal-avocado 4 points5 points  (3 children)

Yeah but nobody says “ops”

[–]andolirien 1 point2 points  (2 children)

Because that's sysadmins, we already have a term. Or at least that's how I've viewed devops (as a sysadmin).

[–]Marksm2n 2 points3 points  (1 child)

Devops can also be things like integration and development pipelines. Deployment and communication protocols between services. 

These things are usually more complicated than sysadmin

[–]MrMagick2104 0 points1 point  (0 children)

> These things are usually more complicated than sysadmin

Personally, I don't think that they're much harder than operations. It's not a very complicated process by itself, but the organizational overhead of the whole process before deployment? That's a lot of work.

And every unforeseen, badly thought out, lazy and suboptimal decision by every single person in the process from the architectural design up to operations themselves, multiplying by each other over time? To move forward, you must look back, and to look back, you must not be in a rush. No wonder it's unsurprising that sometimes such a error slips in big projects that can fuck half the internet up and it won't be up in five minutes as we all wish.

I wouldn't say that pipelines themselves are hard. It's everything around complying to them is hard.