From Legacy Code to Testable Code: Introduce Parameter
The series continues with the introduction of our little friend, the parameter. Check it out.
The series continues with the introduction of our little friend, the parameter. Check it out.
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.
A few weeks ago, I had a chance to be interviewed by Vasco Duarte for the Scrum Master Toolbox podcast. It was a great privilege, also because Vasco is a prominent figure in the #NoEstimates community, which I like too. Anyway, the series contains 5 parts, each one around 5 minutes. There is also bonus
New post on Everyday Unit Testing: Emergent design through TDD is not promised to be better than up front design. Check it out.
I didn’t think that my Story Points story would garner such attention. Reactions were divided to two groups: the “Great Post” type, short and supportive. And the “You’re doing it wrong” type, long and argumentative. I can’t fault people for telling me “You’re doing it wrong” after I used it in that post. It did make me
I’ve got the final part of the Creating Unit Testing Strategy series on Everyday Unit Testing. This time we look at test review and knowledge sharing. It’s only got one squirrel. Check it out!
I don’t like story points. I think this is part of my crusade against complexity. You can catch a glimpse of it here. Story points were invented as supporting beams for the bridge between business and development that would later be called agile. They started with a very good concept that wasn’t there before: The story.
I’m continuing the series about creating a unit testing strategy on Everyday Unit Testing. This time it’s about code preparations and actually writing the tests. Check it out!
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
I’m continuing the series about creating a unit testing strategy on Everyday Unit Testing. This time it’s about design constraints. Check it out!