Industrial Blogic

× Warning: this blog contains ugly code requiring horizontal scroll bars. Viewer discretion advised. Yesterday, we found the following badass query in our CompletionStatusRepository class:

A product metaphor shapes the look and behavior of a product, integrates the product's features and inspires new functionality. If you value metaphors, a single word can inspire your entire product.

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.

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.

Smells to Refactorings Cheatsheet (.pdf) We developed this handy cheat sheet as a teaching aid while teaching our Refactoring Challenge Activity. You'll find a table that maps code smells to their likely refactorings with corresponding page references to source material contained in the books Refactoring: Improving the Design of Existing Code by Martin Fowler and [...]

Stop Over-Engineering (.pdf) Patterns are a cornerstone of object-oriented design, while test-first programming and merciless refactoring are cornerstones of evolutionary design. To stop over- or under-engineering, balance these practices and evolve only what you need.