Showing posts from April, 2012

This Blog Has Moved!

Right, so yes, five years ago I moved to github pages, and never bothered to redirect any of these pages there. Now I've moved on from there, and... Finally I am using my real domain, . My blog is now at .  See you there!

In which I defend the Male species at an all Female event

Google Campus is an awesome space Today I was at the Girl Geek Meetup conference.  I didn't advertise it much because I've said in the past I don't really agree with women-only events , and actually I felt quite uncomfortable telling you guys I was going to be there, knowing the majority of my readers weren't allowed to attend. It's probably worth explaining why I went, so a) I can give you guys and excuse but b) conference organisers can see what people like me are looking for in a conference. Graduate Developer Community Meet a Mentor Programme The primary reason I went is because the new Meet a Mentor programme I'm involved in does not have a lot of women mentors.  This is simply a numbers game - when you don't have all that many people signed up to be mentors yet, and you have the "normal" proportion of women in that group, you'll be lucky if you get one female mentor turning up at these events.  Since one of the things we want

Overheard: Agile truths

After attending a number of conferences and events, and performing numerous interviews, I'm starting to hear the same things again and again.  Since Dan North challenged all my assumptions at QCon , I'm reluctant to outright ridicule them, but I will put forward my personal opinion. Note: these are things I have heard from multiple sources, so with any luck I am not breaking the sanctity of the confessional interview. I've never pair programmed, but I've frequently worked with a partner on critical production problems I find this fascinating.  If there's one thing that needs to be fixed as fast, as correctly, as efficiently as possible, it's a production issue.  And when there is one, "everyone" knows that two heads are better than one, even The Business. If this is the case, why is it so hard to sell pair programming as the default state of affairs? Is it because creating new features is seen as just typing, where the bottleneck is access t

Popular posts from this blog

Dissecting the Disruptor: What's so special about a ring buffer?

Dissecting the Disruptor: Writing to the ring buffer

Dissecting the Disruptor: Demystifying Memory Barriers