Happy New Year.
If you can’t dispose of toxic waste (say, by burning it or launching it into space using surplus ICBM’s), then you probably need to contain it: stop innocents from stumbling across it, or stop the malicious from using it for malicious projects.
The same issues apply to your source tree. If you have Amazon Web Services credentials checked into a project on GitHub, that’s a toxic repo. You’ll want to contain to protect people from intentionally or unintentionally damaging the resources that can be accessed from the credentials.
One of the problems of having your own toxic waste dump, is that it’s very easy to add more waste to the pile. So that repo with a private key checked in might easily get an AWS credential, and a couple of months later, a raw database password.
Another is that sometimes, you might give the wrong people access.
What can you do about it?
Cleaning up some toxic waste yesterday was pretty good. That’s one less dirty secret.
So, I return to New Zealand. Spend most of a year hiding in a cabin and then fail to organise any events. And now they’ve all come at once:
2013 was busy. It’s hard to work remotely with people who are literally on the other side of the planet. Remote helps explain why: there’s no overlap, apart from what overlap I make myself.
To make things more busy, we ended up buying a new Build Doctor HQ and moving from the country to the suburbs. Moving from a cabin back to the spare room has it’s comforts. Like plumbing. There’s a lot of work to do on the HQ, but it’s nice to have a new long term project.
This blog is a long term project, too. The last couple of years have seen it slide as I worked on other things and moved country. It’s no longer sponsored, and pursuing sponsorship doesn’t work when I haven’t been posting. I almost ported to Ghost, but decided that I’d take the simplest option of moving it to wordpress.com and letting the content speak for itself.
A benefit of the move is saying goodbye to the www in the blog URL, which fixes a mistake made in 2007. That and never having to do another plugin update.
Now I just need to find something to write about.
Happy 2014. Have a happy and productive year, wherever you are.
(A guest post by Dan Gordon of Electric Cloud)
Enterprises are building, testing, and deploying software faster and more frequently now than at any point in the past. Faced with unprecedented demands, many of these software development organizations are realizing their rollout processes are haphazard, at best. These improvised procedures lead directly to heightened numbers of costly, time-consuming errors that degrade their business agility. Production deployments remain the last mile hurdle in the agile world due to the disconnect between the Dev and Ops teams.
Fortunately, there is a well-regarded, proven collection of best practices and supporting technologies that can go a long way towards making the software deployment process more streamlined, safer and more robust. These fail-safe software deployment techniques deliver an impressive array of business and technological advantages.
These techniques can make your software deployment experience faster, smoother and more reliable. By transforming complex software delivery processes into fail-safe production deployments, you will benefit from increased DevOps collaboration, reduced cost and a higher quality of delivered software.
Dan Gordon is a Product Manager at Electric Cloud. Dan brings over 20 years of experience in the IT software industry. At Electric Cloud, Dan is responsible for product strategy, product marketing, tactical alignment and execution with product development, sales and pre-sales enablement and support. Previously, Dan was a product manager and systems architect for the enterprise IT automation software business within HP Software. Dan has also held managing and systems engineering roles at Opsware and Sun Microsystems. Dan holds a bachelor of science in information and computer science from the University of California, Irvine.
Happy summer, Northern Hemisphere dwellers. There’s a break in the rain at Build Doctor South HQ, have some news:
My blogging break has been so long, I feel like a vampire emerging from the grave in a Hammer Horror film.
I’m interrupting my relentless working day to announce that I’ll be at:
Back to flogging Ruby code.
Update: for various reasons, both the struck out appearances are cancelled. Back to flogging ruby code. (I do actually use flog).
We’re looking for someone to help extend and run our Cloud platform.
This is a role in a small team with lots of autonomy: we want to build an awesome cloud service to match our awesome product. We’re funded, we’re selling our product like hotcakes and we want you. Link below.