Section Insights
The Evolution of Coding
How has the role of AI changed coding practices?
The speaker reflects on the transition from manual coding to AI-assisted coding, emphasizing that traditional coding is becoming obsolete. They express skepticism about claims that AI writes a significant portion of code, asserting that their own experience shows a much higher reliance on AI tools.
- Traditional coding practices are becoming outdated.
- AI tools are increasingly capable of writing code.
- Skepticism exists regarding the extent of AI's role in coding.
The Impact of React Hooks
What are the benefits of using React Hooks?
The speaker shares their positive experience with React Hooks, highlighting how they simplify state management and enhance code readability. Hooks provide a more functional programming approach, making it easier to understand and architect applications.
- React Hooks simplify state management in components.
- They promote a more functional programming style.
- Hooks enhance code readability and understanding.
The Future of Coding
What does the future hold for traditional coding?
The speaker predicts that traditional hand-coded software will become rare, likening it to artisan crafts. They suggest that coding will evolve into a more abstract and automated process, questioning the relevance of manual coding in the future.
- Traditional coding may become an artisan-like craft.
- The future of coding is likely to be more automated.
- Acceptance of this change is crucial for adaptation.
AI as a Tool for Learning
How does AI influence learning and creativity in young people?
The speaker compares AI to Google, suggesting it serves as a powerful tool for young learners. AI can help answer questions and foster creativity, preventing burnout and guiding them towards productive paths.
- AI acts as a modern tool for learning and exploration.
- It can help prevent burnout in young learners.
- AI encourages creativity and problem-solving.
Perceptions of Coders
How do labels affect the perception of coders in the industry?
The speaker discusses the stigma associated with being labeled a 'vibe coder,' explaining that such labels can diminish credibility. They highlight the additional challenges faced by women in engineering, emphasizing the need for recognition of their skills.
- Labels can negatively impact a coder's credibility.
- Women in engineering face unique challenges and biases.
- Recognition of skills is essential for all engineers.
Transcript
0:00 Boris and his team at Anthropic 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 pilled.
0:19 A year and six 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 bullshit, because Claude writes more than 90% of my own code. The reality is that coding as we know it is dead now. It's not kind of dead.
0:39 It is. And if you were 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 three to six 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.
1:01 Still, 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. It's over. And that's why vibe coders like Lauren here are talking all about this. Want to make one more thing clear before we go in here, though.
1: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, and.
1:46 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 just driving me mad.
2:14 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. If you're using Docker, you've probably already moved to Depot because these guys are the best way by far to use Docker.
2:37 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. Depot CI is way easier to parallelize. And when I say way easier, I mean your agents can do it and they'll totally understand it.
2:57 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. And it also runs alongside Depot CI 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.
3:20 Go ask Claude how much time you can save at sodev Link Depot. 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. 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.
3:44 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. 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 pore over every line of code thinking hard about how to make my program more elegant, performant and even beautiful. I relate real 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.
4:15 But I also had some very borderline elitist takes on these types of things. 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 and validating some feelings I already had, it's also a huge part of why I'm a youtuber now.
4:47 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. Oh no, it's not quite as popular.
5:08 It was one of my biggest at the time. But yeah, four years ago is wild. Look, look at that era of Theo. Goddamn 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. 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.
5:30 It changed my life and I. I can think back on many of those moments like the original presentation that Dan Abramov 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. 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.
6:03 Hooks gave you a really powerful primitive that felt it's not true proper fp, but it felt a lot more like it, a lot more pure so to speak. And it just made it so much easier to grok 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 front end 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.
6:29 And that was such a fun era. It was an era that I loved so much that 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.
6:51 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 source code and comparing the source and saying, like, this pattern has these benefits. This pattern is these benefits. It's. It's nostalgic now. And as such, I can fully understand why people feel a sense of loss right now. 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.
7:24 It was. I started to understand a pattern and then something happened. I like the trajectory personally, and that's gonna be one of the first pieces of advice I give here. 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.
7:52 Initially. Most people struggle a lot with this, and the amount of change going on right now is nuts. 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 cursors and Grokbot stuff. Matt Pocock, the creator of the Crazy Mat skills that everyone loves and talks about, and myself all have.
8:21 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. She wrote a I think the majority of the code in compiler it was like mostly her and Joe Matt Pocock is the greatest typescript educator to ever live.
8:49 He understands TS better than a lot of like the typescript team members do. And then me the JavaScript and React shit poster that somehow helped the next JS spec get better. I guess it is what it is. A lot of people are mad at me for liking Next so much. I haven't used Next in a while if it makes you feel any better. Regardless, we all came from web dev and a reason I think this matters is we all got used to things changing really fast.
9:12 There were so many memes back in the day of how web dev 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 mootools, jQuery I forgot I'll put there Knockout is what I was thinking of. Knockout, js, 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.
9:40 Yeah. Elm preact. Then there's the modern era where there's just so many quick, svelte, solid Marco I guess Marco should be earlier. It's older. What am I missing? It's going to make you feel stupid. Oh view Duh View Astro Astro is on the line. I'm mostly thinking things that have JS that run in the browser here. 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 htmx I think actually does belong.
10:19 I'm specifically talking about front end JavaScript frameworks. I see a lot of people saying next JS and Nuxt and all these other things. Those aren't client JS frameworks. Those are server side tools. And it's funny, I can relate to this more than ever now because you will keep calling T3 code a harness and people keep calling Next and nuxt frameworks. Yeah, inertia should count. Yeah, I guess inertia kind of counts. Regardless, I am happy with this set.
10:46 I am proud of myself for only forgetting three that are relevant enough to be in this list. Yeah, what an era. 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. 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.
11:10 Her next section starts with a quote from Thorsten. The craft of writing code will disappear. Yes, there are still Italian shoemakers around the world, but look at your feet. Yep, perfectly put. 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 fucking awesome. I think that's cool as hell. 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 fucking 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 bullshit. 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. This is no longer a it will happen.
12:07 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. 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.
12:36 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 2am You've been grinding on a problem for hours, if not days. You're getting delirious from the exhaustion. You've been trying to solve the stupid fucking bug. This stupid issue, this weird architectural problem, this design issue, like whatever it is, some obnoxious, complex thing.
13:08 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 shit, I can just delete half of this and the problem gets way easier. 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 4am and the problem is solved and you couldn't be prouder and.
13:36 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. But we do need to pay tribute to the people who did this because these are the people who created the Internet. They created the kernels that we are using to boot our systems, they created the frameworks and the languages, but that we're building on top of most of the code being written today.
14:07 BY Far like 99% of the code being written today is being written by AI, obviously so. But the code that is running on top of that code is 5050 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 shit 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 the most genuinely impressive achievements of human written code in history, if you cannot appreciate the absurd level of capability that she represented by doing that, then you're a worse engineer than the Vibe coder you're complaining about.
14:51 But at the same time we should be empathetic to the people who are grieving the fact that coding is. 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. We should not shame the people who mourn because we owe everything to them. And yet, while others mourn, we can also rejoice.
15:14 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 could ever produce by hand. I'm going to push back a bit on this because I Don't think she went far enough.
15:38 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 the who's around you. There were few things that curiosity could bring you if you didn't have enough smart people around to help you there. 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.
16:10 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. 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 ever before.
16:33 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. You can learn anything that exists in public human knowledge now. Any code that is on the Internet you can ask the free tier of ChatGPT 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.
17:02 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. And I remember like I don't remember the first time I used Google because I was really young at the time, but I remember having the constant questions a kid asks their parents, like why, why, why is the sky blue? Why did it get that way?
17:23 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 asking my parents to Google things for me when I was a young kid. 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 clicked on Wikipedia.
17:48 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 nearly like a sixth grader. And then she got upset thinking I copied it all from Wikipedia. It's like, no, I didn't. I didn't cite Wikipedia. Wikipedia was a portal to the things I wanted to learn about. And that particular Cisco teacher was so fucking rude to me.
18:09 Which is crazy because 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. That's what it is. The 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 fucking shit about Big Walk the Game. You using AI in its debug process to fix some small things before it went out.
18:37 Exact same type of person. And you know what? Wikipedia has continued to become one of the greatest human accomplishments in history, one of the greatest sources of information of all fucking time. And everybody who is 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.
19:04 Code builders using AI will produce things we could never have done before. She quotes Alex here. You gotta 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, don't give up and give in to hand editing. You can do it. I like this framing a lot.
19:27 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. 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.
19:52 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. 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.
20:17 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. 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.
20:45 Rethinking everything 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 shit. 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. I have historically loved her for her combination of the depth of her technical understanding, her willingness to the sledgehammer effect is what I've always had.
21:19 Like, her willingness to like, throw things out when it makes sense to and not when it doesn't, but also, and this is a special one, her shitposting 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. 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.
21:43 Thankfully, she is so far ahead of me that everyone here agrees she's a better engineer than me. I firmly believe people can only take up so much space in the minds of something like Twitter and like social media, in, 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.
22:14 Because in their head, Theo's the YouTuber who kind of vibe codes. And that's as much space as I'm 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.
22:38 If you become labeled as a vibe coder, engineers will take you less seriously and you will take up less space in their brains. 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.
23:04 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. 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.
23:20 Inherently, that is reality. And I watched this happen. 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 web dev, 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:46 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. So the fear I had with Lauren is that even pre AI, 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.
24:19 As well as being an incredibly talented and capable engineer, she was all three at the time. She was very small. She had a few thousand followers at most. Nobody saw her shitpost but me. And I would do my best to boost them because they were so fucking 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:47 Oh, wait, she works at there, so I have to say X influencer, otherwise she might get in trouble. As she became a vibe coder and an X 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:14 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 shit so well and was like, showing us what the future looks like. And also as a woman. And this to me was like, bravo, we did it.
25:36 It sucks that we lost the world seeing how fucking 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 fucking awesome. And then one particular individual showed up and decided to give Lauren the win and extend to include this as well.
26:03 Do y' all know who this kind, generous individual was? Chad already figured it out. Thibaut Tebow'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 shitposting side would be Overtaken by all of these other things.
26:30 I had this conversation with a handful of my friends, like a sit down chat about the state of like AI conversations and media. And like had a moment where I talked about how sad I was that Lauren's shit posting would never be appreciated because it's one of the coolest things about her and it's genuinely really unique and hilarious. But thanks to our friend Thibaut, Lauren is one of the first engineers to have it all. She is seen as what she is, a legendary shitposter who is an incredibly capable engineer, vibe coding and AI dev extraordinaire.
27:01 An influencer on X. That is one of the best followers you can do and she just so happens to be a woman. That is fucking awesome. Never has somebody taken up this much space in this way where if you ask somebody from tech Twitter who is Lauren? There is a good chance they touch on all of these things and that is fucking awesome. So shout out to Tebow for giving Lauren the complete Infinity Gauntlet, giving her the last gem she needed to complete this mission.
27:30 Truly legendary. Lauren will go down in the history books. I am so fucking proud of her. I don't even know if that belongs in the video, but I don't really care. I just wanted to go on that rant for y' all because 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.
27:52 And I hope this video helps y' all do that a little bit as well. 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 in 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.
Summary
- Traditional coding is largely replaced by AI, with the speaker claiming over 90% of their code is now AI-generated.
- The speaker reflects on their personal journey from manual coding to embracing AI tools.
- They acknowledge the emotional loss felt by developers who enjoyed the hands-on experience of coding.
- The conversation highlights Lauren, a talented engineer, and her contributions to the field, emphasizing the blend of technical skill and creativity.
- The speaker encourages embracing change and the opportunities AI presents for future innovation.
- They draw parallels between AI's role in coding and the historical impact of tools like Google on learning.
- The discussion touches on societal perceptions of women in tech and the challenges they face, particularly in being taken seriously as engineers.
- Ultimately, the speaker advocates for curiosity and creativity in leveraging AI to build new solutions and ideas.
Questions Answered
How has the role of AI changed coding practices?
The speaker reflects on the transition from manual coding to AI-assisted coding, emphasizing that traditional coding is becoming obsolete. They express skepticism about claims that AI writes a significant portion of code, asserting that their own experience shows a much higher reliance on AI tools.
What are the benefits of using React Hooks?
The speaker shares their positive experience with React Hooks, highlighting how they simplify state management and enhance code readability. Hooks provide a more functional programming approach, making it easier to understand and architect applications.
What does the future hold for traditional coding?
The speaker predicts that traditional hand-coded software will become rare, likening it to artisan crafts. They suggest that coding will evolve into a more abstract and automated process, questioning the relevance of manual coding in the future.
How does AI influence learning and creativity in young people?
The speaker compares AI to Google, suggesting it serves as a powerful tool for young learners. AI can help answer questions and foster creativity, preventing burnout and guiding them towards productive paths.
How do labels affect the perception of coders in the industry?
The speaker discusses the stigma associated with being labeled a 'vibe coder,' explaining that such labels can diminish credibility. They highlight the additional challenges faced by women in engineering, emphasizing the need for recognition of their skills.