I’m not going to give you an overview of everything that happened at the meeting. I had some 8+ papers and I needed to focus on my own plus shepherd a few ones I volunteered myself for. Other trip reports go into depth about the overall events: I’m going to focus on what I saw, what I worked for, what I pushed through, and what I learned! Let’s dig in.

“Late”, aha. This is becoming a habit, isn’t it? In an earlier post, I talked about the C++ Rapperswil Committee meeting and said I’d be at CppCon 2018 volunteering and doing work!

(I wrote this paper but forgot to publish it, sorry! I’m still gonna publish it as a bit of a retrospective on what I prepared…!) Got all loaded up decked out for the big paper bonanza; practice talks, draft papers with Double T’s, and more…

I am not great at writing proposals. In fact, I am absolute 🐕 💩 in many aspects. But, I had feedback and help, so I wanted to put out some tips so that when people write proposals they are much less trash when they hit the Committee. I want to read 🔥 💯 ✌️ papers when they hit the Committee, rather than being the fuel for a trash-fire.

The warm up is done, and it is time to choose. Not between Apples and Pears (would pick apples, by the way). It’s time to make some choices about something that’s been looming over the Standards Committee for a long time, and is part of two pretty important papers in the San Diego mailing: