At the end of 2012, I shared some sad news: that Ruth and JTA had suffered a miscarriage. It was a tragic end
to a tragic year.
I just wanted to share with you something that we’ve all kept quiet about until now, until we all felt confident that we weren’t likely to have a repeat of that tragedy: as Ruth just mentioned on her blog, too, she’s pregnant again! With a due date of New Year’s
Eve there’s plenty of time for us to get settled into our new house before
then, but it looks like she’s still going to find herself excused of all of the heavy lifting during the move.
Needless to say, this is all incredibly exciting news on New Earth, and we’ve had to bite our tongues sometimes to not tell people about it. Apologies to those of you who’ve invited us
to things (e.g. at Christmas and New Years’) that we’ve had to quietly turn down without explanation – at least now you know!
I’m sure there’ll be lots to say over the coming months. I can’t promise as thorough updates as Siân‘s fantastic
pregnancy blogging, but we’ll see what we can do.
This is my video review of the second episode of Godzilla Huntley’s (Captain AvAngel) blog series, Family Vlog. See the
original.
With such a long video to review, I had to budget my time to watch and review it. This means that you’ll see me at home, at work, travelling by foot, and travelling by car, as I hop
around and try to find snippets of time to watch it (and to record myself talking about it).
Hot on the heels of our long weekend in Jersey, and right after the live deployment of Three
Rings‘ Milestone: Krypton, came
another trip away: I’ve spent very little time in Oxford, lately! This time around, though, it was an experimental new activity that we’ve inserted into the Three Rings
calendar: Dev Training.
We rented a secluded cottage to which we could whisk away our prospective new developers. By removing day-to-day distractions at work and home, our thinking was that we could fully
immerse them in coding.
The format wasn’t unfamiliar: something that we’ve done before, to great success, is to take our dedicated volunteer programmers away on a “Code Week”: getting everybody together in one
place, on one network, and working 10-14 hour days, hammering out code to help streamline charity rota management. Sort-of like a LAN party, except instead of games, we do
work. The principle of Code Week is to turn volunteer developers, for a short and intense burst, in to machines that turn sugar into software. If you get enough talented people
around enough computers, with enough snacks, you can make miracles happen.
I’m not certain that the driveway was really equipped for the number of cars we brought. But I don’t get on terribly well with laptops, so clearly I was going to bring a desktop
computer. And a second desktop computer, just in case. And that takes up a lot of seat space.
In recent years, Three Rings has expanded significantly. The test team has exploded; the support team now has to have a rota of their own in order to keep track of who’s
working when; and – at long last – the development team was growing, too. New developers, we decided, needed an intensive session of hands-on training before they’d be set loose on
real, production code… so we took the principles of Code Week, and turned it into a boot camp for our new volunteers!
New developers Rich, Chris, and Mike set up their development environments. Owing to the complexity of the system, this can be a long part of the course (or, at least, it feels that
way!).
Recruiting new developers has always been hard for us, for a couple of reasons. The first reason is that we’ve always exclusively recruited from people who use the system. The thinking
is that if you’re already a volunteer at, say, a helpline or a community library or a fireboat-turned-floating-museum or any of the other organisations that use Three Rings, then you already understand why what we
do is important and valuable, and why volunteer work is the key to making it all happen. That’s the bit of volunteering that’s hardest to ‘teach’, so the thinking is that by making it a
prerequisite, we’re always moving in the right direction – putting volunteering first in our minds. But unfortunately, the pool of people who can program computers to a satisfactory
standard is already pretty slim (and the crossover between geeks and volunteers is, perhaps, not so large as you might like)… this makes recruitment for the development
team pretty hard.
Turfed out of the Ops Centre and into the living room, JTA works on important tasks like publicity, future posts on the Three Rings blog, and ensuring that we all remember to eat at
some point.
A second difficulty is that Three Rings is a hard project to get involved with, as a newbie. Changing decisions in development convention, a mess of inter-related (though
thankfully not inter-depedent) components, and a sprawling codebase make getting started as a developer more than a little intimidating. Couple that with all of the things our
developers need to know and understand before they get started (MVC, RoR, TDD, HTML, CSS, SQL, DiD… and that’s just the acronyms!), and you’ve got a learning curve that’s close to vertical. Our efforts to integrate
new developers without a formal training program had met with limited success, because almost nobody already has the exact set of skills we’re looking for: that’s how we knew it was
time to make Dev Training Weekend a reality.
Conveniently, there was a pub literally just out the gate from the back garden of the cottage, which proved incredibly useful when we (finally) downed tools and went out for a drink.
We’d recruited three new potential developers: Mike, Rich, and Chris. As fits our pattern, all are current or former volunteers from organisations that use Three Rings. One of them had
been part of our hard-working support team for a long time, and the other two were more-new to Three Rings in general. Ruth and I ran a series of workshops covering Ruby, Rails, Test-Driven Development, Security, and so on, alternated between stretches of supervised
“hands-on” programming, tackling genuine Three Rings bugs and feature requests. We felt that it was important that the new developers got the experience of making a real difference,
right from the second or the third day, they’d all made commits against the trunk (under the careful review of a senior developer, of course).
Mike demonstrates test-driven development, down at the local pub: 1. touch cat 2. assert cat.purring? When the test fails, of course, the debugging challenge begins: is the problem
with the test, the touch, or the cat?
We were quite pleased to discover that all three of them took a particular interest early on in different parts of the system. Of course, we made sure that each got a full and
well-rounded education, but we found that they were all most-interested in different areas of the system (Comms, Stats, Rota, etc.), and different layers of development (database,
business logic, user interface, etc.). It’s nice to see people enthused about the system, and it’s infectious: talking with some of these new developers about what
they’d like to contribute has really helped to inspire me to take a fresh look at some of the bits that I’m responsible for, too.
Chris drip-feeds us fragments of his life in computing and in volunteering; and praises Ruby for being easier, at least, than programming using punchcards.
It was great to be able to do this in person. The Three Rings team – now about a dozen of us in the core team, with several dozen more among our testers – is increasingly geographically
disparate, and rather than face-to-face communication we spend a lot of our time talking to each other via instant messengers, email, and through the comments and commit-messages of our
ticketing and source control systems! But there’s nothing quite like being able to spend a (long, hard) day sat side-by-side with a fellow coder, cracking through some infernal bug or
another and talking about what you’re doing (and what you expect to achieve with it) as you go.
Chris, Mike and Rich discuss some aspect or another of Three Rings development.
I didn’t personally get as much code written as I’d have liked. But I was pleased to have been able to support three new developers, who’ll go on to collectively achieve more than I
ever will. It’s strange to look back at the early 2000s, when it was just me writing Three
Rings (and Kit testing/documenting most of it: or, at least, distracting me with facts about Hawaii while I was trying to write
the original Wiki feature!). Nowadays Three Rings is a bigger (and more-important) system than ever before, supporting tens of thousands of volunteers at hundreds of voluntary
organisations spanning five time zones.
I’ve said before how much
it blows my mind that what began in my bedroom over a decade ago has become so critical, and has done so much good for so many people. And it’s still true today: every time I think
about it, it sends my head spinning. If that’s what it’s done in the last ten years, what’llitdo in the next ten?
Went up the PYG track this weekend with the TransAid team, raising money in memory of my father (who was killed when he fell from a cliff last year, while in training for a sponsored
trip to the North Pole). Whlie the stragglers made their way up to the summit, I whipped out my GPSr and found this wonderful little cache (pretty sure it wasn’t here when I last came
up Snowdon, in early 2006).
A glorious day, marred only by the ludicrous number of walkers that had come out to make the most of it – the top was heaving with people!
Didn’t have a pen with me, and there wasn’t one in the cache. I’ve taken a photo of myself holding the cache (which I’ll provide on-demand, but in order not to spoil the cache for
others I’ve not included it: instead see attached a photo of my group at the summit – I’m the guy at the front with his arms out; I’ve just run up from where the cache is in order to
get into the picture at the last second!).
Things like this robot, painted onto the door of the bathrooms of a hipsterish East Oxford bar.
(it looks like one of the robot’s eyes fell off before the bar‘s owners Instragram’d it)
See the robot? THE ROBOT SEES YOU NOW!
There are those who would argue that this isn’t true eyebombing, because I ought to be sticking eyes to non-anthropomorphic, inanimate objects, and making them look alive by
doing so. But the folks on /r/eyebombing don’t seem to mind: they’re far more-focused on the
chaos and hilarity that ensues when you just put eyes on any damn thing that looks like it could benefit from them.
This guy’s so angry he’s popping his eyes out of his head!
When I was on holiday in Jersey, for example, I found an unattended rack of tourist information
leaflets that were just crying out for a ‘bombing.
“Does this dress make my eyes look fat?”
And because I pretty-much carry googly eyes around with me all the time – in the pocket that generally contains my headphones, a pen, a hair tie, and other everyday essentials – I
started sticking eyes onto things.
Soon.
The game didn’t stop even when I touched back down on the mainland.
Sign at the toilets in the arrivals lounge of Gatwick Airport.
Hacked through the (enormous) nettles to get close to the oak tree; also tried the obvious places (based on the hint) nearby, but no luck this afternoon. :-(
Last cache of the day for tajasel and I. Ironically, we’d brought our bikes with us but
had to leave them on the other side of Radley Wood, after we’d gotten bogged down in mud, and had to go back for them AFTER signing the log of the “on yer bike” cache. Of all the people
wearing cycle helmets to visit “on yer bike”, tajasel is probably the first such person
to not actually be on a bike!
Off for an afternoon’s caching with tajasel, we decided on a whim against our plan to
go down the Thames Path and instead found ourselves further West, in Radley Wood. We spotted this cache listing, and thought we’d give it a go… and we’re really glad we did! A fantastic
cache with a wonderful puzzle theme; the “decoder” is a wonderful idea; I really love it. Thanks for a great cache!
When Claire and I changed our surnames to the letter Q, six and a quarter years ago, I was pretty sure that we were the only “Q”s in the world. Ah Q‘s name is a transliteration into the Latin alphabet; Stacey Q is a stage name that she doesn’t use outside of her work (she uses Swain in
general); Suzi Q‘s “Q” is short for Quatro (perhaps popularised because of the
similarly-named song, which came out when she was aged 7; Maggie Q‘s “Q” is short for Quigley (she finds that her full name is almost impossible for her fans in East
Asia to pronounce); and both Q and Q are fictional. We were reasonably sure that we were the only two people in the world
with our surname, and that was fine by us.
Fictional, as much as we love them.
After Claire and I split up, in 2009, we both kept our new names. In my case, the
name felt like it was “mine”, and represented me better than my birth name anyway. Plus, I’d really gotten to enjoy having a full name that’s only four letters long: when my poly-tribe-mates Ruth and JTA (each of whom have almost 30 letters in their full names!) were filling out mortgage application forms recently, I was able to
get through the pages I had to fill significantly faster than either of them. There are perks to a short name.
Also fictional. But we’re less-upset about that.
I can’t say why Claire kept her new name, but I’m guessing that some of our reasons overlap. I’m also guessing that laziness played a part in her decision: it took her many months to
finally get around to telling everybody she’d changed her name the first time around! And while I’ve tried to make it possible to change your name easily when I launchedfreedeedpoll.org.uk, there’s still at least a little letter-writing involved.
Now, though, it looks like I may soon become the only Q in the world:
Personally, I thought that after she passed her PhD she’d
have even more reason to be called “Q”. I mean: “Dr. Q”: how cool is that? It sounds like a Bond villain or something. But on the other hand: if she wants to downgrade to
an everyday name like “Carter” then, well, I guess that’s up to her. I shan’t blame them for not opting to hyphenate, though: “Carter-Q” sounds like a brand of ear bud.
It’s not like there was ever anybody famous called “Carter”. Except for this guy, I suppose. But he was more of a “brave politician in the face of international crises” character than
a “Bond villain” character. Not fictional.
Seriously, though: good for them. If those crazy kids feel that marriage is for them, then I wish them the best of luck. And let’s face it, we’re approaching a bit of a lull in this run
of all-of-our-friends-getting-married, so it’ll be nice to have an excuse for yet another wedding and a fabulous party (I’m jumping to conclusions and assuming that they’re going to
invite me, especially after this blog post!).
Aww. It’s a sweet photo, but somebody should probably buy them a tripod as a wedding present: it’s hard to keep the horizon level in an arms-length selfie.
In other name-related news, look out for me in the Money section of tomorrow’s Guardian, where I’ll be talking about deeds
poll, as part of their series of articles on scammy websites. I always knew that it was only a matter of time before my photo appeared in a national newspaper: I guess I should just be
thankful that it’s for something I’ve done right, rather than for something I’ve done wrong!
This blog post is the third in a series about buying our first house. If you
haven’t already, you might like to read the first part. In
the second post in the series, we’d put an offer on a house which
had been accepted… but of course that’s still early days in the story of buying a house…
We hooked up with Truemans, a local solicitor, after discovering that getting
our conveyancing services from a local solicitor is only marginally more-expensive than going with one of the online/phone/post based national ones, and you get the advantage of being
able to drop in and harass them if things aren’t going as fast as you’d like. Truemans were helpful from day one, giving us a convenient checklist of all of the steps in the process of
buying a house. I’m sure we could have got all the same information online, but by the time I was thinking about offers and acceptance and moving and mortgages and repayments and
deposits and everything else, it was genuinely worth a little extra money just to have somebody say “next, this needs to happen,” in a reassuring voice.
This gargantuan beast is our mortgage application form. All of those pages are double-sided, by the way.
Meanwhile, we got on with filling out our mortgage application form. Our choice of lenders – which Stefan, who I’d mentioned in the last post, had filtered for us – was limited slightly
by the fact that we wanted a mortgage for three people, not for one or two; but it wasn’t limited by as much as you might have thought. In practice, it was only the more-exotic mortgage
types (e.g. Option ARMs, some varieties of interest-only mortgage) that we were restricted from, and these weren’t
particularly appealing to us anyway. One downside of there being three of us, though, was that while our chosen lender had computerised their application process, the computerised
version wasn’t able to handle more than two applicants, so we instead had to fill out a mammoth 22-page paper form in order to apply. At least it weeds out people who aren’t serious, I
suppose.
The front door of our intended new home had recently sustained some… damage. That didn’t bode well.
I revisited the house to check out a few things from the outside: in particular, I was interested in the front door, which had apparently been broken during a…
misunderstanding… by the current owners, who are in the middle of what seems like a complicated divorce. The estate agent had promised that it would be repaired before the
sale, but when I went to visit I found that this hadn’t happened yet. Of course, now we had lawyers on our side, so it was a quick job to ask them to send a letter to the seller’s
solicitor, setting the repair of the door as a condition upon which the sale was dependent.
The results of our Environmental Search were perhaps the most-interesting. But I’ll understand if you don’t think it’s as interesting as I do.
Our solicitors had also gotten started with the requisite local searches. One of the first things a conveyancing solicitor will do for you is do a little research to
ensure that the property really is owned by the people who are selling it, that there’s no compulsory purchase order so that a motorway can be built through the middle of it, that it’s
actually connected to mains water and sewers, that planning permission was correctly obtained for any work that’s been done on it, and that kind of thing. One of the first of these
searches to produce results was the environmental search.
A map of the area around our new house, as it was about a century ago, unearthed by our convenient tame librarian.
One of the things that was revealed be the environmental search was that the area was at a significantly higher-than-average risk of subsidence, had the construction not been done in a
particular way – using subsidence-proof bricks, or something, I guess? I theorised that this might be related to the infill activities that (the environmental search also reported) had
gone on over the last hundred and fifty years. The house is near a major waterway, in an area that was probably once lower-lying and wetter, but many of the small ponds in the area were
filled in in the early part of the 20th century (and then, of course, the area was developed as the suburbs of central Oxfordshire expanded, in the 1980s). Conveniently, we have
a librarian on our house-buying team, and he was able to pull up a stack of old OS maps showing the area, and we
were able to find our way around this now almost-unidentifiable landscape.
A map showing a field, hedgerows, water course and – highlighted in blue – a pond. The second highlighting in blue (bottom left) is a letter ‘O’, not a pond. I got carried away
highlighting things, okay?
Sure enough, there were ponds there, once, but that’s as far as our research took us. Better, we thought, to just pass on the environmental search report to a qualified buildings
surveyor, and have them tell us whether or not it was made out of subsidence-proof bricks or shifting-ready beams or whatever the hell it is that you do when you’re
building a house to make it not go wonky. Seriously, I haven’t a clue, but I know that there are experts who do.
In this highly-realistic diagram, which wouldn’t look out of place in a geography textbook, houses go wonky because they’re built on ground that became more-compressible after it was
drained. This is what I want to avoid.
Given that the house we’re looking at is relatively new, I don’t anticipate there being any problems (modern building regulations are a lot more stringent than their historical
counterparts), but when you’re signing away six-figures, you learn to pay attention to these kinds of things.
Hopefully, the fourth blog post in this series will be about exchanging contracts and getting ready to move in to our new home: fingers crossed!
