A developer’s life is not simple. Developers need to contend with adding new software features, quickly, from different customers, while keeping up with technology. And do some support work in the middle. And, also meetings. However, the road to improvement through this complex situation can be a strange one. It sometimes starts with these suggestions, heard around
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
I’ve recently posted on the Typemock blog on test organization, and gave an example of how organizing Outlook folders is not as effective as dumping everything in one bin and using “Search”. Here’s a quote (from myself, by myself): The search box finds things much quicker. There’s also a penalty in the filing system. For
A couple of posts I read lately made me think. Again. The first one is Elisabeth Hendrickson’s on whether testers should write code. Elisabeth focuses on the perception of the tester in agile team. From Elisabeth’s research it shows that testers in teams (not only agile) are expected to be able to code. The research