From the "department of trying way too hard", I'd like to mention that you can pull subtitle information and often massage that into a transcript, either with the DOM [0] or by looking at the traffic and downloading it. [1] However, in this case those are subtitles from speech-recognition, so it's only really useful for skimming broadly.

Pasting the whole thing would probably not be useful, but here's a sample from the downloaded XML:

> if you think about it like tiny components one of the best things about say a tiny method when you look at a tiny micro service is it allows you to consider replacing it but you can change it you can understand it really quickly but even if you can't if it's small enough and it's named well enough and it's decoupled well enough microservices tend to be you can throw it away and just restart if you have to

[0] Example: https://gist.github.com/DHager/2e01f0b82e5d3f5a39e6

[1] Look for accesses of https://www.youtube.com/api/timedtext

Sometimes I like to consume content like it's not fast-food.

That's what's great about reading - you have the freedom to do so if you want to!

This is about a specific design pattern that some of us may have exposure to. It's not a speech for the ages as far as I can tell.

"The only thing we have to fear... is fear itself! And microservices!"

"I have nothing to offer but blood, toil, tears and sweat. Oh, and microservices. If we can get the Germans to adopt those, they're totally fucked"