So far it's universally positive, but the AWS folks need to finish being furious and stop seeing red long enough to work their keyboards to yell at me.
Someone in DM points out that measuring ML's success in terms of AWS is like measuring cloud in terms of IBM. "AWS only markets something aggressively when they're behind."
This person isn't employed by a competitor.
Now I have a 30 minute call to chat with someone about how an @awscloud service works; they're attempting to build a company / offering around said service.
Somehow I wound up on a rant about databases that managed to only mention Route 53 once. Weird!
Now a call with someone my team put onto my calendar without context...
It was a "talk about why they should sponsor us" meeting, followed by a catch-up / debrief.
People should sponsor us because we're awesome, obviously. And people pay attention to it. lastweekinaws.com/sponsorship/
Checking what I've missed while otherwise on calls, and it would seem a mug was shipped to someone, reminding me that I've got swag to sell you all. lastweekinaws.com/products/coffe…
Back to email. I've been invited to Microsoft Build apparently. Sure I'll go!
@peterc mentioned last week's article about being post-OS in the excellent StatusCode newsletter.
AppDynamics was named a leader in the Gartner--
More praise in the email has come in. None of these people appear to work for a large cloud vendor or IBM.
A DM came in attesting that @awscloud Rekognition absolutely solves a business problem and to say otherwise is madness.
Right--that's my point:
I reach out to my graphic designer to let him know that once again his genius is being misunderstood within his lifetime. This is a stylistic choice that looks juuuust off enough that people think it's a bug.
An AWS GM either asks an insightful question about the future of ML in the ecosystem, or for me provide a quote to help shore up a defense about why his service doesn't prominently feature "Machine Learning" in its marketing.
Now I'm working with @robgalanakis on the next generation of a component of my newsletter build pipeline. He built something that works but is... finnicky to deploy, so I'm attempting to shove the thing into @awscloud Codebuild to make it Not My Problem anymore.
Rob has fallen into the same trap I once did--trying to get anything Serverless to make a lick of sense locally for development. Once I gave up on that and turned my test cycle into whacking "deploy to AWS" it got a lot more streamlined.
It's got less to do with cloud independence than it does "trying to mock AWS services locally on a Mac."
(It would take me a day or two to port this entire serverless application to GCP or Oracle Cloud. Azure... would take more time.)
A gift has arrived from @mike_julian and the team showcasing @daiwaka’s excellent work about my favorite topic.
Okay, I can replicate it in a clean environment, which means it's CodeBuild time.
I'm reminded that the @awscloud CodeBuild team hates customers, so it asks them to manually input an ARN without autocomplete or even a link to go build one.
They *REALLY* hate their customers: because I tabbed between the two, it's refusing to accept an empty service role name, despite me providing an ARN.
Smooth, CodeBuild console team. Smooth.
Reloading the page and a bit of dickering with it later, and codebuild works. Only 5 failed builds before one worked.
Now I have a marketing meeting with @mike_julian and @NatVeisWilliams, which is a lofty term for "quantify my shitposting."
Their quantitative measurements of X shitposts per hour clash with my qualitative measurements of rage per shitpost, so we end the meeting after an hour at the same impasse.
I get dragged into a sales call by @LorenSaunders85 with the explicit instruction to speak as little as possible. I stand by the Zoom greenscreen switch so I can vanish instantly if needed.
I controlled myself and didn't get hit with the hose.
New code to my service now gets auto-deployed via CodeBuild after much cursing.
I got tipped off about a new CFP I should submit for. I'll livestream that next week.
A leading indicator that @bequinning loves me and wants me to be happy.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
DtnamoDB is a pretty poor DNS resolver, but @alexbdebrie is the person to talk to about it. I wound up hiring him to fix a thing on contract; strongly recommend.
If Matt looks like the kind of person you'd enjoy having in your company, I'd suggest reaching out sooner than later. His greatest challenge right now is articulating exactly what he wants to do next; once he solves that he won't be available for long.
And now: you've likely heard of @AskAManager; in this thread ask an admittedly-terrible employee what to do for an "alternate" take on workplace questions.
(DMs are open if you’d prefer not to implicate yourself.)
"Only white guys interview for an open role."
Ask the folks at your company who aren't over-represented what they think of the job description and tweak accordingly.
If everyone at the company is a white guy, you have your answer already.