JDD (Jenkins driven development) - noun - A development process in which the coder in question has one or two commits to the source code repository adding a feature or fixing a bug, followed by two or three dozen commits to fix things in the comments, unit tests, variable names, or some other such fiddly thing to coax the Jenkins server into actually running the unit tests to exercise the new code and hopefully integrate the new feature.  The primary usage of time by developers in DevOps environments.  The later commit messages usually consist of variations of "Does it work yet?", "WTF …

Warning: Bitter BOFH ahead.

There is a phenomenon I've come to call Ubuntu Syndrome, after the distribution of Linux which has become the darling of nearly every hosting provider out there (and no, I won't call them bloody cloud providers). All things considered, it seems to have a good balance of stable software, ease of use, availability, and diversity of available software. It also lends itself readily to the following workflow:

• Use a tool like packer.io to automagically instantiate a copy of Ubuntu at the hosting provider of choice.
• Never patch the machine under any circumstances.
• Use Chef, Ansible …