testing...

I used to always feel ashamed that I'd missed something when the testers came back with issues. I have now changed my mind.

Testers are experts in their area and I'm an expert in mine (I hope!). It's their role to check everything to ensure quality. Besides I should spent less (yes, less*) time testing and more time coding. I should not try to write code that will pass all possible tests (functionality, uat, random, etc) in the first instance. Almost all apps will fail testing to some degree in the first run. Why not accept this and move onto a smaller and more frequent develop/test cycle?

So now, I'm happy that the testers find things. It means that they're doing their job and I'm doing mine.

* Less time, but more effectively.

am I geek enough?

It's strange. I'm kind of in between being a full geek and not quite. I really like what I do and technology and stuff, but most nights I still like to sit in front of the telly and do absolutely nothing.

The guys I know who I would classify as Fully Geek (and that's a compliment) seem to spend every available moment researching something technically cool whether related to their employment or not.

I guess I haven't got what it takes to be Fully Geek. Maybe I could be just Mostly Geek...

hello

hi.

i've been thinking about starting a blog for a while now. in fact, some friends/colleagues think that i'm opinionated enough to have a talkback radio show. they're probably right.

i will probably not be a daily poster, but lets see...

i always like to ask people what they do for fun as an icebreaker, so i guess i'll start:
- i like to mountain bike
- i like to ride a unicycle (not well though)
- i like to juggle (again, not well)
- and for something completely different, i like to write code (c#.net) and think about things.

and you?