Category Archives: Uncategorized

Matt Ryall responded to my post on documentation with some suggestions for making it easier. I finally persuaded my brain to give up some of the thoughts that it didn’t like (because they’d result in doing documentation). This isn’t particularly … Continue reading →

Here’s a quick test for the fence from my last post. My customer wants a fence which allows sheep to graze in a field, and prevents sheep from wandering outside of the field. public class FenceTest extends TestCase { public … Continue reading →

Jim and his colleagues (hope you don’t mind me using you as an example) write documentation as the reference point to code. Then, one group of people write the tests, and one group of people implement the functionality, both working … Continue reading →

My friend Jim says, “Have to say, if I were a customer I would stipulate that you left me documentation. I wouldn’t buy services from a company that didn’t ;-)” One of the responsibilities of an Agile Coach (or perhaps … Continue reading →

A request was sent round work for anyone interested in an Agile Coaching stint. “Probably requires a convincing pragmatist,” it said. I’m trying to become an Agile Coach. I found the email confusing at first, because I’ve always thought I’ll … Continue reading →

The worst thing about having a dream is when people say, “I’m not interested in dreams. Please dream somewhere else.” The best thing about having a dream is when people say, “You and I have exactly the same dream. Can … Continue reading →

Following pointers from my last post, I have scoured the net for clear definitions of JavaSpaces, tuplespaces and Grid Computing (ie: I typed the phrases into Google). I have a better understanding of the subject as a result. I still … Continue reading →

Today we had a lunchtime talk about JavaSpaces, which is a form of grid computing (this is a new thing for me, so if I get anything wrong, yell). Grid computing is when a lot of computers are used to … Continue reading →

Use IntelliJ to refactor a class so it’s easier to test. Add a suitable mock object jar to the library. Add unit tests for the class which we’re about to change. Make sure all functionality is covered. Write new test … Continue reading →

At some point I’m guessing that the SheepImpl I’m looking at was an implementation of a Sheep interface, which extended the Animal interface. There’s also an AnimalImpl class. The Impl classes are generated by persistence layer stuff, so there’s some … Continue reading →