It’s been about 7-8 months since we started to serious pilot Fitnesse on a project. Looks like its turning the corner. Instead of developers driving it, the QA staff are starting to build out acceptance tests and add scenarios. It’s coming in very handy for testing a huge number of edits based on a positional [...]
Chapter 3 Ruby Eye for the Java Guy Rails For Java Developers
One of those silent chuckle to yourself moments.
Apparently JB’s entry on Wikipedia is up for deletion. He comments on the whole process of the debate around his deletion as:
The whole experience makes me feel like I’m in a room with people talking about me while not acknowledging my presence and not seeming to care what I think about that.
In number the great bulk of projects I see are small maintenance or minor enhancement projects. They’re done in a day or a week or two by a single developer. Adding anyone or even the overhead of something like Scrum is counter-productive.
My assumption has been you hand off the assignment and let the individual [...]
Developers have no love of estimates. They’ve been pinned in a corner by an estimate and beaten to a pulp. “But you said it would be done by Friday!”
I don’t have any problem with a developer being reluctant to give an estimate. I do have a problem with developers refusing to give estimates unless [...]