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.
Category Archives: Development
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!
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
The ISO 29119 is making waves in the testing communities, regarding its content and necessity. Its focus on test planning and documentation gets modern testers to ask why. I’ve worked in an ISO certified company, so maybe I can shed light from my past experience. ISO standards are written by committees, which are made of
Jason Gorman describes (in a very nice manner) how software courses are lowering the bar. It’s up to us to keep the bar higher. I agree completely. Yet what happens with scrum certification in the last years, has started long before. We’d like to think of software as a craft and development as a skill.
I was reading Lior Friedman’s post about the agile research. He raises an interesting question: Why are agile studies coming from the exact science fields? After all, we don’t see groups of accountants doing a stand-up meeting every morning. The easy answer of course, that’s where they practiced mostly. We tend to look under the
Thanks to Dilbert, developers, engineers and the rest of us managed people, have come to disrespect the “manager”. Ok, it’s not just the comic, some of it was perpetuated by actual managers. Still, there are cases where the managers do the right thing, and the developer messes up. Whenever this occurs, regardless if from the
I’ve gone back to watch Uncle Bob Martin’s presentation “Agile overview” from NDC 2010 (while you’re at it check his “The land that scrum forgot”, the man is such a storyteller!). In the presentation, Bob tells about Winston Royce’s study “Managing the development of large software systems”, from 1970. This article is the origin of
InfoQ had a round-up of ideas about “How Long Would it Take to Build the Product?”. It was funny (ha-ha funny) to read some of the responses. One person suggested that upfront estimations end up in a fixed scope, which is anti-agile. If I was new to agile, I would read it this way: if