Thread by @QuinnyPig

In an effort to help my dear friend @mattstratton hit 9000 followers, I will now watch his most recent talk video (which I have not seen) and liveroast the living crap out of it / him in this thread. Join me!

https://twitter.com/mattstratton/status/1242987448407412737

We start by noticing that the embedded video on the page is not in fact @mattstratton's talk, but rather @KrisBuytaert's, demonstrating the attention to detail responsible for Matt's transition out of writing code and into talking about how other people should write code instead.

The real talk lives at

"It's great to be back in NYC" says @mattstratton, demonstrating the primary DevRel duty of going to exotic places and drinking with your friends.

"I work at PagerDuty" says @mattstratton who no longer works at @pagerduty due to a rumored "sleeping through a page" incident.

"What the hell is a service?"

To AWS, a thing that lasts forever. To Google, a thing that's already on its way out.

But @mattstratton settles on the definition of service that leads directly to bikeshedding about the meaning of the word "Team."

"Service Mitosis," because DevOps is truly the powerhouse of the cellular architecture.

"Thanks to Aaron for correcting me on this slide, the old version had Stonehenge which is technically not a monolith."

True story: Stonehenge is in fact IBM's third generation mainframe.

"...and delineating on-call responsibility inside something like @pagerduty," says @mattstratton, checking the 'you have to pay me for this trip' box like a good DevReloper.

PagerDuty is of course the service that wakes you up at 3AM, and (at the time of this talk) was represented by Matt who has the exhausted look and wild hair as if he was just woken up at 3AM. Now that he works for IBMHat his suits put mine to shame.

At this point in the talk @mattstratton demonstrates recursion by, and I am not kidding, explaining the process of explaining an inside joke.

Demonstrating that he is not now nor will he ever be an @awscloud culture fit, @mattstratton discusses why good names are important.

Having vanquished the DevOps Naming Wars, Matt now turns his attention to taunting the SRE naming convention.

Next he pivots to explaining how alerting and oncall should work, speaking ex cathedra as a person who at the time maintained no production services and whose responsibilities were confined to either business hours or conference happy hours.

Because he's the ThoughtLeader we deserve, @mattstratton is ahead of the curve by bypassing telling engineers they're doing it wrong and skipping directly to telling senior leadership they're doing it wrong.

Matt Stratton no longer works at PagerDuty.

He's now making his third reference to @honeycombio. Honeycomb doesn't employ developer advocates directly because they don't need to; everyone else speaks adoringly of them for free.

"This is when you want @pagerduty to wake you up."

I can only imagine the internal OKRs on midnight wakeups of others.

Now discussing the lifecycle of a service. "Design," "build," "maintain/iterate," and eventually "retire / go work for @RedHatGov."

One guess where @mattstratton works now!

And his bio is the last slide, well done.

Twitter, his podcast, his speaking site, his license plate for stalking purposes, and running the DevOps Days Chihuahua.

And thus endeth the talk. "Come work with me at PagerDuty, we're hiring" sadly didn't age super well, and there was a lost opportunity to bikeshed about where microservices start and stop.

All in all, another excellent @mattstratton talk. Please follow him on the twitters.