Dan Q
This self-post was originally posted to /r/shittyaskscience. See more things from Dan's Reddit account.
Mercury’s year is only 88 days, so if we launch a rocket from there, we only have to travel for just over 1 light year, saving time and fuel.
This article is a repost promoting content originally published elsewhere. See more things Dan's reposted.
Imagine one house, with four people, but five couples. How does it work, asks Jo Fidgen.
Charlie is talking excitedly about a first date she went on the night before.
Next to her on the sofa is her husband of six years, Tom. And on the other side of him is Sarah, who’s been in a relationship with Tom for the last five years. Sarah’s fiance, Chris, is in the kitchen making a cup of tea.
…
Today, my cycle helmet might have saved my life.
This morning, I was cycling to work along my usual route, National Cycle Network Route 51, on its final leg down Banbury Road to Parks Road. Here, the cycle route shares its path with a bus lane, and – on a warm, bright morning like this one, having a broad, flat lane is a great opportunity for a strong cyclist to make great time in a safe environment.
As I approached the bus stop, a spotted a car in the lane to my right, just ahead, slow down and turn on it’s indicator to turn left: it was heading for one of the driveways. But when the car began its maneuver, a split second later, I realised that the driver had not seen me. Perhaps she’d not checked her mirrors before turning? Or perhaps she’d only glanced (and seen no buses in the bus lane – just me and the second cyclist behind me)? Or perhaps she’d underestimated my speed, or dramatically overestimated her ability to get into the driveway before I reached her? In any case, she turned out to be wrong. I hit my brakes as sharply as I safely could, but it wasn’t enough to stop me from ploughing right into the side of her bonnet.
I’m not entirely sure what happened next. At the time, it felt like everything went into slow motion: a gentle flight through the air followed by a gradual landing on the other side, and that I’d be able to recall every single moment. But, probably as a result of the blow to my head (which as I’ve discovered before can have profound and confusing effects on memory), my memory of everything from a few seconds before the collision onwards is fuzzy and fragmented. But I spoke to the driver (a woman with dark hair), to the cyclist behind me (who was wearing a white t-shirt), and to a man who came out of a nearby building (who spoke with an accent – these details are the only things I can reliably remember about any of them), and based upon their descriptions – any my injuries – I’ve managed to piece together broadly what happened.
I hit the side of the car and flipped forward, throwing myself, some of the contents of my pannier bag, and my D-lock into the air. My handlebars knocked a dent into the bonnet of the car, and the lock landed elsewhere on it, but I flew clear over the car and flipped around in the air. I’m not sure how I landed, but it was probably on my back, because I struck the backs of my head, right shoulder, and elbow… but I must have rolled, because I also managed to scrape and graze the front of my legs.
I initially thought that I was fine (though I was clearly in shock), but I discovered about a quarter of an hour (or thereabouts: I’ve only been able to piece together a timeline in hindsight) that I was in more pain than I’d first thought, was feeling intermittently dizzy, and was unable to remember the details of the accident or even what day of the week it was. I asked for a taxi to be called for me and rode to the hospital, where they cleared me of anything seriously wrong (spinal injuries, serious concussion, broken bones, etc.) and sent me home for a day of lying down and mainlining NSAIDs.
Now it’s the early evening. I’m still far from entirely “with it”: I feel like my brain’s been rebooted into safe mode – I seem to be incapable of decent multi-tasking (for example: I can have a conversation with you, or can listen for my name being called by the doctor, but not both). I’ve got aching shoulders and arms and a bit of a limp. And I’ve been pretty much exhausted the whole day.
But here’s something: if I’m right about the angle I landed at, based on where I hurt the most, then it’s possible that my cycle helmet saved my life, today.
Wear your cycle helmet, folks.
This review went a little bit meta, on account of the fact that I feature both as the reviewer and also as a subject of Godzilla’s sixth weekly Family Vlog itself. So ultimately, I end up reviewing an episode with me in. Clearly the bits with me in were the best.
The theme for Godzilla’s fifth Family Vlog was (clearly) “callbacks”, and my review – done while I was shaving – recognises this, and explains all of the references to previous episodes.
In Godzilla’s fourth Family Vlog, a lost cat is recovered from under the floorboards and the secret history of Godzilla and Zara is uncovered. Here’s my review, hastily and belatedly put together during my recent house move.
This blog post is the fifth in a series about buying our first house. In the third post in the series, we’d contracted some lawyers and applied for a mortgage, and in the fourth post we asked for help with the upcoming move. If you feel like we weren’t telling you the whole story, that’s because we weren’t: some of the bits we can now reveal were things that we needed to keep close to our chest while we were negotiating over the sale…
Things were continuing apace with our new house purchase, and that was the way that we wanted it. We’d had an offer accepted, applied for a mortgage (of which we’d been provisionally accepted already; this was just a paperwork affair), and our solicitors had gotten started with the searches and drafting the contracts. So long as the surveyor’s visit didn’t turn up any problems, we were on a roll.
Unfortunately, a few things did seem to be conspiring against us. The first was that the two sellers – a married couple who were in the middle of what appeared to be a… messy… separation – didn’t seem to be very communicative either with one another nor with their solicitor: or else, their solicitor was incredibly slow at relaying information back to our solicitor.
This posed a problem, because Ruth, JTA, Matt and I had already arranged with our letting agents that we’d be vacating our current house by the 5th of August. We’d left two clear weekends of possible “moving” time, but they were rushing up fast. Before the exchange of contracts, we couldn’t really let the sellers know how important it was that we complete the sale in a hurry, or else we’d be in a very weak negotiating position (and they’d be free to move the goalposts, knowing that we were running out of options). On the other hand, we really wanted to push to get the last couple of issues sorted out as soon as possible.
This ties in to the second thing that conspired against us: there were two particular issues with the house that we didn’t want to go ahead without resolving. The first was that the boiler hadn’t been serviced in a long time, so we insisted upon a gas safety inspection being carried out before we would exchange contracts. The second was that the front door was more “hole” than “door”, believed to have occurred during some kind of fracas between the owners (did I mention that their divorce was a little unpleasant?).
The gas safety inspection got sorted out after a while, but we went back and forth over the front door for what felt like an age. Who should repair it? Who should pay? We were told that the sellers were having cashflow problems and weren’t sure that they could pay for the repair of the door prior to the sale, but we weren’t happy to agree to the sale without a commitment that the door would be repaired by the completion (our insurer, answerable to our mortgage lender, wasn’t keen on us moving in to a house will a hole in it): we were at an impasse. So when the sellers produced for us a list of furniture they’d like to offer to sell to us, we noted with some suspicion that the total value of the furniture was remarkably close to the value of the quote for the repair of the door: clearly, they planned to offer to give us the furniture for “free” in exchange for not repairing the door.
Which might have been fine, except for the fact that we didn’t want about half (by value) of the things they were offering. Having been living in unfurnished accomodation for several years, we’ve already got a sufficiency of wardrobes. We were keen to take their appliances off their hands (including a gas cooker and a very large fridge/freezer), but we weren’t willing to buy something that we didn’t need just so that they could find it easier to repair something that they broke! We made a number of other offers, such as lending them the money to repair the door (which they’d be able to pay us back following the sale), but they weren’t keen.
We put into place our emergency plan, and made arrangements to go and start viewing rental properties, in case we ran out of time and needed somewhere to live. JTA and I played “good cop, bad cop” with them in a spectacular tag team, leveraging this situation as a threat to pull out of the purchase entirely… and just like that, they caved. Within a day or so, their solicitor had agreed to the terms of our contract, and the sellers agreed to sort out the front door prior to completion of the sale, and we made sure to get it in writing. Our solicitor had already requested the money from our mortgage lender, so we agreed upon a completion date later in the week.
We popped open a bottle of prosecco and celebrated the successful exchange, and redoubled our efforts to fill our house with boxes, prior to the move.
This checkin to GLBJHQQG Ladybarn Canal reflects a geocaching.com log entry. See more of Dan's cache logs.
Harder than I might have expected to navigate my way around the winding paths and alleyways surrounding this courtyard – I found myself within 10 metres of the cache at one point, but on the wrong side of a fence and hedge, and had to walk all the way around the block before I found my way in!
Cache is overlooked by lots of houses, so a great deal of care was required so as not to attract the attention of muggles. Thankfully I’d come early on a Sunday morning, before most folks were up (I’d woken earlier than my colleagues at the conference centre where I’d spent the weekend, and thought I’d hit a local cache before breakfast).
Found it in the end, though: hurrah! Pencil’s looking a little blunt, and I didn’t have a sharpener, but managed to sign the log despite this. TFTC!
This blog post is the third in a series about buying our first house. In the third post, Ruth, JTA and I had acquired some lawyers and started the conveyancing process…
We’re moving house! And we want your help!
There’ve been… a few hitches with the house move. A few little hurdles. And then a few big hurdles. It’s been a little challenging, is what I’m trying to say. I’ll write about that in Part 5, but for now: we need your help!
(cynical folks might notice that pizza, booze, rental vans and friends are a lot cheaper than professional removals companies, especially for short hops across to the other side of a city)
Can you help? Can you be free for some or all of the weekend of 27th & 28th of July, to come and shift boxes in exchange for good times, booze and snacks? If you are, we’d love to have you over. Ruth has written more about the wonderful perks that you’ll enjoy if you can help us, so – if you’re free and can get to Oxford – please come! And it’ll be lovely to see you, too!
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.
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?
This checkin to GLBERMGT Summit or Submit reflects a geocaching.com log entry. See more of Dan's cache logs.
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!).
This self-post was originally posted to /r/CosmoSexTips. See more things from Dan's Reddit account.
Just take his scrotum in your mouth and pretend it’s gum.