I have a confession: I’m an early adopter. I like new shiny stuff. And if I like what I see, I’ll continue to use it. I was wondering a few days ago, what is the difference between what I’ll continue to use and what I’ll drop. The first tool that came to mind? Ask around
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
I’m very excited about this. I’ll be presenting at the Advanced Developers Conference 2011, Munich, Germany. Check out the schedule on the site. I’ll be giving two presentations: The first one about unit testing SharePoint applications, and the second one about techniques for multithreaded software. Also, I’m planning to attend a .NET Coding Dojo Group
In the last few weeks, we were hit by the flu. Many (including myself) have fallen before the mighty bug. Even after coming back from their sick bed, people have gone off for a second or even a third round. And lost. And the few that remained on their feet, need to carry on with
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
The first thought I had, reading about the Skype meltdown last week is: here’s another opportunity to score points for unit testing. Nothing like a a single bug causing so much havoc (or silence, in this case) to get developers attention to the catastrophes waiting to happen. But I decided to go deeper. There are
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