Who’d have thought that my onboarding fortnight at @WooCommerce / @Automattic would conclude with a very literal “on-boarding”. Hang five! 🏄🏼♂️
Well, Cape Town, you were a blast. But now it’s time to get back to my normal life for a bit.
Off to Cape Town. Don’t wait up! ✈️ 🇿🇦
This adventure took a lot of planning. It’s 350 miles from where I live to Glasgow. I have a Honda CG 125cc, and my maximum range in one day is around 200 miles – if I have the full day for travelling, which I wouldn’t have, most days. I figured if I was going to have a road trip, I’d have to make stop offs at various parts of the UK, to break it up. This actually worked out really well, as there are lots of parts of the UK that I wanted to visit.
After booking the series of hotel rooms, I started to think about the actual riding. It was two weeks before the trip. I didn’t have enough thermals, or a bike suit that was protective enough. I also didn’t have a way of storing luggage on my bike, or keeping it dry (and two laptops would be in the bags). There was also an issue with the chain on my bike that needed fixing. Not exactly a trivial to do list! So the next two weeks turned into a bit of an eBay and Amazon frenzy, with a trip down to see my dad in Kent to get the bike chain fixed, and rummage around for my old waterproofs in my grandparent’s attic. It was pretty close: the final item arrived the day before the trip. I got ridiculously lucky on eBay with my new, more visible, better padded, comfy bike suit though, which I love to bits. In hindsight, more time for all of this would have been helpful!
My friend Bev wrote about their motorcycling adventure up and down the UK; it’s pretty awesome.
I so very much want to have a go on this.
On the way out to the French Alps for a week of skiing, and we had enough air miles to upgrade to business class on the way out, so I’m sat in the lounge enjoying complimentary gin & tonic and croissants. 10 in the morning, and I’m already buzzed: after a long and hectic few months, I’m really glad to be off on holiday!
Aaaand…. right before I left I put in an application for my boss’s job, which she vacated a few months ago. Should hear by the time I get back whether I’m being invited to interview, so that’s exciting too!
Anyway: just wanted to share my excitement with my favourite MegaMasons. If I’m not online much this week, you’ll know why! Have a great week, folks: love you all!
I’ve had a tardy summer for blogging, falling way behind on many of the things I’d planned to write about. Perhaps the problem is that I’m still on Narrowboat Time, the timezone of a strange parallel universe in which everything happens more-slowly, in a gin-soaked, gently-rocking, slowly-crawling haze.
That’s believable, because this summer Ruth, JTA and I – joined for some of the journey by Matt – rented a narrowboat and spent a week drifting unhurriedly down the Monmouthshire and Brecon Canal… and then another week making a leisurely cruise back up it again.
We picked up Nerys, out of Cambrian Cruisers, who also gave us an introduction to the operation of the boat (driving it, filling it with water, pumping out sewage, generating electricity for appliances, etc.) and safety instructions (virtually all of the canal is less than four feet deep, so if you fall in, the best thing to do is to simply walk to the shore), and set out towards Brecon. In order to explore the entire canal in the time available, we needed to cover an average of only five miles per day. When you’re going at about two and a half miles per hour and having to stop to operate locks (there are only six locks on the navigable stretch of the canal, but they’re all clustered towards the upper end), though, five miles is plenty.
The upper end of the canal is by far the busiest, with not only narrowboats cruising up and down but a significant number of day boats (mostly on loan from Brecon) and at least one tour boat: a 50-seater that you don’t want to have to wiggle past at sharp corner North of the Bryich Aqueduct. From a navigation perspective, though, it’s also the best-maintained: wide enough that two boats can pass one another without much thought, and deep enough across its entire width that you needn’t be concerned about running aground, it makes for a great starting point for people who want some narrowboating practice before they hit the more challenging bits to the South.
Ruth was excited to find in me a driver who was confident holding the boat steady in a lock. Perhaps an expression of equal parts talent and arrogance, I was more than happy to take over the driving, leaving others to jump out and juggle the lock gates and lift bridges. Owing to Ruth’s delicate condition, we’d forbidden her from operating the entirely-manual locks, but she made sure to get a go at running one of the fancy hydraulic ones.
After each day’s cruising, we’d find a nice place to moor up, open a bottle of wine or mix up some gin-and-tonics, and lounge in the warm, late summer air.
As we wound our way further South, to the “other” end of the waterway, we discovered that the already-narrow canal was ill-dredged, and drifting anywhere close to the sides – especially on corners – was a recipe for running around. Crewmates who weren’t driving would take turns on “pole duty”, being on standby to push us off if we got too close to one or the other bank.
Each night moored up in a separate place gives a deceptive feeling of travel. Deceptive, because I’ve had hiking trips where I’ve traveled further each day than we did on our boat! But the nature of the canal, winding its way from the urban centre of Brecon out through the old mining villages of South Wales.
The canal, already quite narrow and shallow, only became harder to navigate as we got further South. Our weed hatch (that’s the door to the propeller box, that is, not a slang term for the secret compartment where you keep your drugs) saw plenty of use, and we found ourselves disentangling all manner of curious flora in order to keep our engine pushing us forwards (and not catching fire).
Eventually, we had to give up navigating the waterway, tie up, and finish the journey on foot. We could have gotten the boat all the way to the end, but it’d have been a stop-start day of pushing ourselves off the shallow banks and cleaning out the weed hatch. Walking the last few miles – with a stop either way at a wonderful little pub called The Open Hearth – let us get all the way to both ends of the navigable stretch of the canal, with a lot less hassle and grime.
It’s a little sad coming to the end of a waterway, cut short – in this case – by a road. There’s no easy way – short of the removal of an important road, or the challenging and expensive installation of a drop lock, that this waterway will ever be connected at this point again. The surrounding landscape doesn’t even make it look likely that it’ll be connected again by a different route, either: this canal is broken here.
I found myself remarking on quite how well-laid-out the inside of the narrowboat was. Naturally, on a vehicle/home that’s so long and thin, a great number of clever decisions had clearly been made. The main living space could be converted between a living room, dining room, and bedroom by re-arranging planks and poles; the kitchen made use of carefully-engineered cupboards to hold the crockery in place in case of a… bump; and little space-saving features added up all along the boat, such as the central bedroom’s wardrobe door being adaptable to function as a privacy door between the two main bedrooms.
On the way back up the canal, we watched the new boaters setting out in their narrowboats for the first time. We felt like pros, by now, gliding around the corners with ease and passing other vessels with narry a hint of a bump. We were a well-oiled machine, handling every lock with ease. Well: some ease. Unfortunately, we’d managed to lose not one but both of our windlasses on the way down the canal and had to buy a replacement pair on the way back up, which somewhat dented our “what pros we are” feeling.
Coming to the end of our narrowboating journey, we took a quick trip to Fourteen Locks, a beautiful and series of locks with a sophisticated basin network, disconnected from the remains of the South Wales canal network. They’ve got a particular lock (lock 11), there, whose unusual shape hints at a function that’s no-longer understood, which I think it quite fabulously wonderful – that we could as a nation built a machine just 200 years ago, used it for a hundred years, and now have no idea how it worked.
Our next stop was Ikea, where we’d only meant to buy a couple of shelves for our new home, but you know how it is when you go to Ikea.
We wrapped up our holiday with a visit to Sian and Andy (and their little one), and Andy showed off his talent of singing songs that send babies to sleep. I swear, if he makes an album of children’s songs and they’re as effective as he is in person, we’ll buy a copy.
Altogether, a wonderfully laid-back holiday that clearly knocked my sense of urgency so far off that I didn’t blog about it for several months.
Edit, 22 June 2018: after somebody from the Canal & River Trust noticed that my link to their page on the Brynich Aqueduct was broken after they’d rearranged their site, I removed it. They suggested an alternative page, but it didn’t really have the same content (about the aqueduct itself) so I’ve just removed the link. Boo, Canal & River Trust! Cool URIs Don’t Change!
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.
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.
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!
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.
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.
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).
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.
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.
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’ll it do in the next ten?