TRANSKRIPTIO 🔗
Adam Jacob: Hello, welcome to AI Frontiers, where industry experts run down all the AI news. For engineers, it's Monday, the 16th of November. Yes. So grab a snack and let's get started. I'm Adam Jacob. I'm the CEO of Swamp Club. I'm joined this week by my Swamp co founders, Paul Stack,
Paul Stack: How's it going?
Adam Jacob: Nick Steinmates,
Nick: That's me.
Adam Jacob: and product manager, virtualization nerd, longtime Microsoft y. Now figuring out how to use agents to do PM stuff, Sarah Cooley.
Sarah Cooley: Hey hey.
Adam Jacob: All right, let's let's run down the news.
Nick: It's definitely Monday too. That's why you knew the that's why you knew the date today.
Paul Stack: Hahaha
Adam Jacob: You know, 'cause it's Friday the thirteenth. and on on Friday it was, but then, you know,
Paul Stack: On Friday, passed. Yeah.
Adam Jacob: like yeah.
Nick: My favorite part of the Discord is we have them so confused whether what day we actually record this on. And it's because
Adam Jacob: That's true.
Nick: we ourselves are confused about which day it
Adam Jacob: All the time.
Nick: is and also which day to record this on. So it's like anyway, my favorite lore about the podcast so far.
Adam Jacob: Yeah. It's it is it is the way. also you just learn things about me. I'm terrible with numbers and dates.
Nick: Yeah.
Adam Jacob: okay. let us begin by talking about what is clearly the top news item of the week. Jensen's out. so you know, first we had affair with Chinese spy, we denied affair with Chinese spy. Then it turns out we had another a second affair, this time with a direct report. and then now a third affair, apparently with another direct report, but who as yet remains unnamed. the board he tendered his resignation to the board. Sarah, what do you think? No more gents in an Nvidia.
Sarah Cooley: the memes have been incredible. I'm like real verdict out on the if they did more digging, would they find out that there have just been massive numbers of GPUs going to China forever and they just don't want the investigation or what? Because it seems like, maybe this is me editorializing in the world we're in right now, but it
Adam Jacob: Please do.
Sarah Cooley: seems like affairs would not be. warrant the apparently it's one too much or they really don't want to do a deeper investigation. But it's wild. Like it's wild how fast that happened.
Adam Jacob: Yeah, it is insane how fast it happened for sure. key, what do you think?
Nick: Yeah, I think the conspiracy theory that I floated last week that he was you know, it was the opposite of a honeypot and he was doing it all for love of country. you know, that seems
Adam Jacob: Turned out to be
Nick: seems to be not the angle to follow, given,
Adam Jacob: Yep.
Nick: you know, you violate the cardinal rule as an executive, which is which is sleep with your direct report or whatever. Like, not a good look. I also I I also am more in the camp that that's not what did him in. but you know, who cares at this point.
Load full transcript
At the same time at the same time, it's gonna be interesting to see just how much of NVIDIA was Jensen versus NVIDIA the machine, and what that means for the company. I think that that's where all of the speculation's at now. everyone's passed the salacious headline and is now what the fuck is gonna happen to NVIDIA? what does this mean for them? What does this mean for their dominance? do they become Intel? and like anyway, big problem.
Paul Stack: My favorite part of the whole week was the rumors that Elon is going to try and hire Jensen for Terra Fab, which is
Adam Jacob: To tariff. Yes.
Paul Stack: kind of hilarious because the CEO job spec that went out, there was literally only one person in the world that is kind of qualified for that role. I'm like, sure.
Adam Jacob: Yes. And then a bunch of NVIDIA employees signed a letter being like, If if you don't bring Jensen back, we're all gonna go work for Elon and Jensen at Terfab. Like, which is also insane. thank you, social
Nick: And what's
Adam Jacob: media.
Nick: one of the one of the stories that Jensen loves to tell is like, you know, he dialed up TSMC and like built that relationship from the ground up by literally calling them from the yellow pages or whatever. And they don't have a contract in place. They're just homies. And he's like, Hey, you know, we've been a reliable consumer, you've been a reliable supplier, like that's the nature of the relationship between the companies. And if you think about how important TSMC is to all of that to all of that, and how important their relationship is, at least as he portrays it, yeah, it's like troubled waters ahead for NVIDIA.
Paul Stack: Yeah.
Adam Jacob: Yeah, it's a whole thing. I made the mistake maybe of just weighing in on this on social media, which is like I just I have real I like I just I have beliefs about the fact that like there's some ethical lines that CEOs just ought to be held to. And when we don't hold people to them, like it's just inappropriate and wrong. And one of them is like I think it's impossible to have an affair with a direct report and have that not be an ethical violation, regardless of how consensual it may or may not be, because I'm your boss. And I can decide if you get paid or not, and all kinds of stuff. And it's like just way too easy to cross that line. And boy, I brought out all of the right-wing internet crazies, I just got a stream of people being like, why are you such a loser? I got told that even saying it was like a what was it they said? It was like essentially they were like, it's a feminist lie or whatever. And I'm like, it's
Nick: Mm-hmm.
Adam Jacob: not, actually. It's just a really straightforward truth. And like I think. in terms of what does you in, it's like in some ways this I feel like the spy allegation was actually more survivable. because while while there while it was troublesome and there's a bunch of evidence there from a board point of view, you could make an he could make an argument the whole time that he's like, well, but it the r the initial relationship was only unethical to my wife. It wasn't like like those things were not unethical in the way that deciding to sleep with two of your directs were.
Paul Stack: Unless, thousands of GPUs went to China, then it's unethical across the spectrum.
Nick: And and also finding a finding a direct path. It's a getting yeah, which drives
Adam Jacob: But I bet you open Well, but it turns out that thousands of GPUs
Nick: everything up.
Adam Jacob: going to Malaysia wasn't illegal.
Paul Stack: By the way, what you were actually called was a bullshit feminist slop on Twitter. Because I laughed my
Adam Jacob: Thank you, thank you. Bullshit feminist slop.
Paul Stack: ass off when I read that this morning. like, yeah.
Adam Jacob: Which look, I am a feminist, so I'm pleased to be bullshit feminist plo slop. But yeah, it was like I think I think there's a lot of folks who like, you know, I'm sure that that investigation opened up. I'm sure they found the first one. I'm sure they found the second one toot sweet after that. Who knows if there's more? All of that stuff, like there's a reason he resigned instead of was fired, because they're gonna want to bring him back, you know, like they gotta leave that door open and they did. they were polite on the way out the door. Like, I think there's you know, this story's not over, both because we have like congressional investigations to go through, we got all kinds of other shenanigans, but like I think the odds he comes out of this clean and returns to Nvidia as CEO at some point remains high. Like I don't think that's the
Paul Stack: I'd like to thank Jensen because for doing this, the meme game has been so strong this week on a quiet news week. It's been great. It's kept me going.
Adam Jacob: The meme the meme game has been she Sarah, you're totally right. The meme game is the greatest perhaps ever.
Sarah Cooley: It's been lit.
Paul Stack: You
Sarah Cooley: So the real question, did the Chinese agent lose her job too? One must s assume.
Nick: She was absolutely promoted. What are you talking about?
Adam Jacob: depends on which job. I mean maybe
Paul Stack: Definitely promoted. Definitely promoted. Yeah.
Sarah Cooley: Yeah.
Adam Jacob: both, because now she's been added as a Chinese spy, so she lost her spy job and she lost the job at Mega Speed, probably. yeah, it could be
Paul Stack: Hey, that's not how it goes in the movies. James Bond has outed hundreds of times every fucking movie and he never loses his job.
Adam Jacob: Yeah. And someone said to me that the VP that he slept with is gonna lose her job. And I'm like, no. Talk about Lawsuit City. Like there is no legal team. I mean, not on Earth that would let that happen that way. Just a big nope on that one. and like, you know, whatever. Elon Musk does all sorts of bad things. like And gets away with it. And I think there were a lot of arguments that were like, this is fine because
other people have done it and gotten away with it. And it's like, no, actually, it was wrong when they did it too. And
Nick: I don't think any of those people worked for him. That's a that's a big
Adam Jacob: yeah. One of his baby mamas worked directly for him. so you know.
Nick: All right. Well there
Paul Stack: One of
Nick: you go.
Paul Stack: his baby mamas, Jesus Christ.
Adam Jacob: He's got a lot of baby mamas. And they weren't
Nick: Yeah, he does. Yeah.
Adam Jacob: his wives. I don't know what else to call him.
Nick: Yeah.
Adam Jacob: he's got 20 kids or whatever. You know, it's a lot. I don't think he's a great dad. I don't know. Maybe he's a great dad. It's gotta be weird.
Nick: Who knows?
Adam Jacob: 20 kids. probably good Christmas gifts. It's probably good. Okay,
Paul Stack: Being a trillionaire gets you a lot of kids, I'm guessing, right? A lot of childcare.
Adam Jacob: let's move on.
Nick: Yeah.
Adam Jacob: Anthropic launched Fable and Mythos 5 2. Fable looks a little even more powerful than it was before. I've only done some small bits of fabling with it, but it looks pretty great. I think also they gave away some free resets. So it was like free token day for everybody, which is also a delight. you know, this is right before the IPO. It can't hurt. I don't think it makes a difference. and also Opus five five has remained so good that I don't know that I was like that I was crying for for a better fable, but All right, Paul, you're shaking your head. You got feels?
Paul Stack: Yeah, the rumors this week are that 5.5 tanked or rather was tanked before Fable 5.2 came out. I've tried Fable 5.2, it is off the hook. It is so good, but I'm getting maybe 10 % of usage that I would get from Opus 5.5, which is crazy. as the week has, say again.
Nick: So it's token hungry? Is that what is that what that means? It's token hungry? Is that what you mean?
Paul Stack: Yeah, it's like really verbose. just, it's, it's just taken, you just don't get access to as many tokens with it as you would do with Opus five five. for me, it's like, it's kind of awesome. for what it's done, it's, it is definitely like, you can see that they've, they've done a huge improvement on it from fable five one. it definitely doesn't feel like it's a daily driver. Like, you know what I mean? It's definitely not, but For me, the more interesting thing is the fact that they might have the suggestions are and people have measured it that they tanked five five five to make it look that fable five two is better. And I have had some very interesting agent sessions this week. where I'm like, what are you doing? that's just
Nick: Mm.
Paul Stack: not how you've been performing the whole time. even told, even, the first time in a long time, I threatened my agent and said, I'm canceling my subscription and using chat GPT again. I'm like, it had no effect this time. Usually it's like, I'm sorry, blah, blah, blah. Yeah. So yeah, it's like, off you go, buddy. We're IPOing. It doesn't matter, Yeah. Yeah.
Nick: It's like go ahead. I know your tricks. That's how you know AGI is here. Your threat doesn't work anymore. Yeah.
Adam Jacob: You're lucky you didn't Yeah. Yeah, you're lucky you didn't get banned.
Paul Stack: no, I didn't like say nasty things out of it or anything. I was just like, but I mean, 5.2 is very good. Like, and I'm, you know, I'm not one that usually gets excited about models that are usually boring for me. I'm really more interested in what Mythos 5.2 would give to be totally honest with you. That's the one that I'm like very, very interested in. But of course, like so like locked up. Yeah.
Adam Jacob: Yeah. We're not getting a hold of it anytime soon. Sarah, what do you think about that conspiracy theory? That
Sarah Cooley: yeah.
Adam Jacob: they tank the performance of the lower end model to make themselves look good?
Sarah Cooley: I don't know, man. I'm in a weird place right now where I'm I'm really curious which things are like, this was amazing. Like I love this. I don't know that they're like tanking the cheaper, we'll say cheaper models. I think that probably they're just like, you get to live on our cheaper hardware. Like we're just going to make this service less premium because we expect fewer people. You get the last generation of GPUs. Go hang out over there. Cheaper model, have fun. and we're gonna have to figure out how people do price differentiation at some point and like what it means because we've been subsidizing tokens so much. But I'm really curious what people love at new models because I've been in the mode for a long time where the model's intelligence is not my problem. Like, I mean, one of the reasons I wind up here talking to you delightful people is like my harness is way behind the intelligence of my models, and it has been for probably the past like. three or four waves of model releases. granted, they're pretty fast waves, So I'm really
Adam Jacob: Yeah, yeah.
Sarah Cooley: curious, is it like getting better at a thing or or what? Because it's been a while since it's like intelligence is my blocking problem.
Paul Stack: Yeah,
Nick: Yeah.
Paul Stack: the interesting thing here is you're right, the intelligence is pretty great across the board, but... The structural changes that they're making to it, with regards to, it's verbose crap, it's output, it's structure, all of this type of thing is actually making it more efficient to use that, that you can actually get better pieces of it. And some of the features like they have where it's like, you know, like how it can spin up sub agents, how it can become controllers, how it can become orchestrators. That's kind of like why it's appealing in some ways. I do not keep up with the latest models. I was in 4.6 for forever until 5.5 came out, because I hated every model in between. I'm just nosy, which means that as soon as one came out and I got a free reset, I'm like, free tokens, I'm going to burn them. I'm going to see what I can do.
If I did not get a free reset, I would not have used those tokens at all.
Sarah Cooley: Is this also good as some
Nick: Yeah, it's weird. go ahead.
Sarah Cooley: I was just I have a partner who does mechanical engineering tasks, and I do know that the more recent models have become much, much better at domain-specific things. So it seems like they've been doing a pile of RL for things outside of being a good developer. and I do remember back in it's dog years, AI moves in dog ears. I have no idea how long ago this was, but there were the like one or two models that couldn't speak English, where they were like fine at code, but for some reason language just like regressed terribly. so I think that they're tuning for different applications probably. So it wouldn't surprise me that it's a much better orchestrator or what have you. But I think it's gonna become more bespoke. Sorry, Nick, go for it.
Nick: No, n I was just gonna say I remember when Fable Five One came out and I used it a a little bit to do some like analysis of the Swamp Club code base, specifically around security, because that's what you know it was supposed to be really good at. Let's say it found the like things that should be fixed, but also nothing pressing. but clear gaps that that Opus at the time had missed. And like Yeah, I think that was literally the only application I'd used Fable for, and then completely forgot about it, to be honest, until Fable 5 2 came out. And now I'm like, You know, again, it's just like, do I do I need to spin up that agent to do it in that way? Like, I don't think so. But you know, everyone's getting hacked right now, so maybe I should. so
Adam Jacob: Yeah, I think I think Sarah, your point about like it's been a minute since intelligence was my problem. Like that just that feels really resonant to me. You know, like the the reality is that the all the other pieces that we've put in place around the model, in terms of like how am I double checking your behavior, how am I testing the output, how am I doing all of those things, like, you know, those things also decrease my need. For the intelligence to be as high as it otherwise would have been. And so there's there's there may be some trade-off where it's like, hey, if the model's super smart, I need fewer of those guardrails. But of course, that's also probabilistic because sure it's smarter, but how much smarter, and how frequently does it stay smart? And, I so it's it's an interesting trade-off that I think we're still figuring out how to do, as an industry.
Nick: Well, I'm hoping
Sarah Cooley: I will
Nick: that Chinese homies are distilling the fuck out of Fable and making disdeepseek and
Adam Jacob: Mm.
Paul Stack: you
Nick: whatever even better. Because
Adam Jacob: No doubt they are.
Nick: the thing that I love
Paul Stack: on the GPUs.
Nick: about new model releases is it raises the floor of open source. And if what we're saying is we're not so excited about the level of intelligence over the
last few models or whatever, like that's how far behind these open source or open weight models are. And so they're gonna reach that floor. at some point where we just get to get rid of anthropic or whatever and, run run the open weight stuff,
Adam Jacob: Totally.
Nick: at the same fidelity, which is gonna be fucking awesome.
Paul Stack: I did meet a person in the wild this week at a conference in Germany who uses LeChunk, which I was like so happy that I met somebody
Adam Jacob: Amazing.
Paul Stack: who uses it on a day to day basis. And I was asking, was like, what do you like about it? It's like, I'm not giving any of my data to anybody. It's literally like mine
Nick: Ha ha
Adam Jacob: Yeah. Yeah.
Paul Stack: and I do whatever I want. And I actually asked them what it was like and it was like, great, like absolutely brilliant. Gives me everything I need. And I was like really happy to meet somebody in the wild with LeChunk.
Nick: That's great.
Adam Jacob: Yeah, and also it's La Jonc. It's the greatest model
Paul Stack: Yeah, exactly.
Adam Jacob: name of all time. Okay.
Paul Stack: It is.
Adam Jacob: let's move on. Let's talk about this is a fun blog post. Michael Baricella. Let's hope I got his name right. I need to I need to start asking people how
Nick: Baccarella?
Adam Jacob: to s how to how to s Baccarella, probably. Yeah, that could be better. wrote a great blog post about his time at Jane Street and essentially how they false smoke alarm almost drowned the data center that they had sitting next to the floor. And the story here was basically that some dust got kicked up in a renovation. That triggered a smoke alarm. when the smoke alarm gets triggered, what happens is the sprinklers pressurize, but they don't come on immediately because that would be bad, like in a skyscraper in general, that's not what you want. So what happens is the pipes pressurize and then they wait for heat to reach a certain Threshold, at which point then the sprinklers will go off. So, if you've ever seen the little red things on sprinklers, they're they're those are those are heat sensors, not not they're not not anything else. So when the fire alarm was triggered, the other thing that you do, just in case, is you turn the AC off because it keeps the air from circulating in the room in the hopes that you don't like keep the fire going harder inside your skyscraper. Unfortunately, this is also where they had built the server room. So all the servers were still on and they were generating a bunch of waste heat. And so they wound up in this cycle where the waste heat
Paul Stack: Cheers.
Adam Jacob: was pushing the temperature up. And this guy happened to live a couple of blocks away from this data center and it happened when nobody was there. and he got this phone call that was like, Hey, you've got minutes to get into this room and unplug all these servers before the sprinklers go off and destroy all of the gear. And so he tells the story of having to like run over
there and then go upstairs and actually unplug. physically unplug the entire data center before it reached 150 degrees. and then the sprinklers would go on and destroy everything. And what this story made me think is that we were, you know, we're recording this on Friday the 13th. It's not Halloween, but I wish that I had thought of it for a Halloween episode. let's tell a horror story real fast. So this was a horrible
Nick: Yeah.
Adam Jacob: operation story. This is one of those stories where you're like, no, this was going to be real bad. So let's go around the horn. Nick, do you have a do you have a do you have a horror story you want to share?
Nick: Well no. I'm gonna take a slight detour and just say, too bad they didn't have the technology that the refrigerator people, you know, supermarkets did where they could turn that
Adam Jacob: In France.
Nick: shit off remotely or whatever. Then you wouldn't have had to run into that room. And sorry.
Paul Stack: too early, too early. my God.
Adam Jacob: Yeah. Yeah. Yeah, it's unclear to me why they didn't just run S bin shutdown in a for loop. That did come to that did come to mind, but
Nick: Yeah. Yeah, it turns out you need a state actor to turn some machines off. Anyway, no, I don't have a horror story.
Adam Jacob: You don't have any.
Nick: No, my favorite okay, my favorite short story, horror story, is the last man in the world sat in a room, and then something knocked.
Adam Jacob: Yeah, that's creepy. Okay, that's a good one. Sarah, do you
Nick: There you go.
Adam Jacob: have a do you have a do you have a ho any horror stories?
Sarah Cooley: I've been racking my brain, but whenever a technical horror story comes up, I'm like the person running around being like, Can I get you coffee? I'm so sorry this is happening to you, people doing work. as is the play the PM. man, I think the last one that was really bad, I'm gonna struggle to remember the external versus internal names. I'll just describe it when we all figured out that like you can do speculative execution and have multi-tenant attacks on all of our cloud
Adam Jacob: yeah.
Sarah Cooley: infra. That was a really bad day for a while. And then
Adam Jacob: Yeah.
Sarah Cooley: triaging and discovering that stuff when you have disclosure dates is
Adam Jacob: Well
Sarah Cooley: like it is painful, man. I I feel right now, I feel I'm gonna feel bad when when this comes up later where I'm like, I don't feel that bad about Outlook. We all have different ways of communicating, but like
Adam Jacob: Yeah.
Sarah Cooley: I so feel for people who are handling those types of things that come up in unanticipated ways where it's just like, who knew that this would be a problem when you built a data center? It all
Adam Jacob: Right?
Sarah Cooley: it all makes so much sense when you organize the system, And then something like this
Adam Jacob: Until it does it.
Sarah Cooley: happens and you're just like, I'm sorry that nobody was able to think through that particular failure mode. yeah.
Adam Jacob: Yeah, for sure. Paul?
Paul Stack: have many, many, many fucking more wounds with regards to operations, like management. I guess my worst one, when I worked at open table, a long, long, long time ago, there was a, a puppet script went wrong and we had this like huge logging infrastructure that like pulled in like customer metrics and like, all these different pieces of information. was taking about a billion messages a day through this. it was like, you know, nodes on the edge, Kafka feed and other Kafka nodes and like making its way through and replicating and the elastic search, like elastic search cluster was like 120 EC2 nodes. was just like massive and, and misconfigured puppet script took down the three main puppet nodes, which were like the coordinators. weren't the data nodes and the whole thing just went dead. And of course, like That misconfiguration meant that no reviews were able to be made, none of this level of information, and it was basically a three-day repair of it. It was
Adam Jacob: Oof.
Paul Stack: two days before New Year's it happened. On New Year's Eve, I was sitting at a friend's house during a party with my laptop, still dealing with it, and it was just an absolute disaster. After that... That's probably definitely the one that was the worst, a three day systems outage based on misconfiguration.
Adam Jacob: yeah, that's brutal. Yeah.
Nick: I I'm now realizing that you asked for a technical horror story and not just a horror story in general.
Adam Jacob: Just not horror stories in general. I like that you gave us a horror story in general. I mine mine was what this story made me think of was, and I've told this story in some forums before, but I was working for a startup. We I was the like only operations guy, but they had like hired me a boss who was like a you know, like a director of operations and like it was just the two of us. And he was a retired Marine Corps colonel. And I had spent the evening getting really drunk. Like drunk, like the kind of drunk you can only be in your like early twenties. You know what I mean? Like inappropriately drunk, as an adult. And and he starts paging me because, you know, you still carried pagers or whatever. And I wasn't supposed to be on call. That's why I was super drunk. And and so finally I call him back and he's like in his like very marine core voice was like, you know, soldier, you know, you gotta the servers are down. You gotta come fix it or whatever. And I'm like, nope, super drunk. can't be doing any of that right now. and he was like, sober up, I'm coming to your house. And he roared up in his suburban or whatever and had a cup of coffee for me and drove me to this data center and stood next to me while I drunkenly tried to figure out how to bring a bunch of Solaris machines back online. I forget, I don't even remember why they died, because I was too drunk to remember and just like. I just remember him standing over my
shoulder, giving me words of encouragement, like it was Vietnam. he was like, We're we're all gonna make it home, I'm not gonna leave you alone, It was very
Nick: Ha
Adam Jacob: intense. and then we got it all working and, you know,
Sarah Cooley: This is something.
Adam Jacob: I couldn't even tell you what our product was. I don't even remember what we did. Cause I'm not sure we ever did anything useful
Paul Stack: Cause you're still drunk or okay.
Nick: Well.
Adam Jacob: because it was pre dot com crash, you know, where you could just be like, What's your company do? And we were like, Internet, you know. And then people were like, Great, you're bigger market cap than Microsoft, it was just very strange. It's a weird era.
Sarah Cooley: Yeah, I gotta say though, I love the two two things, but they're both pretty quick. I love with the Marines or army, anybody in the military, like this belief that you can take a drunk teenager and solve all of the world's problems if you give them enough documentation is actually like a kind of beautiful thing where you're like
Adam Jacob: Look, it he was right. It I did it. It worked.
Nick: No
Sarah Cooley: Yeah. Well
Adam Jacob: I was like, I can't do it. I'm too drunk. He was like, No, you're not. No, you're not. Yeah, exactly. Yeah. Totally.
Sarah Cooley: Yeah, he's like, I've done more with less, And the other thing I love is you were his LLM that day. He was like,
Nick: Ha ha
Sarah Cooley: I am gonna prompt you into getting what I need out of your brain,
Adam Jacob: Yeah. That's exactly what he did. And he just hustled me through the whole thing. He was like, You need coffee and me yelling at you. And we're gonna get through it together. And we did.
Paul Stack: So note to self, don't get hideously drunk on a work trip with Adam. Otherwise he's gonna make me work on just like Stanna.
Adam Jacob: Yeah. I had to learn from the best.
Nick: What's the reverse meat proxy? I don't know. We'll figure it out, but
Adam Jacob: Okay. well unless you want to share a technical horror story. I think you did a good job with the OneNote story, Kate.
Nick: No, no, no, I'm gonna keep it awkward that I didn't answer the question at all. So
Adam Jacob: Keep it awkward that you didn't that you didn't grok it. Makes perfect sense. they published the Slop Manifesto. and the thing about the Slop Manifesto I noticed first was that it's too long. you know, like part of why the Agile Manifesto is great is that it's short. you know, four values, twelve principles done. This one is basically saying, hey, we don't want to live with slop. and so they say, you know, we've come to value outcomes over output, understanding over speed, our own thinking over a model's first draft, better work over easy work, and improving the system over patching the output.
Nick: Yeah, if they just had that if they if they literally just had that bold section in this article and that's all they posted,
Adam Jacob: I'd agree.
Nick: you you'd you'd be like, Yeah
man, this wasn't generated by Claude. and now
Adam Jacob: Right. And then you gave me nine points more about what you believe. And then from ten to twenty two, twenty-two points. you gotta slim your manifesto down. That's my feedback.
Nick: once 'cause it was written by speakers and attendees. So, they everyone had to get their point in, turns out.
Paul Stack: Yeah, we got to get off this fucking high horse about slop, my opinion, honestly, it's starting to get people are getting more bogged down now about worrying about slop than they are about actually delivering systems. And sure, one person slop is not another person slop, right? It all depends on the outcomes. It depends on the performance. It depends on the security aspect, all these different things. But it's starting to get frustrating. It's really it just feels like massive smoke and mirrors. And it just feels it's just this huge hill people want to die on. It's like, I'm gonna make myself very unpopular here. It's like the software craftsmanship movement all over again, just moved to a different era. you know what I mean?
Adam Jacob: yeah, yeah.
Paul Stack: Sure,
Nick: In
Paul Stack: I love that people like are like are in it and they love their craft and they do it, but like, who are you to tell another person that their stuff's locked? You know what I mean? It's like.
Adam Jacob: Yeah, we're gonna you're gonna hit me with the w like your how many complexity tokens you're allowed or whatever and why we gotta use simple simple tools or whatever.
Paul Stack: Exactly. And and I did find out this week and I told internally that I was at a conference and I heard that there was a company, I cannot name that name, that they have a token improvement plan. So when they
Nick: Plan. Yeah.
Paul Stack: don't hit specific tokens, so they're encouraging people to experiment through stuff. Is that slump? Who cares? People have to learn, people have to understand it. Let's just focus on building good engineering systems and it doesn't matter about what the code comes out the other end of this moment.
Nick: Y you
Adam Jacob: We
Sarah Cooley: Matt.
Nick: know what, Paul?
Adam Jacob: think so.
Nick: I love that.
Sarah Cooley: no, I was just gonna say if you could hear my eyes roll whenever you say token improvement plan, if I could just roll my eyes continuously.
Paul Stack: We don't do that. Just making sure you know that and all the viewers know that. We don't have a...
Adam Jacob: Yeah. But they would roll out of your brain, right? straight out
Nick: Yeah.
Sarah Cooley: Yeah.
Adam Jacob: of your head.
Sarah Cooley: It would be like it would be incredible, but every time I hear it, I just viscerally cringe at a deep soul level. Because
Adam Jacob: Yeah. Yeah, me too.
Nick: Yeah.
Sarah Cooley: we all know how to do performance reviews. Just stop worrying about AI. Just are people doing their job that you expect with the tools that they have and the capabilities that they have and the processes that they
have. Just judge whether people are doing their job, And at some point they won't
Adam Jacob: You wish.
Sarah Cooley: keep up. If they're not keeping fresh, they won't keep up. it's just like the vegetables, Sorry, that's my
Nick: Yeah.
Sarah Cooley: tirade.
Adam Jacob: Gutaried.
Nick: Absolutely. And and yeah, Paul, I love that haters get a hate mentality, actually. that's what you made me think of. And yeah, it seems like there's a particular set of people that are very anti you know, they're they're almost like Luddites when it comes to AI in a way. And like, yeah, it's just another angle to attack it. and also I sympathize with those people and all of that stuff. change is hard. and
Adam Jacob: Yeah. I but I think the the it's the gatekeepy part that I don't want. I don't need you I don't need you I don't I don't
Nick: I yeah, th there you go, that's the right word.
Adam Jacob: I don't need you yelling at people about how what they wrote is slop. And sometimes when I read things, I'm like, you meet proxied me. You know? Or like like or somebody sent me a link to a thing they were excited about because they'd built it and I'm sure it was awesome. But I couldn't read it because it was like thirty pages long of Claude explaining. all this stuff that it didn't I didn't I couldn't get through it. And I don't know that that was because Claude wrote it or maybe they wrote it and that's just the way they wrote, maybe that was their natural writing. But what I didn't do was tell them, I think your product sucks. you know, like I was like, I'm I'm struggling to understand it because I can't see through like I like it's a little too much, a little too verbose. But I didn't say, why'd you slop can in me, bro? You know?
Nick: Yeah. The whole problem with Claude though is you could read two sentences and it feels like thirty pages. and so like you know, who knows how many tokens there actually were, but god damn is that so hard to read every time, you know?
Adam Jacob: But I don't think it's gonna be better when we send somebody a link to the slop manifesto in the hopes that they will change their behavior,
Paul Stack: No, it's just gonna like it, like it just, it's gonna be, it's gonna feel massively rude. Like I was at a conference last week where Eric Meyer talked about it he's like, Hey, LLMs and like they're producing code better than 99.95 % of people at this moment in time. Like they just are. If, if the outcome is not the outcome, then it's because it's probably not been prompted in the right way. But like, I mean, let's be honest. I never wrote the most fucking best code in the world. Like you could look at my code before and say was proper slop. Like.
Nick: I look at my code
Paul Stack: Does it matter?
Nick: all the time, it's enshrined behind me and it's actually beautiful. So I don't
Paul Stack: But like honestly, it is such a subjective thing. Sure, when it comes to writing styles and sure when it comes to documentation, you can look at it and
think, Jesus, that's hard to read. But when it comes to actual code itself, it is so subjective. And that's why I akin it to the software craftsmanship movement, because if you didn't write it in the right way that they loved and that they cared about and that they pushed in a specific way, it was not good code, not clean
Sarah Cooley: Yeah.
Paul Stack: code, right?
Sarah Cooley: And
Adam Jacob: Yeah.
Sarah Cooley: and this is like a high horse that I have because again, using AI to do PM things. I think people have deep opinions about how AI writes code, but how AI just writes is also another taste judgment moment where it's like, I've been a manager for a number of years. I can't tell you how many junior employees I sit down and I'm like, Your email doesn't say what you want at the top of the email. The person you are sending sending this to, especially this person, that probably will read the subject line. They might read the first sentence. If you don't tell them what you want from them in the first sentence, it will not happen. If if if you can make it so they can answer with a yes, no, like Jeff, do that. You know what I mean? But writing is also
Nick: Yeah.
Adam Jacob: Yeah.
Sarah Cooley: a taste judgment exercise, like writing code.
Adam Jacob: Holy.
Sarah Cooley: And so, the chances are even that they actually just have bad writing judgment. Cause it's a skill,
Adam Jacob: Totally. Cause it's and it turns out lots of people do. Yeah.
Sarah Cooley: Yeah.
Adam Jacob: right. yeah, the number of people in my career that I've introduced to Barbara Minto's pyramid is high. You know? And it's just in
Sarah Cooley: Yeah. Yeah.
Adam Jacob: case you haven't, you should read it. The Pyramid Principal, Barbara Minto, incredible. She like was the first like female consultant at at which one? I doesn't I'd have forgotten. She's a legend in the seventies. She basically was like, here's how you do executive communication. she wrote the book on it. It's it's the it's the thing. Also, if you tell your agent to write like Barbara Minto, does better. like it'll solve it'll solve that problem.
Sarah Cooley: I'm gonna try that. Legit.
Adam Jacob: You can be like, write this in Barbara Minto's pyramid, and it'll be like, okay, it'll be like first things first, conclusion first, you know?
Paul Stack: It was McKinsey, right? She worked out by the way. It was McKinsey, right?
Adam Jacob: McKinsey, yes. She was the she was the first female consultant at McKinsey. I think. I could get that wrong. That may be the legends over legending.
Sarah Cooley: I love that you found a writing framework. You're like, my whole jam, here's a writing framework to apply to your writing, anyway.
Nick: There's there's
Adam Jacob: yeah.
Nick: a f there's a few of them he loves.
Adam Jacob: Yeah, I've got that's not the only one. I have several.
Paul Stack: We have Diataxis, our doc site is based on Diataxis as well.
Adam Jacob: Yeah. Yeah. If you wanna just hang out, I've got I could
keep going. that's like just the kind
Nick: Ha ha
Paul Stack: Yeah.
Adam Jacob: of stuff that I like.
Paul Stack: This is the follow-up podcast writing with Adam.
Adam Jacob: Yeah, exactly. Just well no, we should just do one that's only me talking about frameworks. Anyway, love a good framework. Thanks, Sarah.
Nick: I'm gonna be sick that week.
Sarah Cooley: No, I'm into it, but I'm weird. Okay, anyway.
Paul Stack: I thought you were going to say you're washing your hair, Keith.
Nick: yeah, that
Adam Jacob: I know you have my back.
Nick: too.
Adam Jacob: okay, so the folks at I have never known how to pronounce this. Atun? Atun? Atun. Ellie Huxtable is the person who wrote it. so Atun was like a search engine for your bash history. It was like syncing it into the cloud and across machines. It was a useful tool. it's now been extended to work across threads. So basically syncing agent history across machines. Which is then allowing you to resume tasks in different models across different harnesses, all those sorts of things, because it's sort of decentralizing the history of sort of what you've said and how you've done it. and I think there's been a couple of passes at this where, you know, this is one where it's thinking about like how do we store the information about what the agents are doing, about our own conversations, how do we then restore that or understand it sort of in in different places? And I think that idea that there's a substrate that sits underneath the agent harnesses that we work with that is helping us to figure out what we want to do. I think those are good ideas. And I'm not sure how I feel about this particular implementation. I haven't actually sat down and run it. But what I thought was interesting about this article was that and this release was that I think it points to the fact that there's there's still things that are gonna feel pretty simple and pretty straightforward that like. I don't know if this is a good idea or not, but I think it's interesting you did it because things that sit at this layer that you can move around, is the kind of weird I want to see right now, if that makes sense.
Paul Stack: Yeah, this is the layer at which a bunch of cool things are happening at this moment, right? Like outside of the harness, like harness agnostic, like the transportable like systems, people can start to program themselves a little bit, like, like take advantage of them. And like that goes back to what we were talking about earlier, right? Moving away from specific model implementations allows you that transportability, really allows you to be able to choose the different pieces that you want. I had such a long conversation in Germany about this during the week. And somebody was like, why don't you run local models? like, it doesn't matter what model I run at this moment in time. And if ever I'm caught at building an implementation in a specific way. for a model then I've gone wrong and I love that people are actually starting to do this at the same level right they're just really giving you that versatility.
Nick: What we're also finding though is that deep integration into the model or harness that you're choosing is something that's really interesting and can be differentiating. And so that's an interesting thought. And also, what are the chances that it's a tune?
Adam Jacob: It's pretty good.
Nick: Yeah. I've just
Sarah Cooley: The Discworld Turtle, that one?
Nick: been I've just been
Adam Jacob: I think it is the Discworld. It's literally the Discworld Turtle. How do you pronounce the Discworld Turtle's name? A tune. That is exactly what it is. Yes, it is a it is a reference to the Discworld Turtle for sure. Yeah.
Sarah Cooley: Yeah, yeah, yeah. A tune. Yeah. Perfect. We got it. Go team. Fantastic.
Nick: I was just sitting here thinking, what could it possibly be reading it? And so that's what I came up with, and I'm glad that that's right.
Adam Jacob: Yeah, the the logo is a turtle.
Nick: I I don't know what that reference is, so maybe that maybe that's outing myself as as an
Sarah Cooley: yeah, they made a mock world. Yeah.
Nick: awful n not nerd or something for the first time.
Adam Jacob: Yeah,
Sarah Cooley: Yeah, that is awful. You should go read it. It's like a joyful, joyful universe. But yeah, basically a satirical writer, Terry Patchett, wrote an entire little world about a whole society that's on a plate on top of four elephants on the back of a turtle flying through space. And it's just fantastic. Like I love that they made, you know, talking luggage a prominent character and depth death. And you know, there are witches and all of the things. It's it's a delightful place to spend some time if you want some popcorn reading. on the original topic though, let's not pretend that harnesses are like solved. you you're talking about this and I haven't read the blog post, so full disclosure, I haven't read it. But just like reacting, it feels like what we all expect from a cloud service. I'm like, how dare you suggest that maybe your session should be like a cloud service where you have data sync across your sessions? Welcome to what Google Drive and OneDrive and SharePoint and OneDropbox and all of those things have been
Adam Jacob: Yeah, yeah.
Sarah Cooley: doing with your data forever. Crazy that you would treat your session like it's data. Who know what I mean? Like, I
Nick: Mm-hmm.
Sarah Cooley: don't know. It feels
Adam Jacob: I do.
Sarah Cooley: like it's the obvious cloud genesis of a harness. Like it just is.
Paul Stack: I'm lucky I don't have multiple computers. I can only deal with
Adam Jacob: Yeah.
Paul Stack: one. So minus.
Sarah Cooley: Yeah, you do. You have ten IP addresses on you. Don't pretend you don't have multiple computers, sir.
Paul Stack: that's my fridge and my cooker and all of the things that people can take down as hackers outside. But yeah,
Adam Jacob: Yeah.
Paul Stack: everything is like, even when I have travel laptop,
it's like thin client, thin I don't need to share anything between them. I refuse to share anything between them. absolutely.
Adam Jacob: Yeah, I I think it's interesting, I you're not wrong. And I and I feel like the remixing of how those layers are seen and what the user experience of them and how we think about them, that to me is where it's interesting right now. So like, you know, if you had an you know, like we how to do source control. And so there's this like reductive argument that's like, so therefore we should never build source control again because, you know, get and that's true for the last 20 years. But right now I'm like, ooh, but if I got all these agents running around and they're writing all the code and humans aren't really thinking about it, is this actually what I want? And why is this user experience still my user experience? And why am I still stuck in this shape? And so yeah, it is just data synchronization and it is just the normal cloud move. And could it get weirder? And, you know, what if it was weirder? Weirder might be better.
Sarah Cooley: This is actually a thing that we are struggling with so hard. So I work in AI safety right now, right? And we are struggling so hard with what it means to secure AI memory because that context window is both like data, people treat data like it's inert. And when I go to tech safety conferences, everybody's talking about how you give read-only access to your data to agents so it can't mess up your data. But every time stuff from your data plane enters the context window for your model, it changes its behavior. So it's both a data plane and a control plane. So, that session information is uniquely interesting because it's both source control and also user data. And by the way,
Adam Jacob: Yes.
Sarah Cooley: people, I'm sure you like this is the Microsoft Hat speaking, not the this is my personal agent. People put all sorts of things. you give somebody a chat prompt and they put everything in there. So you can't treat it like it's not PII. It's PII, it's like deeply sensitive customer data. We treat sessions like we Microsoft, Microsoft Hat, treat The things in your context window like sensitive customer content because it is. So it lives in this weird not source, not data place that I think is gonna be a real struggle from a security and safety standpoint. But you're absolutely right. It is like, I'm not saying it's not gonna get weird. It's gonna get real weird, but it's still like you can hear echoes from other things.
Adam Jacob: For sure. For sure you can. And the echoes are loud. okay, let's talk about the AWS emulator. So AWS launched an emulator, finally, for mo for a ton of their cloud services. And the storyline here is is that essentially they built it all with agents whose job was to go scour the active services with access to the internal code and then build the emulator up. And now they've launched the emulator. They're gonna like, I'm sure they're gonna officially launch it at reInvent or whatever. and great post on all things distributed, which is Werner Vogel's blog from like the guy that was like Werner's intern, who is the person who like put together the agentic system that wrote this thing. it's a fun story about sort of using agents to sort of build up the emulator and sort of how to think about that. How to think about that problem. and you know, the commit history, the issues that the agents filed to go build it, like all of that
Sarah Cooley: Okay.
Adam Jacob: stuff is all done in public, which I think is very cool. So A, I'm just I'm pleased that there's an emulator because the local stacks of the world made my life harder than I wanted them to for too long. and B I feel like this is the kind of thing you can do now for sure. That before was too much work and too much effort. And you'd have thought of it as an open source project. They're very clear that it's not. it is open source. It's under Creative Commons, which is a weird license to choose for source code, by the way. But but also they're not taking pull requests because they're like the agents do that. So, you know, let us know if there's a problem, but we're not we're not writing it. Open for issues, which is which is also our policy at Swamp. so Paul, how you feeling about the AWS emulator?
Paul Stack: Actually pretty good. It's totally honest with you. It's probably one of the most like requested features that AWS have filed for years. Like, you know, sure. You have local stack, have many stack, have flokey, have like emulators everywhere at this moment in time. One of the things that like has happened with them in that ecosystem specifically, I had this in my time with Terraform and Pulumi. All of those emulators massively languished behind like the actual product surface itself. And what they're trying to do here is they're trying to make that that it's not the case. you know, that's the fact that the same teams are going to be pushing, like using their agents to push code into the emulator itself means it's going to be relatively as much as it can be up to date, which is like a huge win. I think this is going to be a massive thing at reInvent. I really do. Like I already know a bunch of builders and a bunch of like AWS heroes who are just like thrilled with this and over the moon by it. you know, I think fair play. Microsoft or Amazon missed the boat for like a long period of time on this. And like, finally they've realized that this is something that like they have to be able to get on top of. really do. I want the same way for Azure. Just saying. Sarah.
Adam Jacob: Right? Come on, Microsoft.
Sarah Cooley: Yep, yep. What are you gonna do?
Nick: The well says no bearing on Microsoft or AWS, but I'm bullish on neo clouds because what you don't need in a neo cloud or someone who's optimizing for the agent apocalypse that is upon us is a fucking emulator for, you know, their platforms. What they do is just get apps deployed on them and
run them, hopefully safely without deleting your database. and yeah, I think it's a it's it's it's like a unfortunate reality that the service landscape of something like AWS is so complex that what you wanna do instead of like just deploying infrastructure to it, you wanna think about deploying it to an emulator first is kind of insane. and so anyway, it's like sad for complexity, yay for AWS, sad for the com consumer. And hopefully won't be required over the fullness of time.
Paul Stack: Yeah.
Sarah Cooley: Yeah.
Paul Stack: mean, the trouble here is, that there's just so much people, so many people have just invested such a huge level of infrastructure into the major
Nick: I
Paul Stack: cloud providers. like, finally, finally they can actually test it, right? I mean, in the age of like where we're going.
Nick: I I I know. I know. But also like building out a network shouldn't be seventeen hundred components to do so, correctly. And so like
Paul Stack: Absolutely. You're definitely not going to find any argument with me that the over complexity of how people put stuff in the ecosystem. We've played with XE, we've played with all sorts of sandbox and technologies recently. We've like DigitalOcean, we've been on Railway, we've been on GCP. Each of them have different levels of feature sets and you can see the progressing level of complexity in each one as you go in there.
Sarah Cooley: Yeah. This is a deep yes.
Paul Stack: The parent of all complexity is AWS, because of how many services
Sarah Cooley: Yeah.
Paul Stack: it actually does. But at the same time, I think I've only ever used maybe 10 % of the entire AWS surface area. I don't use a bunch of the stuff on the outside.
Sarah Cooley: Deep, yes, and anything that helps people do evaluation seems like a good thing right now, frankly. second, yeah, working in virtualization, the num the amount of nested virtualization out there right now, because every time there's a new persona who has a security boundary, they add a new VM to the stack and they're like, look, bam, security boundary. And it doesn't matter that there's like the physical hardware, the cloud, like the cloud VMs, the virtualized cloud fabric. Then on top of that, a VM surface like service that's giving you IaaS VMs. Oftentimes there will be a service running in the IaaS like style VMs. And then you have somebody who's like, but I own security in my business, therefore I need to add a new VM on top of that. the amount of nesting that happens in virtualization, because there are lots of different humans with their own like that they that are paid for security. And the easiest way to do that is to build build a new sandbox. you just wind up with layers and layers of it's so easy for me to imagine why that complexity happens. unless you own your own fabric. That complexity, I think it's almost inevitable every time you add a new person to the frame, like to the stack. Anyway.
Adam Jacob: Yeah. I think this is just in hot take land. I'm I think the return to raw compute and running systems on it is upon us. And like, you know, Paul was talking about like the various providers we've run and the different layers of that stack and there's a bunch of things. And I think like I think we've trained kind of a generation to really understand how to do this kind of work. through those abstractions. And if you just took an agent right this second, and what you said was, I got some pooters and I want to deploy this workload across these computers and I'd like to load balance them. And I would like to do X and Y like it's gonna do it. and and the amount of, you know, the amount of struggle that has gone into the systems that we've put in place like Kubernetes and those sorts of things in order to make the operational semantics of that simple. the truth is it's as complex as it is because of all that nested virtualization, because of all those nested abstractions, because of all of those layers we've put in place for all those different rules, none of which I think we need anymore. because so much of that difficulty gets gets pushed under the hood now in in agent land. And like we're not quite there yet.
Nick: I yearn for the day.
Adam Jacob: As an industry, we haven't quite come to that conclusion globally. I'm not sure we ever will because I might just be old and be like, wasn't it better when the server you just had servers? And I've been shaking
Nick: but
Adam Jacob: my anti-Kubernetes stick from the jump. So like it and nobody Yeah. And I and I can promise you that no one cared
Nick: But a couple of servers and a couple of data centers, like how is that not a little romantic, you know?
Adam Jacob: that I hated Kubernetes. You know what I mean? I made not a dent in the industry. So, you know, like, but I I look at this and that's what I think. I'm like, I'm glad there's an emulator. I've needed the emulator because we've had to support those APIs. It's good for everybody. All of that. And boy, it just makes me want servers again. It just
Nick: Yeah.
Adam Jacob: makes me want computer in order.
Paul Stack: And then we just whack in an emulator on the server so that the agent can actually deal with it.
Nick: If you
Adam Jacob: I got an emulator, it's called Linux. I got one.
Nick: don't email your
Adam Jacob: I got one for ya. I'll just do it right now. You want me to emulate Linux for you?
Paul Stack: The day we move to our own data center is the day I'm building Keeb and Emulator.
Adam Jacob: I mean, I know what the emulator will do. Okay. let us let us let us talk about outages. It's outage time. we've reached the part of the conversation where we talk about outages. Microsoft, the Outlook Microsoft 365 outage seeing encouraging signs of being restored. I think mostly is back, but still seeing some degradation. 24 plus hours on the far side, struggly struggle bus response in terms of like what's happening, visibility into how we were gonna use it. Like those things, that's tough.
You know, all the operational love in the world. No question, this
Sarah Cooley: Yeah.
Adam Jacob: must have been very hard. It must have been very complex. It must have had cascading failures. Like, you know, all that stuff's gonna be there. I can't wait to read the the write-up about it. and Once again, you're back to this moment where that centralization was so necessary. I remember running Outlook servers for companies of thousands of people. And like I was happy to hand all that stuff over to Microsoft, or I was happy to hand it off to Google. I don't know that I would be now though. Like I I'm back at this moment where it's like suddenly it it doesn't sound so crazy to me anymore to be like, well, I could have just owned my availability a different way, you know? And not that I wouldn't have had my own outages or whatever, but at least it would have been my at least it would have been my outage. and as we see these sort of increasing, you know, GitHub's fragility, Outlook's fragility, railway's long outage, you know, like we s we keep seeing these pile up. And it just makes you wonder, if we're gonna start rethinking the boundary, makes me wonder if we're gonna start rethinking that boundary in a way that's different than we had before.
Sarah Cooley: Who knows? Anything's possible. I am really excited about the return to primitives and relitigating some of those old layers of stack that might not make sense anymore. And I have no idea at what layer that happens. I promise
Adam Jacob: Totally.
Sarah Cooley: you, ninety-nine percent of humanity doesn't want to manage their own mail server. Like they don't even want to like look at the status report on their uptime. But for the rest of us, you know.
Nick: Very much.
Adam Jacob: Yeah, but I'm not sure you but I'm not sure you have to. that's the part that's weird. for sure my mom doesn't want to. You know what I mean?
Sarah Cooley: Yeah, but what about the dust orb in your data center, right?
Adam Jacob: Yeah. Sure. And like it was a like when somebody hit the off switch in a data center, that was annoying. The like emergency power off switch, that was a problem. And I mean, it didn't take me a day to restore it. You know, I walked back in, I turned it on, mail cued on the far end, no biggie. You know? But when I'm running Outlook, when I'm Microsoft three sixty five, it turns out that all that mail queuing up for you across the internet, that's a lot of mail.
Sarah Cooley: Yeah.
Nick: Causes
Adam Jacob: And the longer the outage
Nick: a lot of problems.
Adam Jacob: lingers, the more mail queues up, the back
Sarah Cooley: Yeah.
Adam Jacob: pressure of that whole system, that's bad. That's tough. And I don't know. I don't know.
Sarah Cooley: Yeah, saying this as a
Paul Stack: Again.
Sarah Cooley: human on the internet, not as a Microsoft employee. I really hope everyone enjoyed their snow day because it really
Adam Jacob: Totally.
Sarah Cooley: felt like the internet had a snow day. Like everybody with important
Adam Jacob: Totally true.
Sarah Cooley: communication, like we have so many ways of communicating today that like, let's be real, Outlook being down just meant that your manager can't easily like everybody just had like a collective societal excuse to have a snow day.
Nick: Ha ha
Adam Jacob: Yeah, yeah.
Sarah Cooley: And I think that nothing critic well, like when I say nothing critical, like I didn't see stories about like, hospitals couldn't do core jobs, you know what mean? Like it just really felt
Adam Jacob: No. No, no, no.
Sarah Cooley: like the internet had a snow day and I love that for everyone. I'm sorry
Adam Jacob: Mm-hmm.
Sarah Cooley: that I am
Paul Stack: Bye.
Sarah Cooley: at the company that caused people to probably lose money, but you know.
Adam Jacob: look, I nothing, nothing,
Paul Stack: Again, the internet was on fire.
Adam Jacob: nothing but love for the actual humans who had to deal with that and for
Sarah Cooley: yeah.
Adam Jacob: the technical complexity of that problem, but
Nick: I'm a like
Paul Stack: I get.
Nick: a infamous hater of GitHub on this podcast a lot. and it's so funny how different I feel about this outage compared to GitHub being down on days that end with Y, aka every day. and and like I think it's because I use one and not the other. that's probably why I care so much. I was like in really introspecting. and also I I just have a my feeling is that when you're down for 24 hours for something as critical as Office 365, like some real shit must have happened. You know? This isn't like someone didn't scale like plan to scale properly or, you know, shoddy infrastructure continues to be shoddy or whatever. This is like This is the realest of the real infrastructure that's really having a problem. And so yeah, I think that that also changes my my my relationship to it, for sure.
Paul Stack: The internet was on fire again with this one. I did see somebody who took the brand Office 365 and made it Office 364. Like the internet
Nick: Ha ha
Sarah Cooley: Yeah.
Adam Jacob: Yeah, that one hurts.
Paul Stack: is just absolutely brutal. you know, we're in, we're in this age where shit
Adam Jacob: Yeah, it wasn't reaching Jensen levels.
Paul Stack: posting is like so encouraged. And it's like, I, know at some point, you know, I'm going to be part of this and I'm going to have an outage, which I'm going to like feel shit about and just, you know, have to deal with.
Nick: Yeah, our day will come, for sure.
Adam Jacob: Our day will
Paul Stack: Exactly.
Adam Jacob: come for sure.
Paul Stack: 100%. it's just, especially when we've
Adam Jacob: For sure.
Paul Stack: sat and watched other people and you can see some of the memes coming through. But I'm kinda like, I'm excited
Adam Jacob: Talked about it on a podcast like Muppets. We're all doomed. We're signing our death warrants for sure.
Paul Stack: to see what the memes will be about it. honestly, so cause they'll be fucking brilliant. brilliant.
Brilliant. I will be so happy at that. My kid says I'm bald. So
Adam Jacob: Yeah, it'll probably have something to do with how bald we all are. I think yeah.
Nick: That's right.
Paul Stack: a normal internet person is not going to hurt my feelings by telling me I'm bald. yeah.
Adam Jacob: Yeah. Okay. let's talk about the other breaking story, which is the FAA has shut down all the flights nationwide ground stop, which is awful. Thousands of flights delayed, canceled, people not leaving. I think nationwide ground stop means flights in the air direct themselves to the nearest airport and land, right? So, like
Paul Stack: Yep. Yep.
Adam Jacob: if you're in the air, if you were like flying cross country. and you were heading to San Francisco and you're near Chicago, they're like, landing in Chicago, so it's gonna be brutal. the reports
Nick: By the way, the last time this happened was nine eleven. So
Adam Jacob: Yes. And Mullen's been very clear that it they believe it's not a state actor, like it's a telecommunications they call it a major telecommunications outage. but we don't know what it is or why, but they they have been clear that they feel like it there is no known threat, but there's also no known timetable for resolution. So yeah, if you're on a plane, you're stuck. and we're so sorry. hopefully you get home before or wherever you're going before. you hear this podcast on Monday.
Paul Stack: I mean, like there was a post that went out yesterday by the FAA that they were rolling out smart. which is
Adam Jacob: That they were rolling out what?
Paul Stack: they were rolling out a tool like their AI tool called smart, which is to assist
Adam Jacob: no.
Paul Stack: in managing air traffic control. It's $875 million worth of kit. And then the next day there's a global outage. mean, two plus two people, like, you know what I mean? Something feels like it's a bit weird. I can't have a show without a bit of a conspiracy theory and a bit of me trying to draw conclusions that are definitely not evidential at all. that was reported yesterday at 8 p.m. Pacific time, like on the 12th. So something feels a bit strange here.
Adam Jacob: Yeah. I we'll find out. but for sure it's one of those things that yeah, if it turns out that it's related to AI, yeah, that's definitely one more notch to the bubble bursting, people already don't like it.
Paul Stack: I have to go on a flight Monday to the US, so I'm really hoping it's taken care of by then, by Monday morning.
Adam Jacob: Yeah.
Nick: Me too.
Adam Jacob: a nationwide ground stop that's not deployed by Monday. I don't even know that means. yeah. We're a couple hours in already. Like the amount of money that you would lose by having
Paul Stack: I'm gonna get in a boat.
Nick: I think you guys have done that before, so you know, you'd be like reliving the past a little bit.
Adam Jacob: A little bit.
Sarah Cooley: Yeah. And that one really
Adam Jacob: Okay.
Sarah Cooley: does hurt people. th there are the ops people I really, really feel for, 'cause that one doesn't feel like a snow day. That one's like a real bad day for a lot of people. Hmm. No, I don't even want to.
Adam Jacob: Could you imagine the stress of being no, no, being on the receiving end?
Paul Stack: people are going to be fired over this. Like, absolutely. If it's actual infrastructure issue that has been caused by the rule letter or something like that, that's a rule, right?
Adam Jacob: it's gonna be bad.
Sarah Cooley: Well and and here's the thing, it's so hard because you really want the FAA to be able to modernize, but it's so critical. just balancing, the how do you do the right DevOps so that you can innovate, but also you don't ground every flight in the continental United States. There has to be a feather in between. Yeah.
Adam Jacob: Yeah, I'm cool I'm cool with floppiness. I'm good with it if it if it keeps the planes flying. I I f I feel that way about most enterprise technology. one of the things I I just hear so much whenever I go into a large enterprise is people are like, we're the worst technology stack. It's so old, everything's so bad. And I'm like, Yes, and you run the global economy. So, on the other hand it's pretty great. So one way to look at it is it's old and gnarly and you have to deploy that shit on COBOL or whatever to IBM mainframes. That is a bummer. And and it, you know, never makes a mistake, never goes down, runs the global economy. So, you know.
Nick: Alright, so back to spicy memes. you know, yesterday some someone posted on Twitter just a minute ago, yesterday was my last day at Microsoft. Today I started a brand new job at the FAA and things are going pretty well.
Paul Stack: Jesus.
Sarah Cooley: What a good week for memes. It has been such a great week for memes, if we're being
Adam Jacob: Yeah.
Sarah Cooley: yeah.
Adam Jacob: It's a it's a golden age
Nick: That was too good.
Adam Jacob: for memes. Yeah. Yeah,
Paul Stack: That's a good one.
Adam Jacob: as long as you're not Jensen's wife, it's a great week for memes.
Nick: Jesus Christ.
Adam Jacob: okay. That's it for the news this week. let's hope that it's a quiet weekend. five questions for you, Sarah. Of the stories we just covered, which one will you be thinking about later today?
Sarah Cooley: man, it's split between two of them. Honestly, the server dust room melt or dust meltdown will honestly kind of stick with me for kind of the same reason as like the FAA news. Like sometimes we just forget security at every layer. And I think often we spend a lot of time talking about well, I guess there has been like some of the power infrastructure, water infrastructure type hacks that have happened, but I still think that's like a deeply unappreciated, under-reported. portion of the tech news scene. And especially in a world where obscurity was more of a thing with, these cobalt systems that run the global everything. boy howdy, some of these stories where it's like somebody figured out that this is
the chain cascading behavior on something, keeps me up at night. So I don't know that that particular story will, but as a category, it's a thing. Yeah.
Adam Jacob: Yeah. It's gonna keep keeping you up at night. Which one of these stories do you think is just noise? And you're like, I can never hear it again.
Sarah Cooley: definitely slot manifesto. slot manifesto, don't care. I'm like, yes, people have feelings. That's nice. Have fun.
Adam Jacob: Yeah, absolutely. What's a common belief in the industry that you just think is wrong?
Sarah Cooley: man. so maybe this is a different I feel like I should pick something spicier because I feel like this is a different permutation of being a tech optimist. I really do think that it's not a bubble. I just don't. I think that there will be jobs. I really believe that humans will keep finding things to demand from our technology. And I really do think that it will result in different jobs and it might be painful. And there will be retooling and you will have to relearn how you work. And all of that will be a transition, but I don't think that it's hype or a bubble. I think the world is different now, and that's just a thing. Maybe the one that's more controversial though is I don't think everything collapses into a product engineer role, this weird PM engineer hybrid. I think it's gonna be
Adam Jacob: yeah.
Sarah Cooley: architects and PM engineer hybrids. Like I think you're either gonna be a product person or an architect. Like there are gonna be some people who are like, I care about token cost and I think they will be different than the people who care about user experiences. I think that there will be
Adam Jacob: Yeah.
Sarah Cooley: the different optimization routes on people who think at a next level of design,
Adam Jacob: Yeah. that is a good take though. all right, what's the one thing you wish you could teach everybody?
Sarah Cooley: I subscribe to the everybody is going to need to have great taste and judgment in the future and whatever the thing is that you care about. Like if you have great taste and great judgment, it's never been a better time to be a creator. There will be a place for you. And you should go figure out how to get AI to do the part that you don't like. you wouldn't know this because I joke about how I'm a PM who doesn't like public speaking, is bad at names, dates, and doesn't like the blank page problem. Like I like having written content, but I don't like writing. And I find that AI has just made the parts that I like about my job more fun and taken away the things that were really hard to overcome before. So I think it's like actually reducing a certain kind of ableism. So go figure out how to have AI do this stuff that you don't like, just try it.
Adam Jacob: Yeah.
Sarah Cooley: Just try it. even if it's a dumb chat prompt, just go try it, see what happens. it's delightful. yeah.
Adam Jacob: Yeah, I think that's amazing. What is the best and worst moment you've had working
with AI agents?
Sarah Cooley: Lately it's been discovering different ways of getting AI to help me think. So I've been playing with a lot of different tools for clarifying thought. And this is coming from somebody who hates like planner mode. I just don't like planner modes. I don't know what to say. I don't like them. I've been playing with one that Google just open source that's like, I'm gonna get this wrong, like elephant goldfish model, but like a planning agent harness thing that I've actually been having a really good time with. And it just basically goes through and plays 21 questions with you where you can type in the one-line pithy prompt that it does a better job filling out the rest of your spec. And I really like that, where it starts with the like, who's a customer? Why do you care? Why do you do this now? Like, what level of permission do you need? And then does failure analysis and then does planning and blah-blah-da-da-da. So that's been delightful. Like it's been delightful typing less, but having a LLM go through, like having my harness go through with me and do some co-thinking. In ways that are really judgment and taste nurturing, if you will. So that's been delightful. bad moment? Dude, my mom has discovered that she can put like, I think that AI has like jumped the the generational divide with learning how to use
Paul Stack: Yeah.
Sarah Cooley: menus. My mom is like all in on talking to agents, and our family chat will never be the same. Like she will like send me like Wikipedia style-esque updates about like, Hikes I am literally doing. I will be like, I'm on this hike, and my mom will send me, you are on an eight-mile hike in this state doing these things. This is your weather. I'm like, thanks, GPT. I know this is not you right now. She is, she
Adam Jacob: I love that your mom is meat proxying you. That's amazing.
Sarah Cooley: is, but she doesn't have that language. So I can't tell her that.
Adam Jacob: No. No, she just le she's she's just like, I love you, honey. Don't careful if it gets rainy. Don't get lost,
Sarah Cooley: Yeah, and now I know Yeah.
Nick: I'm being helpful.
Paul Stack: See, like in Ireland, we've just found, like people of that age have just found Facebook. So I think we're two generations away from AI, like we're in that level at this moment.
Adam Jacob: Yeah, I think my mom is she's not there yet, but I she will get there. she's like she's using it to identify things in the garden, So she's
Sarah Cooley: Exactly.
Adam Jacob: like right next door.
Sarah Cooley: Yeah. No, it's been fascinating because this is not a lady who gets along with other kinds of technology. apparently the prompt chat interface is exactly the type of thing that she can deal with. And it's just on one hand empowered her to go discover the internet as I know it. On the other hand, it has empowered her to discover the internet as I know it without any of the social accoutrement that came with doing the in-between stuff. Ha ha.
Adam Jacob: Yeah, totally. Okay. Well, that's all the news for this week. If you want to dive deeper into any of the things we just talked about, you can find all the links and the summaries over at Swamp Dash Club.com slash podcast. You can sign up to get it delivered straight to your inbox every Monday morning if you're trying to figure out how to build AI systems that are repeatable, more token efficient, that solve real problems. Swamp is here to help you build those behaviors. Visit swamp dash club dot com to learn more. Sarah, take us out. What do you want to plug?
Sarah Cooley: man, I don't even have a thing ready. Just the general actually I've really liked Swamp. It's helping me keep things it this might be offensive, but it's my new cron. I've replaced every automation thing that I would have. I'm like, look at you, sophisticated
Paul Stack: Awesome
Sarah Cooley: cron, you're helping me with drift failure problems.
Nick: New messaging
Adam Jacob: Let's go.
Nick: coming to the homepage right now. It's the new cron. I love it.
Adam Jacob: Yeah. The new headline.
Sarah Cooley: Well, like it's really hard to figure out drift. Like, I'm talking about taste and judgment, and the thing that I'm finding the hardest about like spec driven development, blah blah blah blah blah is that nothing keeps you honest to whether you have drifted off of your goal until you get to PR, but by the time you've gotten to PR, you've already done a pile of work. Like I really want it to happen sooner. So yeah, I don't know. I plug some combination of planning agents and swamp. It's been fun.
Adam Jacob: Love it. All right.
Nick: Hell yeah.
Adam Jacob: Well, it's great to have you. Thank you, Sarah.
Sarah Cooley: Yeah, thank you.
Adam Jacob: Keb, Paul, we'll we'll see you all next week.
Nick: See ya.