DevOps and Management
Sun, Mar 25, 2018TL;DR: What do you do if your management doesn’t “get” DevOps and Continuous Integration/Continuous Deployment?
TL;DR: What do you do if your management doesn’t “get” DevOps and Continuous Integration/Continuous Deployment?
Lately, I’ve been playing with Lets Encrypt as a means to encrypt public(ish) web-based services I run on my local server. It’s actually remarkable what this non-profit group has accomplished when it comes to SSL - they offer free, automated SSL certificates to anybody who wants them. They even support SAN certificates (those that cover multiple, explicitly-named DNS entries), and starting in January they will offer wildcard certificates. I will tell anybody who is willing to listen, and who is looking to avoid paying paying $50+ for an SSL certificate, about them and encourage everyone to look into their service.
We use Octopus Deploy at my workplace to handle all of our releases. The tool is one of the best I’ve had the pleasure of dealing with, and the more I interact with it, the more I realize just how powerful, yet flexible, it is. I will gladly recommend it to anyone who is looking for a way of releasing any kind of software.
However, there is always room for improvement. In this case, not necessarily improvement with the software package, but how we use it.
This morning I realized that, as programmers, we frequently make assumptions about the software we write which seem to be reasonable, but aren’t completely thought out.
I recently read this really awesome article written by a developer who had no formal education or background and his journey to becoming a front-end developer. Having gone through a somewhat similar transformation, I was inspired to also write about my own transition into programming without a traditional programming background.
Ever since I started programming, I’ve been fascinated with what you can do with a codebase - not just the act of programming, but building and deploying it as well. For a programming company, the less time programmers have to work on building or deploying their code, the more productive they can be. The automation of these things can have a huge benefit.
A fascinating picture, isn’t it? A fuzzy spork. It conjures images that raise far more questions than they answer. What does it mean? What could make a spork fuzzy? Is it safe? Is it supposed to be like that? Is it really a fuzzy spork or is it a sporked fuzzy? Where are the adults?