This definitely applies to Puppet code, you have Puppet classes to encapsulate functionality, and modules that group classes together for reuse and redistribution.
In Continuous Delivery, each build is potentially shippable. This implies a lot of things.
In the current age of software development the phrase "technical debt" has become part of the common vocabulary.
A few libraries need to be installed prior to the installation of Git...
After considering different alternatives, we eventually settled on using the ratio (today’s count + 1) / (yesterday’s count + 1). This solves the zero denominator problem without unduly skewing the ratio.
Let's assume you have just bought the memorable domain name idrinkink.org and you want to host your lovely web app on that old server in the shed.
Imagine that you’re a Hadoop administrator, and to make things interesting you’re managing a multi-tenant Hadoop cluster where data scientists, developers and QA are pounding your cluster.
There is a real convergence occurring, one that sees a new breed of organization, a changing environment within which those organizations operate, and a new type of demand upon those within the organization tasked with delivering the business needs.
When we want to understand some lovely, Java code, we read it. Sometimes, however, a slightly higher perspective helps to show us the patterns that reading alone may hide.
Are you interested in introducing BDD to your team? Don’t try and do it like this under these circumstances. Learn from my failure.
As part of my role at a new company I’ve been asked to provide feedback about structuring Dev & Ops as well as what sorts of things work and don’t.
The essence of software engineering, in my opinion, can be captured in two words: managing complexity.
Test Driven Development, Behaviour Driven Development, Extreme Programming and many other new-age hippie methodologies have spread through the dev world like wildfire. I believe there's room for one more.
On Friday Nathan and I were setting up a new virtual machine and we needed a firewall rule to be created to allow us to connect to another machine which had some JAR files we wanted to download.
At deployment time, we’re worried about a new set of dependencies. That web application probably depends on other components in order to function properly.
Everything in getting my personal site setup went fairly smoothly, including updating my registrar’s DNS records to point my domain name at my hosting provider.
I make a lot of jokes at work about code review karma. Here's the idea: each time a person volunteers to review others' code, that person build their code review karma.
As IT systems become an important competitive element in many industries, technology assets are influencing more and more parts of any organization.
Eric Minick from urbancode supplies a slideshare on managing build time dependencies.
In our Fabric code we make use of Boto to connect to the EC2 API and pull back various bits of information and the first time anyone tries to use it they end up with the following stack trace.
As I write this, I’m sitting in a half-empty office in London. It’s half empty, you see, because it’s snowing outside, and when it snows in London, chaos ensues.
Earlier in the week, I presented a webinar on managing build time dependencies which is now available as a recording.
I have a client who is very firm on the idea that the user should know what went wrong when exceptions are thrown.
Etsy Labs' fantastic Code as Craft series explores Etsy's strategies for moving fast at scale.
Some of the ugliest things that happen to code don’t have anything to do with technical debt. They’re the result of conscious and well-intentioned design changes.