Well, as promised, my travel calendar finally calmed down after May and I got to start shipping again 😊
It's probably a good sign that I've barely been finding the time to blog in the last few weeks right?
WARNING: Extremely long and information-rich blog post incoming! I started putting this together in my head on the last day of the conference as a way to gather and report out on some discussions. Before long it turned into an entire over-3000-word roadmap.
As you might imagine, we've been pretty busy this week, between being front page news in parts of the tech press and prepping for our upcoming conference! I also spoke at SCaLE last Saturday — great turnout, really engaged audience, nice questions afterward, love our community — so I've once again been cooking for a little longer than usual. That means this is going to be a short update :)
Am I really postmortem-ing this one? Too soon? Never, I have a whole weekend coming up to wipe my brain completely smooth. Gotta get it out first.
Hello, don't mind me here, just borrowing the title for this week's blog post from my favorite poet.
I'm back! I'm back from a cross-Atlantic trip that involved a Saturday/Sunday conference, meaning that I've been failing to take adequate time off from work for about 11 days and counting! Let's see how coherent this post turns out :)
Oof, I have had terrible blogging cadence the last few weeks! The one thing you're supposed to get right at all costs — stick to a schedule — and I'm blowing it!
Did you know that often, journalists aren't able to choose the titles of their own stories, and it's up to the discretion of their editors? Horrible, right? Can you imagine not being able to give your blogs their own titles, no matter how silly? Me neither.
I can tell DevRel season is starting back up again, because I counted the number of flights I currently have booked in the next 6 months, and came back with 18. Granted, some of these are vacations, and I'm a bit of an over-preparer when it comes to vacations (PLEASE do not start me on a conversation about min-maxing Chase points, I will embarrass us both), but a big part of that is the job! I'm usually on the road a little more than once a month from January-May, and while I think that's a mostly sustainable cadence (and appreciate getting face time with AT heads from all across the world), it does come on pretty strong every year.
This week's blog post title comes from my very brief period as a beer nerd about 15 years ago. I should have known it was hopeless; I'm already too many other kinds of nerd, and I really like to buy the same session IPA or Italian pilsner over and over again (for some reason not everyone agrees with this, but actually all beer should be about 4.5% ABV). People started bringing all these different imperial stouts over my house and expecting me to drink them in the middle of the afternoon... it was a very confusing time.
There's something about the week after Thanksgiving... as a colleague said to me in a meeting on Monday: it gets kind of sad when you're at the "microwaving gravy" stage of getting through your leftovers.
Well, I totally failed to start writing this before EOD on the east coast the day before Thanksgiving, so my readership is unlikely to do Ryan Lizza numbers this week, but what can you do?
In this business, we have a lot of ways of saying "hey, you know this kind of sucks, right?" I like to think of it as analogous to the 50 Words for Snow concept -- which, with all due to respect to Kate Bush for her album title, I believe has actually been discredited since as an overly exoticized way of viewing Inuit languages, but then again, I did a linguistics undergrad in the late 2000s, and it was popular at that time -- where am I going with this? Oh, right. We have a lot of ways for saying that something kind of sucks because a lot of things in open source software development kind of suck :)
Hello again! It's been a very big week for the more protocol-brained among us here, since this week was the triannual IETF meeting in Montreal where two of my colleagues and many of our community members helped lead a session to take AT to the IETF. That session recording is now available for anyone wanting to catch up on the discussion and the plan for drafting parts of AT as IETF specifications -- see also this repo -- and this marks a really exciting next step towards maturing the governance of AT.