March/April 2019 issue of acmqueue The March/April 2019 issue of acmqueue is out now

Subscribers and ACM Professional members login here



Research for Practice

Development

  Download PDF version of this article PDF

Error 526 Ray ID: 4ec130d89ad8ccf6 • 2019-06-24 19:43:28 UTC

Invalid SSL certificate

You

Browser

Working
Newark

Cloudflare

Working
deliverybot.acm.org

Host

Error

What happened?

The origin web server does not have a valid SSL certificate.

What can I do?

If you're a visitor of this website:

Please try again in a few minutes.

If you're the owner of this website:

The SSL certificate presented by the server did not pass validation. This could indicate an expired SSL certificate or a certificate that does not include the requested domain name. Please contact your hosting provider to ensure that an up-to-date and valid SSL certificate issued by a Certificate Authority is configured for this domain name on the origin server. Additional troubleshooting information here.

acmqueue

Originally published in Queue vol. 17, no. 2
see this item in the ACM Digital Library


Tweet


Related:

Natasha Noy, Yuqing Gao, Anshu Jain, Anant Narayanan, Alan Patterson, Jamie Taylor - Industry-scale Knowledge Graphs: Lessons and Challenges
Five diverse technology companies show how it's done


Ivar Jacobson, Roly Stimson - Tear Down the Method Prisons! Set Free the Practices!
Essence: a new way of thinking that promises to liberate the practices and enable true learning organizations


Alpha Lam - Using Remote Cache Service for Bazel
Save time by sharing and reusing build and test output


Jez Humble - Continuous Delivery Sounds Great, but Will It Work Here?
It's not magic, it just requires continuous, daily improvement at all levels.



Comments

(newest first)

David M. Karr | Wed, 05 Jun 2019 22:21:31 UTC

The DevOps notion is very popular in forward-looking large and small enterprises, for good reason. Another theme that is very prominent is security. Unfortunately, there's at least one way where these two notions work against each other. Typically in large enterprises, it is common to carefully define the role of each employee and even audit how well those limitations are followed, to prevent people from having more access to systems than they need to. If someone is a developer, they're not allowed to have access to operations. Managers are not allowed to see code in repositories (much less change it).

If these rules are strictly followed, any benefits from a DevOps approach will be severely diluted. You certainly won't see developers being allowed to troubleshoot or implement operations changes, and it's unlikely that operations personnel will have a very good perspective on what developers need to do their job.

These rules might not prevent "communication" across the divide, but what is the point if neither side really has much to do with the other?


Leave this field empty

Post a Comment:







© 2019 ACM, Inc. All Rights Reserved.