Getting started

I recently restored my Asus Eee Pc so I had to start over from the beginning. I had a lot of help from the Eee Wiki.

First step, activating the Full Desktop mode: http://wiki.eeeuser.com/howto:getkde

Then, I had to get apt-get going to be able to install new programs easily. That included adding the Xandros Repositories to the apt-get source list, pinning and then adding the Debian Repositories.

After that, a simple apt-get install eclipse/junit/subversion and I was all set.

Google nerd

Today I’m a google nerd. I spent a lot of time adding Google Labs components to Gmail.

First up, the tasks application. It’s simply a quick way to make a to-do list with checkboxes, the ability to move tasks up and down the list, view/hide finished tasks. The surprise was the ability to pop-out the list into a separate window. Easy and clean!

Second, the Google Docs app. It’s a list of your most recently used Google Documents in an easy accessible box on the left hand margin in Gmail. No need to take the extra step of going to the actual Google Docs page.

Last, I enabled Gears with WordPress so I can use it if I happen to be offline.

“There is no rule for what a ‘unit’ is”

When learning about Unit Testing, it was repeatedly pointed out that there is no way of objectively deciding what makes up a unit. As I thought about, it hit me: does it really matter?

Sure there is no golden rule but isn’t a unit test a unit test because of its purpose, that is to test code in its isolation? As soon as you stretch beyond and try to test components together it’s integration testing, further than that, system testing. Can it be that the purpose defines the test or is that simply a naive way to look at it?

Perhaps it is more challenging than I expect to choose the boundaries for a unit. Time will tell.