Oh ho ho I just saw this. With @gaberivera's begrudging permission and significant trepidation I will be tackling the mini-essay questions in a tweet thread. Let's begin!
I'm a fan of @techmeme. The first essay question explains what the requirement is. The article in question is located at neowin.net/news/webrtc-be….
Answer 1: "Technology I don't understand certified as standard by groups you don't understand to do things nobody understands."
Answer 2: "This story is an unattributed sponsorship of Techmeme by Google. Please perform unpaid image classification work for them to train their AI/ML services."
Apparently there was some confusion:
Answer 2: "Insufferable jackass fails to understand technology, laws, and how every tech company's terms of service actually work; also conflates 'conservatism' with 'violate hate speech.'"
Answer 3: "Company that makes processors whose value proposition is 'making Intel seem competitive' discovers lack of customers; pivots to industry that believes touchscreens are a smart idea for vehicle controls and is thus presumed to be older, dumber."
Answer 4: "Journalist who writes code instead of trusting PR folks takes internet by storm. If you aren't following @wongmjane then what are you even doing, go do that immediately."
Answer 5: "While many observers see the challenges with the government's case against Facebook as being rooted in antitrust law, the reality is that prosecutors are strangely timid to aggressively pursue a company with access to private messages and a network of toilet cameras."
And lastly! One tweet for each publication to follow.
1. While you could claim @verge's in-depth coverage of tech news lands them the #1 spot, the reality is that a lot of the Techmeme folks are night owls, and the dark theme is way easier on the eyes.
2. "Before it's on Techmeme, it's on @business. And before it's on Bloomberg, it's on the Bloomberg Terminal. And before it's on the Bloomberg Terminal, it's on background."
3. "The @nytimes drives engagement by spurring Twitter influencers to angrily and publicly cancel their subscriptions for the third time in a week."
4. "The @WSJ helps Techmeme cater to a varied audience with its combination of astonishingly good journalism and breathtakingly bad opinions."
5. "Having multiple providers for redundancy is a good idea; similarly Techmeme depends upon @TechCrunch to provide VC opinions in case VCs are suddenly unable to shitpost on Twitter because Miami lost internet access."
But seriously--Techmeme is an amazing aggregator that I depend upon. I'd encourage interested folks to apply. techmeme.com/jobs
• • •
Missing some Tweet in this thread? You can try to
force a refresh
I'm at the AWS Summit in NYC, where I believe that nicknames are for friends--and Gennifer Artificial Intelligence is no friend of mine.
Good morning.
Thirsty much?
A game / challenge at the AWS Startups booth: how long can an AWS employee go without mentioning GenAI? Someone just made it all the way to one minute, ten seconds!
Okay. Let's do Networking Specialty. Practice question 1:
Correct answer is B.
"Wrong!" says the answer key, "it's B because network load balancers don't support client IP preservation."
Except that they do. They absolutely do. They have for the past year. I'm just a boy, standing in front of an AWS Cert team, asking them to do their damn jobs.
Today's cloud marketing story is called "The Tale of Hot Rebecca," and is a truthful recounting of dinner last night.
Strap in; it's a fun ride.
Back in my early 20s, I had a number of friends / acquaintances in my (primarily Jewish) social circle named "Rebecca." It was kind of a problem.
("Can't we spray for them?"
"…not since the 1940s.")
So every Rebecca got an adjective, much like the seven dwarves. One of them asked me once what her adjective was, and I responded in a fit of unadulterated honesty, "you're Hot Rebecca" because honestly? Damn.
Made it to the #GoogleCloudNext keynote seating finally. Let's see how this goes now that the world is starting to wake up to a "much of the AI hype is unwarranted" reality.
Boeing: "HOW ARE THEY DOING IT?!"
Airbus: "We bought a torque wrench?"
Boeing: "No, how are you being a featured customer testimonial at #GoogleCloudNext?"
Airbus: "Oh, that? We made a strategic decision to not be walking poster children for corporate negligence."
And now, some DevOps / SRE / Sysadmin / Ops / ENOUGH already tips I learned from early in my career--brought to us by our friends at Chex™ Mix. All of these are great ideas that you should implement immediately...
DNS is notoriously unreliable, so use configuration management to sync all of the servers' /etc/hosts files. Boom, no more single point of failure.
Future-proofing is an early optimization, so don't do it. Every network should be a /24 because that's how developers think. I mean come on, what are the odds you'll ever have more than 253 hosts in a network?
And the Amazon earnings are out for Q4. A miss on @awscloud revenue by $20 million because analysts didn't expect one of you to turn off a single Managed NAT Gateway.
Let's explore deeper into their press release.
For 2023, AWS sold $90.8 billion of services, most of which were oversized EC2 instances because you all refuse to believe Compute Optimizer when it tells you there are savings to be had if you're just a smidgen more reasonable.
Word frequency in the earnings release:
Customer: 87
Employee: 11
Generative: 16
Cloud: 24
Serverless: 3
DynamoDB: 2
Union: 0