• submit to reddit
Jim Bird05/21/12
1 replies

Software Development Metrics that Matter

How can we get better, or know that we need to get better, or know if we are getting better, if we can’t or don’t measure something? How can we tell if a new approach is helping, or make a business case for more people or a rewrite, or even justify our existing costs in hard times, without proof?

John Dobie05/17/12
0 replies

Easy Unit and Integration Code Coverage

This example shows how to generate coverage for unit and integration tests using Maven and Sonar. It uses very simple techniques and should only take 10-15 minutes to get running in any existing Maven build.

Patrick Debois05/15/12
1 replies

Codifying DevOps

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.

Willie Wheeler05/13/12
1 replies

Devops: What it is and Why you Should be Doing it

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.

Partha Bhattacharjee05/13/12
0 replies

Categorize tests to reduce build time.

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).

Nicolas Frankel05/09/12
0 replies

Specification by Example review

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...

Kief Morris05/09/12
1 replies

Continuous Delivery vs. Traditional Agile

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."

Giorgio Sironi05/09/12
0 replies

Lean Tools: the Last Responsible Moment

Delaying commitment is good to mitigate risk: but delaying commitment does not mean never make a decision.

Jim Bird05/08/12
0 replies

Application Security at Scale

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.

Giorgio Sironi05/07/12
0 replies

What is global state?

Globale state: it's everywhere, but its mutability is the real danger.

Jens Schauder05/06/12
1 replies

Where is your Mentor?

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 Lott05/03/12
1 replies

My Django Application Refresh: The Joys of Deleting Code

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.

Geoffrey Papilion05/03/12
0 replies

Redunancy Planning - A Guide to What's Right for You

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.

Giorgio Sironi05/01/12
0 replies

Lean tools: Options thinking

Starting to decide as late as possible requires small investments in time and money, to buy options.

Esther Derby 05/01/12
0 replies

Hiring is a Team Activity

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?