Heading back by train from a holiday in Derbyshire with @bornvulcan, @Crusty_Twobags, @fleeblewidget, @TheGodzillaGirl, @LadyJemma_, @Andrewsean85, and others. This trip must have been under some kind of curse: contagious gastric illnesses, dog-bite drama, perpetual rain, and a satnav that directed me to drive down a footpath!
For the benefit of those that suffered alongside me, I’ve started collating pictures and videos here.
Our eldest singing a classic song.
Our eldest, 4, started school this year and this week saw her first parents’ evening. This provided an opportunity for we, her parents, to “come out” to her teacher about our slightly-unconventional relationship structure. And everything was fine, which is nice.
I’m sure the first few months of every child’s school life are a time that’s interesting and full of change, but it’s been particularly fascinating to see the ways in which our young academic’s language has adapted to fit in with and be understood by her peers.
I first became aware of these changes, I think, when I overheard her describing me to one of her school friends as her “dad”: previously she’d always referred to me as her “Uncle Dan”. I asked her about it afterwards and she explained that I was like a dad, and that her friend didn’t have an “Uncle Dan” so she used words that her friend would know. I’m not sure whether I was prouder about the fact that she’d independently come to think of me as being like a bonus father figure, or the fact that she demonstrated such astute audience management.
I don’t object to being assigned this (on-again, off-again, since then) nickname. My moniker of Uncle Dan came about as a combination of an effort to limit ambiguity (“wait… which dad?”) and an attempt not to tread on the toes of actual-father JTA: the kids themselves are welcome to call me pretty-much whatever they’re comfortable with. Indeed, they’d be carrying on a family tradition if they chose-for-themselves what to call me: Ruth and her brothers Robin and Owen address their father not by a paternal noun but by his first name, Tom, and this kids have followed suit by adopting “Grand-Tom” as their identifier for him.
Knowing that we were unusual, though, we’d taken the time to do some groundwork before our eldest started school. For example we shared a book about and spent a while talking about how families differ from one another: we figure that an understanding that families come in all kinds of shapes and sizes is a useful concept in general from a perspective of diversity and and acceptance. In fact, you can hear how this teaching pays-off in the language she uses to describe other aspects of the differences she sees in her friends and their families, too.
Still, it was a little bit of a surprise to find myself referred to as a “dad” after four years of “Uncle Dan”.
Nonetheless: in light of the fact that she’d clearly been talking about her family at school and might have caused her teacher some confusion, when all three of us “parents” turned up to parents’ evening we opted to introduce ourselves and our relationship. Which was all fine (as you’d hope: as I mentioned the other day, our unusual relationship structure is pretty boring, really), and the only awkwardness was in having to find an additional chair than the teacher had been expecting to use with which to sit at the table.
There’s sometimes a shortage of happy “we did a thing, and it went basically the same as it would for a family with monogamous parents” poly-family stories online, so I thought this one was worth sharing.
And better yet: apparently she’s doing admirably at school. So we all celebrated with an after-school trip to one of our favourite local soft play centres.
This article is a repost promoting content originally published elsewhere. See more things Dan's reposted.
Sometimes Stephanie Weisner doesn’t know how two-parent families do it all, without a Mike in tow.
Weisner, 38, has been in a polyamorous relationship with her husband, Ian Hubbard, and her work colleague, Mike Wissink, for eight years. The three adults all live together in one home in Moncton, alongside Weisner and Hubbard’s two children, who are seven and nine years old.
The family keeps a joint e-mail account to sort out their household logistics. While Weisner and Wissink, 49, work shifts at their airline industry jobs, Hubbard, 47, home-schools the children. Wissink often cooks and cleans while Weisner does the groceries. All three pitch in with bedtimes and shuttling the kids to their various activities. This winter, the whole family’s going to Disney World.
“We’re very boring and normal,” said Weisner. “We’re not swinging from chandeliers.”
…
Sometimes somebody will ask me about my polyamorous relationships and they often have a preconception that Ruth, JTA and I’s lives are incredibly interesting and exciting (usually with the assumption on the side that we’re particularly sexually-adventurous). But like virtually any other decade-plus long relationship and especially with children in tow, we’re really quite ordinary and domestic. That there’s an additional adult around is basically the only thing that stands out, and we’re each individually far more-interesting and diverse than we are by the product of our romantic lifestyle.
This article pleased me somewhat because of the symmetries between us and the family depicted by it, but especially because they too seem to have to spend time reassuring other that they’re just regular folks, beneath it all. There’s a tendency to assume that if somebody’s a little different from you then everything else must be different too, and articles like this help to remind us that we’re all a lot more-alike than we are different. Even we weird polyamorous people.
After the success of Challenge Robin this summer – where Ruth and I blindfolded her brother Robin and drove him out to the middle of nowhere without his phone or money and challenged him to find his way home – Robin’s been angling for a sequel. He even went so far as to suffix the title of his blog post on the subject “(part 1)”, in the hopes perhaps that we’d find a way to repeat the experience.
In response to an email sent a week in advance of the challenge, Robin quickly prepared and returned a “permission slip” from his parents, although I’m skeptical that either of them actually saw this document, let alone signed it.
With about a day to go before the challenge began, Robin’s phone will have received a number of instructional messages from a sender-ID called “Control”, instructing him of his first actions and kicking off his adventure. He’d already committed to going to work on Friday with a bag fully-packed for whatever we might have in store for him, but he doubtless wouldn’t have guessed quite how much work had been put into this operation.
By 18:06 he still hadn’t arrived to meet his contact. Had this adventure fallen at the first hurdle? Only time would tell…
Update – Friday 9 November 18:45: Robin arrived late and apologetic to find his contact, “Frowny”, at the GBK at that address, was played by JTA.
The pair ate and drank and “Frowny” handed Robin his first clue: a map pointing to Cornwall Gardens in Kensington and instructions on where to find the next clue when he got there. The game was afoot!
Clearly he’d taken the idea of being prepared for anything to a level beyond what we’d expected. Among his other provisions, he was carrying a tent, sleeping bag, and passport! “Clearly my mistake,” he told his contact, “Was giving intelligent people a challenge and then leaving them three months to plan.”
Update – Friday 9 November 19:53: In Cornwall Gardens, Robin found the note (delayed somewhat, perhaps by the growing dark) and began his treasure trail.
Soon after, though, things started to go very wrong…
Update – Friday 9 Novembr 20:40: Let’s take a diversion, and I’ll rely on JTA to keep Robin’s eyes away from this post for a bit. Here’s what was supposed to happen:
Meanwhile, here’s what actually happened:
So now we’re working out what to do next. Right now I’m holed-up in an undisclosed location near Penzance (the ultimate target of the challenge) and Robin’s all the way over in London. We’re working on it, but this hasn’t been so successful as we might have liked.
Update – Saturday 10 November 07:58: We’ve managed to get Robin onto a series of different trains rather than the sleeper, so he’ll still get to Penzance… eventually! Meanwhile, I’m adjusting the planned order of stages at this end to ensure that he can still get a decent hike in (weather permitting).
Update – Saturday 10 November 10:45: Originally, when Robin had been expected to arrive in Penzance via a sleeper train about three hours ago, he’d have received his first instruction via The Gadget, which JTA gave him in London:
The Gadget’s primary purpose is to send realtime updates on Robin’s position so that I can plot it on a map (and report it to you guys!) and to issue him with hints so that he knows where he’s headed next, without giving him access to a phone, Internet, navigation, maps, etc. The first instruction would be to head to Sullivan’s Diner for breakfast (where I’ve asked staff to issue him with his first clue): cool eh? But now he’s only going to be arriving in the afternoon so I’m going to have to adapt on-the-fly. Luckily I’ve got a plan.
I’m going to meet Robin off his train and suggest he skips this first leg of the challenge, because the second leg is… sort-of time-critical…
Update – Saturday 10 November 13:29: Robin finally arrives in Penzance on a (further-delayed) train. I’ve given him a sausage sandwich at Sullivan’s Diner (who then gave him the clue above), turned on The Gadget (so I’ve got live tracking of his location), and given him the next clue (the one he’d have gotten at Roger’s Tower) and its accompanying prop.
Armed with the clue, Robin quickly saw the challenge that faced him…
After all of these delays, there’s only about an hour and a half until the tide comes in enough to submerge the causeway to St. Michael’s Mount: the island he’s being sent to. And he’s got to get there (about an hour’s walk away), across the causeway, find the next clue, and back across the causeway to avoid being stranded. The race is on.
Luckily, he’d been able to open the puzzle box and knows broadly where to look on the island for the next clue. How will he do? We’ll have to wait and see…
Update – Saturday 10 November 14:18: Robin made spectacular time sprinting along the coast to Longrock (although his route might have been suboptimal). At 14:18 he began to cross to the island, but with only a little over half an hour until the tide began to cover the causeway, he’d have to hunt quickly for the password he needed.
At 14:22 he retreived the clue and put the password into The Gadget: now he had a new set of instructions – to get to a particular location without being told what it was… only a real-time display of how far away it was. 7.5km and counting…
Update – Saturday 10 November 14:57: Robin’s making his way along the coast (at a more-reasonable pace now!). He’s sticking to the road rather than the more-attractive coast path, so I’ve had “Control” give him a nudge via The Gadget to see if he’d prefer to try the more-scenic route: he’ll need to, at some point, if he’s to find his way to the box I’ve hidden.
Update – Saturday 10 November 16:50: No idea where Robin is; The Gadget’s GPS has gone all screwy.
But it looks like he probably made it to Cudden Point, where the final clue was hidden. And then kept moving, suggesting that he retreived it without plunging over the cliff and into the sea.
In it, he’ll have found a clue as to broadly where his bed is tonight, plus a final (very devious) puzzle box with the exact location.
The sun is setting and Robin’s into the final stretch. Will he make it?
Update – Saturday 10 November 17:25: He’s going to make it! He’s actually going to make it! Looks like he’s under a mile away and heading in the right direction!
Update – Saturday 10 November 17:55: He made it!
We’ve both got lots to say, so a full debrief will take place in a separate blog post.
Do you remember Challenge Anneka? It aired during the late 1980s and early 1990s and basically involved TV presenter Anneka Rice being dropped off somewhere “random” and being challenged to find and help people in sort-of a treasure-trail activity; sort of a game show but with only one competitor and the prizes are community projects and charities. No? Doesn’t matter, it’s just what I was thinking about.
Ruth‘s brother Robin is doing a project this year that he calls 52 Reflect (you may recall I shared his inaugural post) which sees him leaving London to visit a different place every weekend, hike around, and take some photos. This last weekend, though, he hadn’t made any plans, so he came up to Oxford and asked us to decide where he went: we were to pick a place between 10 and 15 miles away, blindfold him, and drop him off there to see if he could find his way home. Naturally he’d need to be deprived of a means of navigation or communication, so we took his phone, and to increase the challenge we also took his wallet, leaving him with only a tenner in case he needed to buy a packet of crisps or something.
After much secretive discussion, we eventually settled on N 51° 50.898′, W 001° 28.987′: a footpath through a field in the nothingness to the West of Finstock, a village near the only-slightly-larger town of Charlbury. Then the next morning we bundled Robin into a car (with a blindfold on), drove him out to near the spot, walked him the rest of the way (we’d been careful to pick somewhere we believed we could walk a blindfolded person to safely), and ran quietly away while he counted to 120 and took off his blindfold.
I also slipped a “logging only” GPS received into his backpack so that we’d be able, after the fact, to extract data about his journey – distance, speeds, route etc.. And so when he turned up soaking wet on our door some hours later we could look at the path he took at the same time as he told us the story of his adventure. (If you’re of such an inclination, you can download the GPX file.)
For the full story of his adventure, go read Robin’s piece about it (the blog posts of his other adventures are pretty good too). Robin’s expressed an interest in doing something similar – or even crazier – in future, so you might be hearing more of this kind of thing.
Does this review look familiar? It might, a little… my content was shamelessly reused.
At a little over 590 thousand words and spanning 1,349 pages, Vikram Seth’s A Suitable Boy is almost-certainly among the top ten longest single-volume English-language novels. It’s pretty fucking huge.
I only discovered A Suitable Boy this week (and haven’t read it – although there are some good reviews that give me an inclination to) when, on a whim, I decided to try to get a scale of how much I’d ever written on this blog and then decided I needed something tangible to use as a comparison. Because – give or take – that’s how much I’ve written here, too:
Of course, there’s some caveats that might make you feel that the total count should be lower:
On the other hand, there are a few reasons that it perhaps ought to be higher:
Of course, my blog doesn’t really have a plot like A Suitable Boy (might compare well to the even wordier Atlas Shrugged, though…): it’s a mixture of mostly autobiographical wittering interspersed with musings on technology and geekery and board games and magic and VR and stuff. I’m pretty sure that if I knew where my life would be now, 18 years ago (which is approximately when I first started blogging), I’d have, y’know, tried to tie it all together with an overarching theme and some character development or something.
Or perhaps throw in the odd plot twist or surprise: something with some drama to keep the reader occupied, rather than just using the web as a stream-of-conciousness diary of whatever it is I’m thinking about that week. I could mention, for example, that there’ll be another addition to our house later this year. You heard it here first (unless you already heard it from somewhere else first, in which case you heard it there first.)
Still: by the end of this post I’ll have hit a nice, easy-to-remember 594,000 words.
This self-post was originally posted to /r/MegaLoungePearl. See more things from Dan's Reddit account.
She’s 16 months old and while she’s gotten the hang of a few words (notably “cat” – she’s very interested in cats), this morning she surprised and delighted us all as I took her off to nursery by turning to her mother, waving, and saying “buh-bye mum-muh.” Totally adorable.
This self-post was originally posted to /r/polyfamilies. See more things from Dan's Reddit account.
Hi /r/polyfamilies. After much pestering by people who know us, I finally got around to writing about how my polycule and I organise our finances, and I thought that you might be interested to. The whole thing’s described behind that link, but I didn’t want to be seen to be gathering karma or self-promoting, so I thought I’d make a text post to briefly explain it:
Us: My partner, her husband and I are three adults sharing a home (plus, this year, their baby girl!). We rented together for several years, and now we’ve got our first mortgage together. We wanted to come up with a fair way to share our costs (rent/mortgage, bills, shopping, etc.) that wasn’t just “split it three ways”, which didn’t seem fair given that we all earn different amounts – variable even from month to month as my income fluctuates depending on how many days I spend looking after the baby and what kind of freelance work I get, and as my partner gradually returns to work (part-time for now) after her recent maternity leave.
Our system: We use a system of 100% means-assessment based on gross income. So in other words, if Alice, Bob and Chris live together, and Alice earns twice as much as Bob, then she’d be expected to pay twice as much towards their collective household costs, too. And somebody who didn’t earn anything wouldn’t be expected to contribute anything. We didn’t always use 100%: early on, we used 75% – in other words, a quarter of our costs would be simply “split three ways”, and three-quarters of our costs would be split in accordance with means-assessment. Make sense?
It’s really easy: The good news is, it’s really easy to do. I’ve made a spreadsheet on Google Docs that’s a simplified version of our sheet, and you’re welcome to take a copy and use it yourself. Just put in everybody’s salary and what percentage “means assessment” you want to use (0% means ‘simply split X ways’; 100% means ‘split completely according to means’; anything in-between is a balance of the two). Then put in each cost and who paid it (Eve paid the rent, Alice paid for this week’s shopping, Bob paid for last week’s shopping, etc.) and it’ll tell you who owes money to whom in order to square everything up again.
It’s universal: You don’t even have to be a polyfamily to make use of this, I reckon. It works with as little as two people, and it’d work with any household of multiple adults, if you wanted it to. It provides a simple, fair, and slightly-socialist way of splitting up the living costs of a group of people who live together and trust one another.
Let me know what you think!
tl;dr: My polycule and I use a use a spreadsheet to divide up our monthly costs in accordance with our relative incomes, which then tells us who owes money to whom at the end of each month.
This self-post was originally posted to /r/polyamory. See more things from Dan's Reddit account.
Hi /r/polyamory. After much pestering by people who know us, I finally got around to writing about how my polycule and I organise our finances, and I thought that you might be interested to. The whole thing’s described behind that link, but I didn’t want to be seen to be gathering karma or self-promoting, so I thought I’d make a text post to briefly explain it:
Us: My partner, her husband and I are three adults sharing a home (plus, this year, their baby girl!). We rented together for several years, and now we’ve got our first mortgage together. We wanted to come up with a fair way to share our costs (rent/mortgage, bills, shopping, etc.) that wasn’t just “split it three ways”, which didn’t seem fair given that we all earn different amounts – variable even from month to month as my income fluctuates depending on how many days I spend looking after the baby and what kind of freelance work I get, and as my partner gradually returns to work (part-time for now) after her recent maternity leave.
Our system: We use a system of 100% means-assessment based on gross income. So in other words, if Alice, Bob and Chris live together, and Alice earns twice as much as Bob, then she’d be expected to pay twice as much towards their collective household costs, too. And somebody who didn’t earn anything wouldn’t be expected to contribute anything. We didn’t always use 100%: early on, we used 75% – in other words, a quarter of our costs would be simply “split three ways”, and three-quarters of our costs would be split in accordance with means-assessment. Make sense?
It’s really easy: The good news is, it’s really easy to do. I’ve made a spreadsheet on Google Docs that’s a simplified version of our sheet, and you’re welcome to take a copy and use it yourself. Just put in everybody’s salary and what percentage “means assessment” you want to use (0% means ‘simply split X ways’; 100% means ‘split completely according to means’; anything in-between is a balance of the two). Then put in each cost and who paid it (Eve paid the rent, Alice paid for this week’s shopping, Bob paid for last week’s shopping, etc.) and it’ll tell you who owes money to whom in order to square everything up again.
It’s universal: You don’t even have to be a polyfamily to make use of this, I reckon. It works with as little as two people, and it’d work with any household of multiple adults, if you wanted it to. It provides a simple, fair, and slightly-socialist way of splitting up the living costs of a group of people who live together and trust one another.
Let me know what you think!
tl;dr: My polycule and I use a use a spreadsheet to divide up our monthly costs in accordance with our relative incomes, which then tells us who owes money to whom at the end of each month.
I recently finished reading a novel called Ice & Lemon, which was given to me by my mother for Christmas (my reading list is quite long at the moment; I’m only just getting close to catching up!). I could tell you about what I liked about the book – and I will, in a moment – but before that I’d like to mention what makes this book personally so spooky to me, as a reader.
My mother got it for me because the coincidences apparent on the front and back cover appealed to her:
Okay, so – that’s a handful of quirky coincidences, certainly, but I’m sure if you looked at every volume in a bookshop – in the right frame of mind – you’d find a dozen other novels that seemed similarly fortuitous. But as I began to read the story, I discovered that I shared a lot more in common with the story’s Daniel than I could have possibly predicted. It was almost as if I were reading an alternate-history version of my own life – it’s incredibly easy to see how believable choices made in the early 2000s could have lead to a reality that even-more closely paralleled with my own:
There are about a hundred smaller coincidences in Daniel’s story, too, but after a few of them you stop looking objectively and you can’t help but see them, so I’ll spare you the list. If I wanted to, I’m sure I could find plenty of things that definitely didn’t fit me: for example, Daniel’s significantly older than me. That sort of blows the alternate history idea out of the water. But nonetheless, it was a disturbing and eerie experience to be reading about a protagonist so much like myself, travelling around a post-disaster area that I personally know so very well. I feel like I ought to reach out to the author and check that he’s not just pranking me, somehow. His son features in the book, but somehow the coincidences that naturally occur as a result of this are less-impressive because they’re pre-informed.
The book itself is pretty good: a soft science fiction story full of a thorougly-explored post-apocalyptic grief. Very human, and very British, it exemplifies that curious sense of humour that we as a nation exhibit in the face of a disaster, while still being emotionally-scarring in the sheer scope of the tragedy it depicts. The science of the science-fiction is… questionable, but it’s not explored in detail (and it’s only treated as being speculative by the characters discussing it anyway, who aren’t scientists): this is a story about people, suffering, and survival, not about technology nor futurism. There are a handful of points at which it feels like it could have done with an additional pass by a proofreader; while occasionally distracting, these typos are not problematic. Plus: the book contains the most literal deus ex machina I’ve ever encountered (and thankfully, it doesn’t come across as lazy writing so much as general wasteland craziness).
It’sunder £3 in ebook format, and if I didn’t already own a paperback copy, I’d be happy to pay that for it. Even if it didn’t make me feel like I was looking at an alternate version of myself.
Last weekend was an exciting and unusual experience, full of exciting (expected) things interspersed with a handful of exciting (unexpected) things. Let’s go chronologically:
I left work, picked up a rental car (having unfortunately forgotten to take my counterpart driving license to the rental place, I had the choice of either cycling for an hour to collect it or else paying a fiver for them to run a DVLA check, and I opted for the latter on the grounds that an hour of my time (especially if I have to spend it cycling back and forth along the same stretch of road) is worth more to me than a picture of Elizabeth Fry. I drove home, packed a bag, said goodbye to Ruth, JTA, and Annabel, and drove up to Preston.
There, I spent most of Friday playing the new Mario game with my sister Becky, gave a few small performances of magic (did I mention I’m doing magic nowadays? – guess that’ll have to wait for another blog post) at various places around Preston, and went out for a curry with my mother, my sisters Becky and Sarah, and Sarah’s boyfriend Richard. So far, so ordinary, right? Well that’s where things took a turn. Because as Becky, our mother, and I looked at the drinks menu as we waited for Sarah and her boyfriend to turn up… something different happened instead.
Sarah turned up with her husband.
It turns out that they’d gotten married earlier that afternoon. They’d not told anybody in advance – nobody at all – but had simply gone to the registry office (via a jewellers, to rustle up some rings, and a Starbucks, to rustle up some witnesses) and tied the knot. Okay; that’s not strictly true: clearly they had at least three weeks planning on account of the way that marriage banns work in the UK. Any case case, I’ve suddenly got the temptation to write some software that monitors marriage announcements (assuming there are XML feeds, or something) and compares them to your address book to let you know if anybody you know is planning to elope, just to save me from the moment of surprise that caught me out in a curry house on Friday evening.
So it turns out I’ve acquired a brother-in-law. He’s a lovely chap and everything, but man, that was surprising. There’ll doubtless be more about it in Episode 32 of Becky’s “Family Vlog”, so if there was ever an episode that you ought to watch, then it’s this one – with its marriage surprise and (probably) moments of magic – that you ought to keep an eye out for.
Next, I made my way up to Edinburgh to meet up with Matt R and his man-buddies for a stag night to remember. Or, failing that, a stag night to forget in a drunken haze: it’s been a long, long time since I’ve drunk like I did on that particular outing. After warming up with a beer or two in our hotel room, the five of us made our way to the Glenkinchie Distillery, for a wonderful exploration into the world of whiskies.
And then, of course, began the real drinking. Four or five whiskies at the distillery bar, followed by another beer back in the hotel room, followed by a couple more beers at bars, followed by another four whiskies at the Whiski Rooms (which I’d first visited while in Edinburgh for the fringe, last year), followed by a beer with dinner… and I was already pretty wiped-out. Another of the ‘stags’ and I – he equally knackered and anticipating a full day of work, in the morning – retired to the hotel room while the remainder took Matt out “in search of a titty bar” (a mission in which, I gather, they were unsuccessful).
Do you remember being in your early twenties and being able to throw back that kind of level of booze without so much as a shudder? Gosh, it gets harder a decade later. On the other hand, I was sufficiently pickled that I wasn’t for a moment disturbed by the gents I was sharing a room with, who I should re-name “snore-monster”, “fart-monster”, and “gets-up-a-half-dozen-times-during-the-night-to-hug-the-toilet-bowl-monster”. I just passed out and stayed that way until the morning came, when I went in search of a sobering double-helping of fried food to set me right before the long journey back to Oxford.
All in all: hell of a stag night, and a great pre-party in anticipation of next weekend’s pair of weddings… y’know, the ones which I’d stupidly thought would be the only two couples I knew who’d be getting married this fortnight!
A week ago, Ruth pushed a baby out of her body, completely upstaging my birthday and, incidentally, throwing all of our lives pretty much into chaos. Having gotten to the point at which she’d resigned herself to “being pregnant forever“, Ruth would have certainly been glad to have that stage over and done with, were it not for a long and painful labour followed by a torturous and exhausting birth.
There’s a lot that can be said about the labour: a 38-hour crescendo of Ruth gradually and repeatedly finding levels of pain and tiredness that each seemed impossible, until she reached them. But Ruth has suggested that she might like to write a little about it herself, so I shan’t steal her limelight. What I can say is that I didn’t – and I don’t think that JTA, either – appreciate quite how emotionally draining the experience would be for the two of us, as well. There was a strange sensation for me about twelve hours in: a sensation perhaps most-comprehensible by our friends who’ve done emotional support work. That was: after watching somebody I love so much suffer so greatly for so long, I felt as if I’d somehow begun to exhaust whatever part of my brain feels empathy. As if the experience of supporting Ruth had served to drain me in a way I’d never fully experienced before, like when you discover a muscle you didn’t know you had when it aches after an unusual new exercise.
Of course, after the ordeal we got to take home a little bundle of joy, who continues – despite now having a perfectly fabulous name of her own – to be referred to as “tiny”, even though her birth weight of 8lbs 12oz (that’s about 4kg, for those who – like me – prefer to think in metric) doesn’t really make that a very fitting nickname! Nor the amount of damage she did to Ruth on the way out, which also might be ill-described as “tiny”! She’s also often referred to as “the poopmachine”, for reasons that ought not need spelling out.
My employer was kind enough to give me paternity leave, even though I’m not the biological father (JTA is; and he’s very-much still in the picture!). I’d looked at my contract and discovered that the wording seemed to imply that I was eligible, stating that I’d be permitted to take paternity leave if I was about to become a father, or if my partner was about to give birth, the latter of which seemed perfectly clear. To be certain, I’d wandered along to Personnel and explained our living arrangement, and they just had looks on their faces that said “we’re not touching that with a barge pole; let’s just err on the side of giving him leave!” As a result, we’ve had all hands on deck to help out with the multitudinous tasks that have suddenly been added to our lives, which has been incredibly useful, especially given that Ruth has been spending several days mostly lying-down, as she’s been recovering from injuries sustained during the delivery.
Despite everything, we and the rest of the Three Rings team still managed to push the latest version into testing on schedule, though fitting in time for bug-fixing is even harder than it would be were we at our “day jobs” during the daytimes! It’s not that our little poopmachine takes up all of our time, though she does seem to take a lot of it, it’s simply that we’re all so tired! For the last few nights she’s been fussy about sleeping, and we’ve all lost a lot of rest time over keeping her fed, clean, and feeling loved.
For all my complaining, though, what we’ve got here is an adorable and mostly well-behaved little bundle of joy. And when she’s not covered in poop, shouting for attention, or spitting milk all over you, she’s a little angel. And I’m sure you’ll all be sick of hearing about her very soon.
