Why I am not posting about re:Invent

•

Oops, I should've announced this: folks, I am all alive and fine — I am just not posting thoughts about re:Invent for now! I appreciate all the slightly-panicked DMs y'all sent me and I am flattered that you were so concerned 😊 1/12 (thread to explain why I am not posting)

What is the first reason I am not posting about re:Invent? It's not my style. I hate "first look" posts — I consider them high-risk (I could be wrong) and low-value (everybody does that + I will have a deeper dive posted in December*). For me, it's not worth it 🤷 2/12

What is the big reason am I not posting about re:Invent? Confidentiality agreements and non-disclosure agreements. This is mildly braggy, but I know a lot of "secret" stuff which makes my style of posting A LOT more complicated! Let me tell you how messy this gets... 3/12

You know how AWS goes on stage, presents a new thing, and then goes "and folks at Company_A have been using this already and they saved X% dollars, moved Y% faster, did Z% better"? I might or might not have been involved in testing some things 🤐 4/12

You know how AWS is customer-focused? AWS legit builds most things because customers yell and demand those things! I might or might not be known for chatting with AWS about things 🤭 5/12

You know how AWS has AWS Heroes — a group of highly-respected super-skilled community members that get to talk with AWS? Somehow I am part of that group. AWS Heroes literally got 14 hours(±, it's fuzzy) of pre-briefings with "this is what we're launching at re:Invent" 🧑‍🏫 6/12

ALL those things led to me knowing a lot of "secret" details about what AWS launched or will launch at re:Invent. Or that will be launched next year. Or in two/three years cause some things take time. Or never cause, you know, reality is cruel sometimes. 7/12

ALL that information must remain secret until AWS makes it public That means I can either: 1) share generic stuff ➡️ Boring! 2) share actually useful stuff, but only after I double-check what was released, what is public, and what is not public ➡️ Impossible/a lot of work! 8/12

I'd hate to post something like "AWS just announced Service-A with support for X, Y, and Z" aaaaand then to find out that support for Z did not actually make the release and that will be announced in January. 🤦‍♂️ 9/12

I'd hate to post something like "yeah, AWS announced Service-B which they described as Y but actually when I used it it was more like Z" aaaaand then to find out they actually fixed that issue since I last tested it. 🤦‍♂️ 10/12

I'd hate to post something like "wooo, AWS Service-C now supports W by doing X which means you can now do Y with no effort" aaaaaand then to find out that those details were actually still secret and that they would only be revealed in a session Friday afternoon. 🤦‍♂️ 11/12

So yeah, I will continue to remain kinda quiet during re:Invent. But I will be back to blabbing my mouth in December and January! Some blabbing will be public and some blabbing will be private, but I will be back to annoying you all! 12/12