End of January beginning of February is DevConf.CZ and FOSDEM and since both are quite close to where I live, the plan was to run out to Brno for the first event, run back home for a few days, then zoom down to Brussels for the other event.
I woke up miserable on Sunday, but since I had stayed out late the night before, I just stumbled into the shower, thinking I only needed a little steam healing. But I just felt worse. And worse.
I took a minute to count up the symptoms. Fever. Cough. Achy skin.
When at home, we speak English, but in public, as much as possible, I try to speak Dutch which just means that I’m damn good at ordering a cup of coffee and buying my train ticket at the kiosk – when I travel the use of Dutch explodes quite a bit between the hotel / commute / airport.
When we first moved to the Netherlands seven years ago I used to get headaches because my brain would try to serve up Japanese as my second language instead of going straight to Dutch. Every time I’d try to practice, my brain would translate Dutch to Japanese to English and back again.
For about six months.
One day I woke up and the Japanese was gone.
Like, GONE gone.
Whenever I’d try to think of some common phrase, my brain gave me Dutch.
But then we had kids and I really want them to be familiar with some Japanese, so I started re-learning via Duolingo. And also, because my partner and our three children are Swedish, I thought now would be a great time to fold in Swedish as well.
So every day I complete at least one module of all three languages within the app, never imagining there would be a situation when I used more than two languages within a short period of time.
A replacement plan is a great resource, even when you’re not being replaced.
A year ago, as the role of OpenStack community manager at Red Hat was moving from one person to another, we started thinking about what needs to be in place to effectively transition a role. More generally, we started thinking about planning, and documenting, for your eventual replacement.
We’ll talk about what worked, what didn’t, and what had unexpected benefits for the larger community.
This presentation helps existing and new community managers take a hard look at their roles within their projects to delegate tasks, encourage future advocates, and facilitate the evolution of their community role.
This post is going to be super first world and come from a place of massive privilege – I recognize that I’m in an amazing place to be able to talk about owning a house and selling it and buying another one and setting up my own office at home. That it’s amazing to have a job, to have a remote job, to have a well paying remote job with an amazing company like Red Hat. All that. This post is entirely about bragging about my new home office. And while I feel incredibly proud of how hard we’ve worked to get where we are today, I also realize how very much this is because we appear white and straight and well functioning and normal and this is very much an advantage we have in the world.
I have my very own home office.
Separate from my own home.
When we found out we were pregnant with twins, among the plethora of stressors was that we’d need to remodel our house extensively to make it work once said twins were old enough to want their own spaces. This is YEARS in the future, but it was still right there with all the other OMG things that were dancing through my DOUBLY hormonal brain.
And instead of taking a deep breath and Putting It Aside we put our house on the market, found a new house, packed, moved, and had babies.