New post on Everyday Unit Testing. Started as a rant, and based on too many conversations I had. Does making members public a real danger? Check it out.
Category Archives: Software
It’s a great privilege to be a featured author on DZone’s 2015 edition of Code Quality and Software Agility. Along with other cool articles and infographics, you can find my “Refactoring in a Legacy Code Jungle” article there.
My old post “Why Microsoft makes bad programmers” made waves last week on Twitter. And so, I decided to write about how I see things five years later, now that I’m not fully in the MS world. Well, basically the same. Visual Studio (and other IDEs – it’s not a Microsoft specific problem) is getting better
To improve we need transparency. We cannot solve problems we don’t see. We can’t improve an invisible process. We need people to speak out about how they feel, how their work is affected. In order to improve, my team needs me to admit I’m late, and not hide I’m working for two weeks, digging a hole, and find out
New post on Everyday Unit Testing, about how we can measure if a test is valuable. Check it out.
I usually make fun of the “become a scrum master in 3 days”. I mean, what can you learn in 3 days? Glad you asked. Once a year or so, I get a chance of going through an exercise with my army unit. These few days are plentiful of agile post material. I’ll try to cram
In one month, I’m returning to Belgium Testing Days. It’s going to be a full week of work and learning. If last time is an indication, it’s going to be awesome, organized impeccably and a good place to learn about software development and testing. That’s for everyone, of course. Now, if you want to stick
When we bought our house, we designated one of the rooms as “ the computer room”. It was kind of small office, with a couple of book shelves. Then, with the children, we’ve added more cupboards and shelves and computers. It was no longer the computer room, it was a storage room. “Where is X?”
David H. Hansson (@DHH) sparked the “TDD being dead” latest twitter storm. DHH is no stranger to controversy, and he certainly picked the right title for it. Of course, the responses followed immediately. and most of them fell directly into his trap. Most people were defending TDD. How? By saying that Ruby on Rails (originally
You think that Arnold and Sylvester movie careers were head to head? Let me tell you the story of what happened before that. <Dissolve Effect> Arnold and Sylvester had a struggling software development business. Arnold wanted better code design. Because he was after better design, he chose TDD, with all the design goodness it brings.