How can something seem so right, and yet so wrong, at the same time? Easy. When the person who speaks is different than the one listening, which is usually the case, and there’s a translation problem. Consider the term “Refactor mercilessly”. I don’t recall when I first heard it, but it definitely caught my ear
I’m a fan of “House”. I’m currently catching up on the 7th season, where the theme is about truth and lies. For those leaving in a cave with no cable TV, “House” is about a brilliant, misanthropic doctor who runs a diagnostic team in a hospital. In each episode the team dives into a mystery
This is the presentation I gave today at the “QA and Development in Agile” conference (It’s a bit more detailed than what the people in the room saw). This wasn’t a technical presentation, just an overview to the newly initiated to unit testing – third of the room wrote unit tests, the rest didn’t. And
One of the sessions at ADC2011 that I understood (even though it was in German), was Bjorn Rochel’s talk on test organization. Bjorn told a story of the evolution of his experience writing tests, and how to organize them. For example, he started out with a test class, called CalculatorTests, and every method name ended
ADC 2011 incidentally happened on a day when a meeting was scheduled for the Munich coding dojo meeting. Luckily, we were invited to the meeting by Ilker Cetinkaya. The first thing you’ll notice in the picture, is that I may seem shorter than the other people there. I’m still suspecting Adi used a fish-eye camera.
ADC2011 is over, and I had a mighty fun time. Like I open my talks, I’d like to speak first on my favorite subject: me. I had two talks, one on unit testing SharePoint applications, and the other about tools for identifying issues in multithreaded apps (slides below). I can tell you that all those
Something strange is going through TDD land these last couple of weeks. First it was Uncle Bob,with a new TDD theory – making tests pass in a certain order, actually helps incremental design, leading to a better solution. This is a very interesting post, and if he’s right, he might have discovered the cornerstone of
I was asked this question last Wednesday, when I led a TDD open session at the Israeli Software Craftsmanship User Group. My answer: It makes you think before you write code. In fact, next time somebody asks you what TDD stands for, you answer: Thinking-Driven Development. Sure, all the benefits are there: structured incremental progress,
It will be for me.This Wednesday, December 15th, I’m going to be a bit busy. 3pm Israel time, that’s 2pm CET, and 8am EST I’m giving a webinar about steps you can take right now toward agile. I really like to learn real world actionable stuff, and this webinar is where I’m giving back. Do
I had a discussion today about the name “unit testing”, and its connotations. I’d like to remind you, dear reader, that the audience of this blog is already aware of the goodness that comes with unit testing. Unit testing is part of our day-to-day work, and also for people just starting to get interested in