“Emily’s talks on Clean Code gave us a big push towards Software Craftsmanship. Her lightning talks followed by provoking questions stirred up many interesting discussions."

Arnulf Krokeide, Software Architect, Confirmit, Oslo

"I had the great pleasure to assist Emily to arrange JDojo@Gbg Coding Dojo meetings. She's an excellent facilitator, perfectly balancing the level of tutoring and stepping back to let the participants "learn by doing". 

Fredrik Wendt, co-organizer of JDojo@Gbg

“When I have been asking about feedback around this Coding Dojo course, people are very satisfied. They think that everyone in the house should have to take it. Really valuable.”

Martin Andersson, Manager, Software Engineering at Jeppesen

I brought in Emily to work with the team on issues around Clean Code, Test Driven Development and Refactoring. Her presentation of the material was always very professional and the structure of the sessions allowed for a lot of interaction and reflection. The feedback from the participants has always been very positive.

Isak Styf, Software Team Leader at Markem-Imaje

I liked "The Coding Dojo Handbook" a lot. It was not too long, very to the point and practical.

-- Anders Schau Knatten, Developer, Oslo

Feed items

SOLID principles and TDD

Emily Bache

Do you automatically get better design with TDD? Does an otherwise average software developer produce superior designs if they write the tests first rather than afterwards? Does it make a difference what style of TDD you use? Read more »

What is Text-Based Testing?

Emily Bache

Programmers have a vested interest in making sure the software they create does what they think it does. When I'm coding I prefer to work in the context of feedback from automated tests, that help me to keep track of what works and how far I've got. I've written before about Test Driven Development, (TDD). In this article I'd like to explain some of the main features of Text-Based Testing. Read more »

TDD in terms of states and moves

Emily Bache

The classic description of TDD that most people know is the 3 rules by Bob Martin. I think his rules are a very succinct description, and for a long time I've just relied on them, together with a picture of "red-green-refactor" to describe TDD to newcomers. More recently I've found value in expanding this description in terms of states and moves. Read more »

Should a professional developer always use TDD?

Emily Bache

I'm really looking forward to Scandinavian Developer Conference, and in particular the fishbowl discussion I'll be moderating on the Tuesday at 10:30am. Presenting their views will be Michael Feathers, Andrew Dalke, and Geoff Bache, and the topic under discussion is the same as the title of this post: Should a professional developer always use TDD? Read more »