Industrial Blogic

Continuous Deployment (CD) and Test-Driven Development (TDD) are two of the most powerful practices we use at Industrial Logic. Both of these practices help us rapidly deliver value to users while significantly reducing the stress of programming and releasing to our production environment.

Over the last few months, we here at Industrial Logic have been working hard on a new album called Sessions. This new album allows you to visualize, quantify & critique your programming sessions.

For many years, I've found students in a situation I call False Green.

I’m so often asked: “When microtesting, doing TDD, is it okay to test a private method?” The answer, at least literally speaking, is no! Let me explain. Imagine I begin test-driving a new object. As I consider my first test, I have to answer a design question: “What does this object do?”

This Google TechTalk (from June, 2009) introduced Industrial Logic’s eLearning to Googlers. Video Duration: 56 minutes Software programming rock stars test-drive their code, refactor mercilessly and deftly apply design patterns. If you’d like to get from musician to rock star status, a good place to start is Industrial Logic’s eLearning albums.

How do we know if someone is truly learning Refactoring and Test-Driven Development? Before 2005, we determined proficiency by literally looking over people's shoulders as they worked. In 2005, we endeavored to automate the "looking-over-the-shoulder" part. We built code that used reflection to automatically check whether a student's solution met certain design criteria.

Storytest-Driven Development Article (.pdf) This article, which appeared in the July/August 2004 issue of Better Software magazine, features descriptions of storytest-driven development, quotes from pioneers and early adopters, as well as side-bars on how to get started.