This blogpost is a first stab at providing a structure to codify devops practices. The wording, descriptions are pretty much work in progress, but I found them important enough to share to get your feedback.
We’ll move past the fluffy characterization involving developers and operations working together joyously—not to mention the outright wrong characterization of one superrole that does it all—and get to the heart of what devops is really about.
In Agile programming, one of the basic concepts is to run unit tests every once in a while (multiple times in a day on developer boxes) and enforce the integration tests to run once a day (on continuous integration server rather than on developer boxes).
Facts
18 chapters, 254 pages, $29.21This book covers Specifications by Example (you could have guessed
it from the title). In effect, SBE are a way to build the right software
(for the...
There can be friction between the various ways agile teams work, and it seems that the root of the conflict between agile and continuous delivery is the approach to making software "ready for release."
This week’s SANS AppSec conference in Las Vegas took on Application Security at Scale: how can we scale application security programs and technologies to big organizations, to small organizations and across organizations to millions of programmers world wide.
Back in the days when I had my lack of experience as an excuse to explain my mistakes I was sometimes wondering: “Wouldn’t it be nice to have a mentor?”
Steven Lott has been refurbishing an older project, built using Django 1.0.1 and Python 2.5, to make it compatible with Django 1.3. In this post, Steven explains the process he took, and why he loves deleting old code.
The general best practice is to add an additional element for each service tier, also know as N+1 redundancy. This approach is straight forward, but many people would actually be surprised by how often these schemes fail.
Hiring new people for a team should always be a joint decision that involves team members. After all, who has more at stake than the people who will work with the new person day in and day out?
My company designs and develop mobile and web based banking solutions. Our customers (banks for the most part) are highly bureaucratized, orthodox (ie. like to have everything pre-defined and pre-approved) and risk adverse, and therefore change and the disruption of the status quo is not a normal sight within most of them.
Gitosis-ng — it’s gitosis with some new features to help users work with the git server. Mainly implemented with commands sent via ssh. Here's what you can do with it.