It was not my first year attending, and my reasons for showing up are pretty clear by now.
It was a challenge to be more spiteful than a few of the service names, but I managed.
3 weeks was WAY too long. I almost died.
And I attended to watch specific people speak, not for specific sessions. That's why Speaker search is so important.
I'll definitely be back for #reinvent. And I recommend it to others, though in some cases less for its utility than as a hilarious prank.
Superlatives! I'm very sincere about my favorite part. The improvement bit might be snark.
Now a bunch of bubbles that aren't interesting. I always rate "how did you like the Speaker X keynote" with top marks. I have issues with some of the *content* but I don't want that to reflect on the speaker any.
Full credit to @ajassy. He's gone from good speaker to great speaker over the years.
But I'm pretty sure his career prospects don't really hang on my opinion any.
I'm sincere when I say the Partner Keynote helped me figure out why I was always cold on APN content.
I really liked Swami's keynote as well, but I find the entire ML space to be patently ridiculous. There *is* value there. It's not being articulated; instead it gets drowned out by massive hype.
Peter DeSantis's keynotes are always wonderful. Getting to peek at the magic behind the cloud makes it feel like Christmas.
And of course @werner's keynote struck a desperately needed note. A+ would watch again.
What about my sponsor expo nature walk?! My @jeffbarr livestream?! Nothing?
Now @awscloud requests that I stop mocking them and instead pivot to actually punching them in the metaphorical face.
It was easy for me to connect with AWS staff because I installed Amazon Chime. The rest wasn't great.
I mean... give me an ICS feed and let me add my schedule to that?
1. Cloud bills only ever seem to go up.
2. The conference is orthogonal to the very real problems @awscloud solves for its customers. I recommend it *when appropriate*.
Now a list of new services and whether I'm "not interested" (ML and IoT), "interested" (most other things), or "already actively exploring" (gp3, Cloud Shell, Proton, DevOps Guru, Lambda changes.)
In previous years partners weren't allowed to imply that the cloud was insecure. These days @awscloud themselves expresses their insecurity through questions like this.
The preferred capitalization is "Arm."
And I know Intel powers it because of the keynote pre-roll Intel ad right before they got into how much better Graviton2 is.
I'm unclear as to what "featured" means in the context of this event.
I'm also self-promotional.
I often wonder what different answers to these questions results in. "Ooh, you're new to AWS, maybe you won't remember a previous horrible misstep!"
Questions like this make me question whether @awscloud really understands big data. Or data of any size, really. Shouldn't they know this better than I do at this point?
Absolutely. I presume we'll meet on Twitter, right?
• • •
Missing some Tweet in this thread? You can try to
force a refresh
It directionally aligns with conversations I've had with a lot of folks internally. And the anonymous Amazonian raises a lot of points that honestly paint AWS in a pretty flattering light.
There are some problems with it, and there's basically zero chance they didn't unmask themselves. How many @awscloud cybersecurity folks use Sioux Falls as their shorthand for "Bumfuck, Nowhere," and turns of phrase like "Companies don't like to have their whole ass be shown?"
It feels like it might be Thread of Uncomfortable @awscloud Truths time again.
Now that #reInvent has subsided, you get to choose between CDK, sam-cli, Serverless framework, Proton, Service Catalog, Service Catalog App Registry, and SAR.
Making that decision is way more entertaining than doing your job.
Now that AWS has begun naming services after things shouted on the factory floor (Lookout for Metrics/Equipment/Vision), next year we can expect "Who the Hell Parked in my Spot," a container pre-empting service.
I've decided I'm going to start selling software as if I were the Cyberpunk 2077 developers.
Please start by using my Stripe webcart to send me $70.
Okay, so the software I sold you *claimed* to help fix your @awscloud bill, but it crashes unless you run the script on FreeBSD.
I am very sorry for the inconvenience. Please stand by while I work on a patch.
After a lot of tweaking, this bash script now works on Ubuntu 14.04.
The patch itself is 22GB because I don't know what git-rebase does and I got sloppy with my git-adds somehow. Thank you for your business, please continue to be patient.
So @awscloud likes to make a big deal about "the first launch of #reInvent." Let's do something else: the last launch of #requinnvent. That's right, I'm dumb enough to launch a product during #reInvent.
Let's start by talking about cost management SaaS tools. A thread...
I've been on record for a while as saying that they suck, because they do. "Percent of your @awscloud bill" pricing, they try to do way too much (you don't use 90% of it), and they're all trying to be Expensive and Complicated Cost Explorer.
Worst of all, a tool can't replace a person in analyzing your AWS costs. There's no API for business insight, and attempting to install one into your staff apparently violates a bunch of laws.
And now, a nitpicker's guide to @awscloud's new Cloud Shell offering, announced today at #reinvent.
I was surprised and delighted to see it today. Yesterday, I was surprised and delighted to see the new console search.
Both product teams were apparently surprised but not so delighted to see each other.
Sadly there's no data on the persistence guarantee of that 1GB of storage. "THAT'S WHERE ALL OF MY PRIVATE KEYS LIVED!" shrieks the future customer with even worse workflow patterns than me.