← All transcripts

I'm gonna miss coding Transcript, AI Summary & Key Points

Theo - t3․gg · yesterday · Science & Technology · 28:16 · EN

Watch on YouTube

AI Summary

Coding as it has been known is dead: Anthropic claims around 90% of its code is written by AI, and Theo says Claude actually writes more than 90% of his own code. The video is a reflection on Lauren's article 'Coding is Dead' (half tribute to hand-written code, half acceptance of the shift), arguing that hand-coding will survive only as a weird artisan practice, that we owe the grieving previous generation of programmers empathy, and that the real opportunity is AI rewarding curiosity. Web developers have done disproportionately well in AI development because React/TypeScript people are used to rapid change. The strongest takeaway: coding is dead, but the skills built alongside learning to code — curiosity, love of building — are not, and applying them to AI building will take people further than before.

Key Points

  • Anthropic says roughly 90% of its code is written by AI; Theo calls that an underestimate, saying Claude writes more than 90% of his own code, and concludes coding as we know it is dead.
  • Very few things still need all their code written by a human; occasionally AI gets parts wrong and you can fix them yourself or redirect it.
  • Lauren's article 'Coding is Dead' is half a tribute to the code that got her where she is and half an acceptance of where things have gone.
  • Boris (Claude Code), Lauren (React compiler), Matt Pocock (TypeScript education) and Theo all came from React and TypeScript land — a shared background of fast-changing web dev that made them well suited to AI development.
  • Thorsten's quote in the article: 'The craft of writing code will disappear. Yes, there are still Italian shoe makers around the world, but look at your feet.' Hand-coding will go the way of artisan goods.
  • 99% of code being written today is written by AI, but the code running on top of that code is at best 50/50 human-written — a debt is owed to the people who built the kernels, frameworks and languages underneath.
  • Curiosity is now rewarded more than ever: AI answers anything in public human knowledge and keeps curious 16-year-olds from burning out and switching paths, like Google did for a previous generation.
  • The teachers angry at students for using Wikipedia are the same archetype as those angry at Big Lock the game for using AI in its debug process — and Wikipedia went on to become one of the greatest information sources in history.

AI in practice

Used for

Agents

  • Run CI and Docker builds for developers and their agents 2 held 02:45

Tools & resources

1 item

Links mentioned

🔒 Full analysis locked

Unlock more videos and the full analysis

A credit unlocks one video's full analysis for good — the build steps, the tools and how each was used, the methods behind every use case. Pro opens the whole library instead, and raises how many videos you can analyse a day.

Unlock full analysis — free

Transcript

Searchable transcript of I'm gonna miss coding — Theo - t3․gg (28:16). Search for a phrase, then click its timestamp to jump straight to that moment in the video.

Captions sourced from the original video on YouTube, published by Theo - t3․gg. The video, its captions and all related intellectual property remain the property of their respective owners; AINotes claims no ownership. Provided for research, accessibility and search — see the Transcript Notice and Copyright Policy.

00:00 Boris and his team at Enthropic love to brag about how Claude writes pretty much all their code, but that's just super unrealistic. Obviously, we're writing our code by hand still. We're real engineers. We build real software. At least that's what I would have said if this was a year ago, back when we were still writing a lot of code by hand. Around this time last year, I was just starting to get a little more AI and Agentic build.

00:18 A year and 6 months ago, I was still doing huge migrations myself by hand with a little bit of AI autocomplete here and there. And obviously things have changed a lot since to the point where when Anthropic says that only 90% of their code is written by AI, I call [ __ ] because Claude writes more than 90% of my own code. The reality is that coding as we know it is dead now.

00:37 It's not kind of dead. It is. And if you are thinking otherwise, I don't actually know why you're here because most of the people who were iffy on this got over it over the last 3 to 6 months. At least the ones who hang out here. Am I saying that there is no code that is best written by hand? Honestly, at this point, kind of. Yeah, there's very very few things that need to have all of their code written by a human still.

01:00 There's occasional things where the AI gets parts wrong and you can tell it to do it right or you can go write those parts yourself, but for the most part, the AI has actually taken over the act of typing in a keyboard to make code happen. It just has its over. And that's why vibe coders like Lauren here are talking all about this. I want to make one more thing clear before we go in here, though.

01:22 Lauren's not a vibe coder. Lauren is one of the greatest engineers I've ever known. Legitimately one of my like biggest inspirations from back in the React days. The things she has done with code break my brain. And the things she's doing now with agents have broken it even more. She just put up an article about how coding is dead that is half a tribute to the code that got her where she is, half an acceptance of where things have gone.

01:45 And I want to take the opportunity to nerd out with her directly and indirectly about all of this. Thank you, Lauren, for the years of inspiration. I'm so excited to dive deeper into how our brains have just been eroded and rebuilt with AI. But in order to do that, I got to pay some bills first. We'll do a quick break for today's sponsor. If you haven't yet bumped into the limits of GitHub as a platform, I genuinely envy you because I'm hitting their rate limits every day and dealing with their super slow runners is

02:12 just driving me mad. It feels like GitHub is increasingly the biggest bottleneck of my life. That's why the dinner I just went to with Depot got me so excited. These guys have been friends of the channel for a while and they already built one of the best CI and actions alternatives to get your code checked before you drop it in production. But they've gone so much further and some of the stuff they're cooking is unbelievably cool.

02:30 If you're using Docker, you've probably already moved to Depot because these guys are the best way by far to use Docker. They cache every layer of the edge so that your devs, your CI, and your agents can all get their images way faster than they otherwise would. Their programmable CI layer is so much faster than actions. It's kind of hilarious. I didn't realize the actions protocol was as big of a bottleneck as it is.

02:51 Depotci is way easier to parallelize. And when I say way easier, I mean your agents can do it and they'll totally understand it. But what I'm most excited for is depot code. They're going to make their own git hosting that is a mirror of the official GitHub APIs so that you can just hammer them with requests without hitting the rate limits that have been killing me and my team.

03:09 It also runs alongside Depotci and Depot sandboxes which allows for everything to have access to the code instantaneously. If you're not already on Depot, your agents are wasting so much time. Go ask Claude how much time you can save at soy.link/depo. I I think I'll go on a rant at the end of this about how truly unique Lauren is. So stick to the end if you want to hear me just glaze her a bunch.

03:31 I legitimately think she is one of the best engineers at this point, like in the running for all time. But I want to talk about what she has shared here first. To my friends mourning the loss of their most loved activity, I feel your pain. I got into programming as a hobby. My first introductions to it being in high school and discovering the marquee tag.

03:50 Ever since that joyful discovery, I couldn't stop myself from making things, tinkering, and looking forward to the thrill of solving the next problem. I would pour over every line of code, thinking hard about how to make my program more elegant, performant, and even beautiful. I relate hard to this. I've always been personally more like practical leaning engineer where I cared more about how the thing worked than how the thing was written, but I also had some very like borderline elitist takes on these types of things.

04:20 One of the first videos on my channel was me reacting to this Brian Will video, object-oriented programming is bad. Is every point in this video correct? No, definitely not. Is the vibe of this video correct? Unbelievably, yes, this video not only was fundamental in changing how I thought about software engineering, in validating some feelings I already had, it's also a huge part of why I'm a YouTuber now.

04:46 This is the exact type of discussion that I was looking for more of on YouTube and just couldn't find to the point where I would go back to this video every few months for years. And eventually, much later on, I made my own channel and then eventually did a reaction to this video that actually performed unbelievably well if I recall. I think it might still be one of my top videos.

05:06 Oh, no, it's not quite as popular. It was one of my biggest at the time, but yeah, four years ago is wild. Look, look at that era of Theo. God damn. Crazy how much things have changed, but also kind of gone full circle. Sorry for the pause. I'm just like, like I'm getting a little sentimental about this. It Yeah, I This video changed my life. It really did.

05:24 Shout out to Brian Will for making it and all the follow-ups he did about these things and how unwilling to compromise he was. It changed my life. And I I can think back on many of those moments like the original presentation that Dan Abrammov and Ryan Florence did for React Hooks. I had just started becoming a front-end dev and was so annoyed around all the object-oriented patterns and the horrible ways to create, update, and manage state between components.

05:50 It was driving me insane. And the lack of reusable state really was driving me nuts. Like in order to have state in two components, you had to pass it from one to the other and do a bunch of chaos in order to keep them in sync. Hooks gave you a really powerful primitive that felt it. It's not true proper FP, but it felt a lot more like it, a lot more pure, so to speak.

06:10 And it just made it so much easier to gro and understand what the code was doing. I loved hooks. I loved what they enabled in React and how it made me a big nerd about frontend and composition and like different ways of architecting applications that eventually led to what became the T3 stack and the relationship between the back end and the front end.

06:29 And that was such a fun era. It was an era that I loved so much that I I made videos about it constantly. I was so hyped to go talk about the cool new things and the patterns that I was seeing and enjoying that I couldn't get it all out of my system just talking to my friends around me. And I made the YouTube channel so my roommate wouldn't kill me because I needed another place to just get this out of my system.

06:49 And now it's like trippy going back through my old videos and looking at different code patterns and just sitting there with like two different versions of the same thing with different like source code and comparing the source and saying like this pattern has these benefits, this pattern has these benefits. It's it's nostalgic now. And as such, I can fully understand why people feel a sense of loss right now.

07:11 I'm very fortunate that my excitement is more for where things are going than where things are because all of my biggest moments weren't like I found an old pattern and fell in love with it. It was I started to understand a pattern and then something happened. I like the trajectory personally. And that's going to be one of the first pieces of advice I give here.

07:32 Learn to love things moving, not where things are. It's kind of one of those like journey is better than the destination things, but it it's deeper than that. It's like learning to love the experience of things changing around you and knowing that change will almost always lead to better, even if it doesn't initially. Most people struggle a lot with this and the amount of change going on right now is nuts.

07:56 I think that's the biggest thing. I think it's also the reason that there are so many web devs that have done particularly well in this new AI dev world. Do y'all know what Boris the creator of Cloud Code? Lauren the creator of Pstack and all of this cursor and Grockbot stuff, Matt PCO, the creator of the crazy Matt skills that everyone loves and talks about, and myself all have.

08:18 We have one particular thing in common. And no, it's not that we write a bunch of markdown. We all come from React and TypeScript land. Boris is part of the OG TypeScript team and is like a core React React like team member and has helped a lot with the web dev world for a decade now. Lauren was one of the lead engineers designing the React compiler.

08:40 She wrote a I think the majority of the code in compiler. It was like mostly her and Joe. Matt PCO is the greatest TypeScript educator to ever live. He understands TS better than a lot of like the TypeScript team members do. And then me, the JavaScript and React [ __ ] poster that somehow helped the Nex.js spec get better. I guess it is what it is. A lot of people are mad at me for liking Nex so much.

09:03 I haven't used Next in a while if it makes you feel any better. Regardless, we all came from WebDev. And a reason I think this matters is we all got used to things changing really fast. There were so many memes back in the day of how WebDev changes frameworks more than it like piles fixes for their sites. And I get it. Let's see off the top of my head how many JavaScript frameworks I can name for fun.

09:23 Mood tools jQuery I forgot I'll put there knockout is what I was thinking of. Knockoutjs Ember Angular React. Do AngularJS and Angular count as different. I think they should considering the pain a lot of us went through for that. Yeah. Elm, Pact, and then like there's the the modern era where there's just there's so many like quick spelt solid Marco.

09:50 I guess Marco should be earlier. It's older. What am I missing? That's make me feel stupid. Oh, Vue. Duh. View. Astro. Astro's on the line. I'm I'm mostly thinking things that have JS that run in the browser here. I I'm going to remove Astro for that reason. What else? I'm looking at chat and the only others that I forgot that I think should count are lit and uh uh HTMX I think actually does belong.

10:17 I I'm specifically talking about front-end JavaScript frameworks. So I see a lot of people saying like Nex.js and Nux and all these other things. Those aren't clientJS frameworks. Those are server side tools. And like it's funny, I can relate to this more than ever now because people keep calling T3 code a harness and people keep calling next and like next frameworks.

10:38 Yeah, inertia should count. Yeah, I guess inertia kind of counts. Regardless, I I am happy with this set. I am proud of myself for only forgetting three that like are relevant enough to be in this list. Yeah, what an era. I I just saw people talking about how they are learning to code because of AI in my comment section. I am sure I lost all of y'all and I'm sorry, but this video isn't really for y'all.

11:00 This video is for us, the people who have been programming for 10 plus years that are facing the reality of where stuff has gone. Back to what Potato has to say here. Her next section starts with a quote from Thorston. The craft of writing code will disappear. Yes, there are still Italian shoe makers around the world, but look at your feet. Yep, perfectly put.

11:20 That that is that's spot on. No one here is wearing shoes that were handmade by like an artisan. If you are, that's [ __ ] awesome. I think that's cool as hell. I I had one pair of actually custom shoes in my life. I had a friend who was really into design and he took some of my shoes that I had skated and destroyed and made them into some like very crazy art pieces that I felt bad wearing.

11:41 They were super [ __ ] cool. I should check in on him. I haven't heard from that friend in a while. But yeah, like that is that is where code by hand will go is going to weird artisan [ __ ] not actually used code. It just it's obviously the case. And if you haven't accepted that yet, I I honestly just have questions. Like it's it's so clear where things not just are going like they are here now.

12:05 This is no longer a it will happen. This is an it has happened. Have you caught up or not? As beneficiaries of AI, we owe everything to the people that came before us. the people who discovered, engineered, and created the knowledge and civilization that we now live in and build on top of. Just look around you. Even everyday ordinary things were brought to life by someone who is passionate about solving a problem.

12:27 Those people are now mourning the loss of the tactile feeling of solving problems with nothing more than your own hands and the knowledge built upon the shoulders of giants. This is a thing that we have lost a meaningful amount of for sure. I want ones in the chat if you can relate to this experience. It's late at night. Talking midnight, 1 2 a.m. You've been grinding on a problem for hours, if not days.

12:52 You're getting delirious from the exhaustion. You've been trying to solve this stupid [ __ ] bug, this stupid issue, this weird architectural problem, this design issue, like whatever it is, some obnoxious complex thing. And despite or arguably because of the stupidity that you're feeling in this moment, because you're so exhausted, because your eyes are blurry, you see things a tiny bit different and it clicks and you realize, "Oh [ __ ] I can just delete half of this and the problem gets way easier."

13:25 And then you do this in a crazy burst, unable to even notice the clock in the corner of your screen. And then suddenly it's 4:00 a.m. and the problem is solved. And you couldn't be prouder. and you go to bed pumped. Let's see ones in the chat if you remember those days. There we go. I miss it too. I think I miss it less than a lot of devs because I found other things that are satisfying in similar ways.

13:53 But we do need to pay tribute to the people who did this because these are the people who created the the internet. They created the kernels that we are using to boot our systems. They created the frameworks and the languages that we're building on top of. Most of the code being written today by far like 99% of the code being written today is being written by AI obviously.

14:10 So, but the code that is running on top of that code is 50/50 at best. It's leaning much more human coded. And we owe those people a debt. They do deserve empathy for where they're at. Where I draw the line is when they start actively talking [ __ ] on other devs who have been there for both. If you go after Lauren for being a vibe coder and don't even know that she built the React compiler, which is one of like the most genuinely impressive achievements of human written code in history, if you cannot appreciate the

14:44 absurd level of capability that she represented by doing that, then you're a worse engineer than the vibe coder you're complaining about. But at the same time, we should be empathetic to the people who who are grieving the fact that coding as they know it is dead. Let's go back to the article. Coding is dead, but yet coding still lives on in the weights of the models that we now use, the frameworks we build with, and the programming languages that we write with.

15:06 We should not shame the people who mourn because we owe everything to them. And yet, while others mourn, we can also rejoice. Personally, as a self-taught programmer, Lauren is thrilled at the thought of more people discovering the joy of building things. While it might be tempting to think that automation of coding is the end of things, she thinks it's a new beginning where a new generation of programmers using natural language to express their intent and goals will build things faster and at a higher quality than we

15:31 could ever produce by hand. I'm going to push back a bit on this because I don't think she went far enough. Building is a type of curiosity, and what I'm excited about more is curiosity and how it's rewarded. Historically, curiosity has been limited by who's around you. There were few things that curiosity could bring you if you didn't have enough smart people around to to help you there.

15:55 If you were super curious about how the Linux kernel worked, you could sit there and stare at the code. You could read through the mailing list. You could read whatever documentation exists. You could watch presentations. You could do lots of things. But if you're a 16-year-old in high school that's just fascinated by Linux, you're going to be very limited to how much you can learn and also who around you is going to encourage you to keep going down that path.

16:20 And it takes so much curiosity to push through that. And I think it ends up killing a lot of curiosity in the end. AI helps encourage that. I think naturally curious people have an unimaginable advantage here more than like ever before because you have a machine that was built to answer your curiosities to encourage you to go deeper to never say sorry I don't know the answer to that to go find it for you anything that exists in public human knowledge now any code that is on the internet you can ask the free tier of

16:52 chat GBT about and get a useful answer from it that is insane that is so cool for curious people and they will become builders, they will become thinkers, they'll become educators, they'll become the future. And AI keeps them from burning out when they're 16 and going down a different path instead. It's basically like the new Google. This is a really good analogy actually, the the magic of Google.

17:10 And I remember like I don't remember the first time I used Google cuz I was really young at the time, but I remember having like the constant questions a kid asked their parents like why why why is the sky blue? Why did it get that way? Why is the sun like that? Like just those types of questions. Google gave them a tool to answer a lot of them. And I remember like asking my parents to Google things for me when I was a young kid.

17:31 AI is that but so much further. And at the same time, it introduces the same archetype of people. Like I remember in sixth grade having my teacher getting really mad at me for googling to find sources even though I like clicked on Wikipedia. I didn't use Wikipedia as a source. I went through the sources on Wikipedia in order to find good stuff. and she was initially impressed with the quality of the thing I wrote as aly like a sixth grader and then she got upset thinking I copied it all from Wikipedia.

18:00 I like no I didn't I didn't cite Wikipedia. Wikipedia was a portal to the things I wanted to learn about. And that that particular sixth grade teacher was so [ __ ] rude to me which is crazy cuz like my last three prior were very much encouraging my curiosity. She was mad at me for doing curiosity in a way she didn't like. And now we have the same thing with AI.

18:19 That's what it is. Same teachers who were mad at you for using Wikipedia to find the information you wanted as sources for your papers are the ones who are flipping a [ __ ] [ __ ] about Big Lock the game using AI in its debug process to fix some small things before it went out. Exact same type of person. And you know what? Wikipedia has continued to become one of the greatest human accomplishments in history.

18:43 One of the greatest sources of information of all [ __ ] time. and everybody who was against it is just has not moved a lot since. Let's just put it that way. I love this section from Lauren as well. It might not seem like it's possible now, but she believes it will be for AI to produce code better than any human could have by hand before, even if they don't know how to code.

19:04 Builders using AI will produce things we could never have done before. She quotes Alex here. You got to think of this like a weird video game. In theory, there's a series of input tokens that's going to give you the code that you want as an output that doesn't need editing. It's entirely possible. You just need to figure out that series of input tokens.

19:21 Don't give up and give into hand editing. You can do it. I like this framing a lot. It's almost like a speedrunning technique. Like you could just go through the part the normal way or you can try a shitload of weird stuff and if you get it right once then you never have to think about the thing again. The more you can automate things with AI, the more you are freed to do more things, to try more things, to experiment with more ideas.

19:42 All of the crazy projects I had been thinking about for over a decade, most of them are built now, and I'm trying to come up with more crazier ones, like an operating system or a browser. It's crazy that you can just do those things, but you can. As Lauren says here, the abundance of software will be glorious. If anything, she feels more love for programming than she ever did before, and I'm very much with her there.

20:02 What used to limit her with her own ability, which remember one of the best engineers alive, she's now able to code into existence if she can figure out the right incantations, the right prompts and context in order to drive an agent towards the vision that she sees so clearly in her head. So, while some might say that they're quote excited to see what you build with empty feelings, Lauren wants to believe that many of us are truly excited at what people who've never experienced the joy of building can do.

20:26 And I am totally with her there. Are the slop PRs from kids who don't know anything about how RAM is managed annoying? Sure, but are the unbelievable novel new ideas I'm seeing from high schoolers rethinking how videos are edited, rethinking how animations are designed, rethinking how games are played, rethinking how frameworks are deployed, rethinking everything.

20:45 That is so cool. There is a unique advantage to not knowing how everything already works because it'll give you the opportunity to try things no one else would have tried. And I'm so excited those people can now go do crazy [ __ ] As I mentioned before, Lauren's a legendary engineer. She came up through the elixir world, funny enough, and since then has become very relevant engineer in the space.

21:08 I have historically loved her for her combination of the like depth of her technical understanding, her willingness to the sledgehammer effect is what I've always said, like her willingness to like throw things out when it makes sense to and not when it doesn't. But also, this is a special one, her [ __ ] posting abilities. We're in a blue country again, so I could say a thing that I haven't been able to do for a while.

21:30 Lauren's life is harder because she's a woman engineer. She will be taken less seriously because of that. Period. Point blank. That's just reality. If her and I were the exact same level of capabilities of engineering, I would be seen as a better engineer than her. Thankfully, she is so far ahead of me that everyone here agrees she's a better engineer than me.

21:47 I firmly believe people can only take up so much space in the minds of something like Twitter and like social media and like the public mind. You're only allowed to take up so much space and the space you take up is limited to like the set of things. Like I cannot tell you how many times people have told me they are surprised that I had a real engineering job or that I can skateboard or that I know things about music because in their head Theo's the YouTuber who kind of vibe codes and that's as much space as I'm

22:19 allowed to take up. In order for me to be better in their head, I'd have to take up more space than I've been given. And that's fine. That's just how reality works. There are a few things that result in you taking up less space that are pretty consistent. One of those is being labeled as a vibe coder. I learned this quickly. If you become labeled as a vibe coder, engineers will take you less seriously and you will take up less space in their brains.

22:43 There are reasons that is good and there are reasons that is bad. But it is reality. If you are seen as a vibe coder, you will be taken less seriously. Period. There's another thing that will hurt there as well. Being a woman engineer, as soon as you are any combo of two of these things, you're going to have things about you get doubted. If you are an engineer that has been around for a while, it has a lot of depth, but you're also a vibe coder.

23:08 People are going to start questioning if you actually know what you're doing with engineering or if you're lucky, they'll question if you know what you're doing with AI. You don't get to do both. You are seen as one or the other. And if you're seen as one, the way people perceive you as the other will be tainted inherently. That is reality. And I watched this happen.

23:24 My example is a bit sillier. My example is as a YouTuber. When I was blowing up on YouTube, I was seen as the open- source dev that cares a lot about stacks, frameworks, React, webdev stuff that happens to be a YouTuber. And I noticed when I hit around 100k subs, it almost felt like a switch flipped and the world no longer saw me as a developer who YouTubes.

23:45 They saw me as a YouTuber who pretends to code. And I felt that transition. It was like night and day and happened in the course of like a week or two. It was all of a sudden the world saw me as a YouTuber who pretends to code, not a programmer who happens to YouTube. And I've seen these things happen to a lot of people and to be frank disproportionately to women.

24:05 So the fear I had with Lauren is that even preai, she was already a unique set of things that felt like it would be in danger because she was a woman engineer who had some of the funniest posts I'd ever seen in my life as well as being an incredibly talented and capable engineer. She was all three at the time. She was very small. She had like a few thousand followers at most.

24:27 Nobody saw her [ __ ] host but me. And I would do my best to boost them cuz they were so [ __ ] funny. I've always considered Lauren to be one of the funniest and smartest people in my engineering spaces by far. So when she started to become a vibe coder and also alongside that Twitter influencer, best I can put it. Don't mean that offensively, just reality.

24:46 Oh wait, she works at there. So I have to say exin influencer otherwise she might get in trouble. as she became a vibe coder and an ex influencer. I was really scared about how the like blob of what she is would shift because as you shift over to being seen as this or as this, the rest is going to start being questioned. Like if she is perceived as this here as a vibe coder influencer who happens to be a woman, no one will ever take her engineering seriously and nobody will actually find her funny.

25:13 They'll just see her as an influencer. What ended up happening and this happened for a while was this. She was seen as a surprisingly good engineer who had really good takes with like Pstack and merging insane amounts of PRs. That was the best follow you could have on Twitter if you're into AI because she knew her [ __ ] so well and was like showing us what the future looked like.

25:31 And also as a woman and this to me was like bravo, we did it. It sucks that we lost the world seeing how [ __ ] hilarious she is. But if that is the cost, to not have people claim that she's actually a man pretending to be a woman or that she's not a real engineer or that she has no idea how AI works, for her to be seen this way, to take up this much space was [ __ ] awesome.

25:51 And then one particular individual showed up and decided to give Lauren the win and extend to include this as well. Do you all know who this kind, generous individual was? Chad already figured it out. Tibo. Tibo's decision to go to war with Lauren is one of the greatest gifts anyone has ever given me specifically because I was so sad that the Lauren I knew and loved and appreciated, the Lauren who was this unique blend of these three things would not be noticed by the world and that her [ __ ] posting side would be

26:27 overtaken by all these other things. I had this conversation with a handful of my friends, like a sit down chat about the state of like AI conversations in media and like had a moment where I talked about how sad I was that Lauren's [ __ ] posting would never be appreciated because it was one of the coolest things about her and is genuinely really unique and hilarious.

26:48 But thanks to our friend Tibo, Lauren is one of the first engineers to have it all. She is seen as what she is, a legendary [ __ ] poster who is an incredibly capable engineer, vibe coding an AI dev extraordinaire, an influencer on X that is one of the best follows you can do and she just so happens to be a woman. That is [ __ ] awesome. Never has somebody taken up this much space in this way where if you ask somebody from tech Twitter, who is Lauren?

27:16 There is a good chance they touch on all of these things and that is [ __ ] awesome. So, shout out to Tibo for giving Lauren the complete Infinity Gauntlet, giving her the last gem she needed to complete this mission. Truly legendary. Lauren will go down in the history books. I'm so [ __ ] proud of her. I don't even know if that belongs in the video, but I don't really care.

27:36 I just wanted to go on that rant for y'all cuz I have feelings. Thank you, Lauren, for proving all of my mental models for how the world works wrong. I did not think what she is doing was possible, and it is. So, yeah. Lauren has continued to disprove my own strongly held beliefs and understandings of the universe, and I hope this video helps y'all do that a little bit as well.

27:55 Coding is dead, but the skills we built alongside learning to code are not. And if you can find ways to apply that excitement around building and learning and that curiosity that got us all here to building with AI, it will take you even cooler and better places. Be more creative, push these things further, and see where it takes you. I have a feeling you'll be really surprised. But until next time, peace nerds.