WEBVTT
1
00:00:00.000 --> 00:00:19.000
In today's modern technological world, developers face many difficult questions, artificial intelligence, autonomous agents, JavaScript frameworks, even CSS, with so much happening so quickly, how can a developer possibly keep up?
2
00:00:19.000 --> 00:00:43.000
Simple. Just listen to the world's most important AI podcast. Two experts, countless opinions, zero hesitation. The internet is complicated. These men are not. Each week they review the latest developments in artificial intelligence and modern web development. This is Whiskey, Web, and WhatNot. The world's most important AI podcast.
3
00:00:43.000 --> 00:00:54.000
Hey, what's up, everybody? Welcome to Whiskey Web and WhatNot with your host, Robbie the Wagner and Adam Thomas, our guy, the nerd. I'm here y'all. What's up?
4
00:00:54.000 --> 00:01:06.000
Yeah, we are here live from React Miami, podcasting from the clerk booth. Thanks so much to clerk for your generous sponsorship to have us here. And who's our first guest today, Adam?
5
00:01:06.000 --> 00:01:31.000
Oh, you might know them as executive director of the React Foundation, former React Lead meta, React compiler champion, relauncher of React, conf creator of React Impact Signals, mentor, leader, speaker, photographer, strategic growth advisor. Overall, Kat, that keeps the pipelines clean, so tools and devs can flow and grow. Now working at expo is chief developer evangelist, but still continues to help react and react native remain open, sustainable and community led. This is Seth Webster, y'all.
6
00:01:31.000 --> 00:01:52.000
Yeah, I need to hire you. How's it going, Seth? It's going great. Man, I'm super excited to be here at React Miami. It's my first time both to react Miami and to Miami. So it's been amazing so far. This event is blown my mind in multiple ways, even in the first few hours.
7
00:01:52.000 --> 00:02:04.000
Yeah, it makes two of us, man. Yeah, it's a great event. They do a great job. Miami's always fun. Yeah, a little loud for me. Like every event is like, what if the music was super loud?
8
00:02:04.000 --> 00:02:11.000
You know, you get to take it up every I get out to the last conference. Yeah, that's true. Sometimes volume is your only choice. Yeah.
9
00:02:12.000 --> 00:02:24.000
All right, so we have a giant list of hot takes. I don't know if we're going to get to all of them, but I want to start with one that I feel like you'll have opinions on. All right, is React a framework?
10
00:02:24.000 --> 00:02:38.000
I thought I was done with this conversation. You know, I think, I think, you know, just depends on where you draw the fault lines, man. Like to me, React is meant to be tiny.
11
00:02:38.000 --> 00:02:51.000
Yeah, it's meant to be a library. But over time, as you know, the needs of users and developers have been surfaced more and more stuff has been added to react. And I think there's a growing feeling among the react.
12
00:02:51.000 --> 00:03:01.000
The folks that are actually still working on react is is actually, you know, getting back to that react core and react native core such that such that the library.
13
00:03:01.000 --> 00:03:17.000
The library is very thin and that it's easier to bolt things on and it's easier to use these scape hatches and so forth. So I think, I think generally speaking, and it's done what every piece of software throughout time and memorial has done, which is to grow as the needs grow.
14
00:03:17.000 --> 00:03:28.000
And I think it's a good time. It has been a good time for a while to look back at scaling that back to the core and putting more things out into the community for community management and that's something foundations looking hard at.
15
00:03:28.000 --> 00:03:43.000
One of the projects I'm most excited about this year is actually working on. I have a bunch of companies that have stepped up to sponsor stable API work for React Native, which basically means that we're going to have this API that platforms can target.
16
00:03:43.000 --> 00:03:56.000
And no longer be victims of every time we do a react native release and it's going to three months catching up, they'll be able to target a stable API and we're going to send for that API such that you can depend on it as long as you're targeting a specific version.
17
00:03:56.000 --> 00:04:08.000
So like stuff like that's like long overdue and gets us back to being a library and less of a framework, but I would say we've drifted pretty, pretty squarely into the framework space over the years.
18
00:04:08.000 --> 00:04:10.000
Yeah, so it depends, you would say.
19
00:04:10.000 --> 00:04:16.000
Yeah, I mean, they, you know, I guess I'm a little bit of a politician. So, you know, they got it.
20
00:04:16.000 --> 00:04:25.000
It was at the very end, but that's what I think I think the right thing is to be a library.
21
00:04:25.000 --> 00:04:32.000
Yes, yeah. Can you move your mic just a little further this way, like like tilt. Yeah, cool.
22
00:04:32.000 --> 00:04:35.000
Because if you're facing, I'm just trying to get as much sound as we can anyway.
23
00:04:35.000 --> 00:04:42.000
That's good. Sorry. Yeah, you're good. Yeah. What about what do you think about React server components? Was it a good idea?
24
00:04:42.000 --> 00:04:54.000
I mean, yes, I was championing that from the inside of the original code name was Flight and it was worked on by Lauren Tan and I think Dan Abramov worked on it.
25
00:04:54.000 --> 00:05:01.000
And the original, the original goal was the same as it is today, which is to give React the full stack story.
26
00:05:01.000 --> 00:05:15.000
You know, the, you know, clear indications after many years of developing spas was that there was no like canonical way to do data fetching and to do secure data fetching close to the server.
27
00:05:15.000 --> 00:05:27.000
You're always having to wire something up. You're having to do API keys and bear tokens and all this stuff to do relatively simple things that Ruby on Rails developers were like, just do this.
28
00:05:27.000 --> 00:05:40.000
You know, it's so easy. And so I think, you know, the in spirit, it was definitely a good idea. One thing that was, you know, super hard in the development of it is that meta has such bespoke web infrastructure.
29
00:05:40.000 --> 00:05:49.000
We could not use server components at meta. And so we had to find an external partner to take on the work of like integrating it into some kind of full stack.
30
00:05:49.000 --> 00:06:02.000
And that's where Verself stepped in and it did an amazing job with the first version. Of course, being a being a friend and framework, we didn't have, we don't have still probably the muscles to understand like the full stack and like the security implications.
31
00:06:02.000 --> 00:06:10.000
And so now you're seeing because of that that we have for the first time in React's history, we're vulnerable to exploits, which we weren't before.
32
00:06:10.000 --> 00:06:27.000
And so I think generally it's a good idea. I think having that story and being able to say that we can operate anywhere from the server to the client and also like, you know, removed likelihood of leaking secret keys to the web, I think is an important step forward for sure.
33
00:06:27.000 --> 00:06:44.000
I don't know that the implementation has reached, excuse me, I don't know that the current like implementation of server components has reached its max yet. I don't know where necessary or like server components prime, but I do think that the continued development there is going to only make things better.
34
00:06:44.000 --> 00:06:59.000
The biggest thing that I think is confusing for people now is like things like caching and so forth. It's like there's not a really clear and Verself trying some things, but there's not really a clear like all encompassing story for caching that that really works for everybody.
35
00:06:59.000 --> 00:07:11.000
And so I think you're going to see evolution there, but I do think it was a really good idea. And I just think it's as even though it's been out for a couple of years, it's still early days because it hasn't had that many iterations.
36
00:07:11.000 --> 00:07:28.000
Yeah, I do think on the one hand, I think it's nice to be able to use the same things on the client and the server. On the other hand, I like the separation of like, I know for sure which one I'm operating on because it's a totally different language or something for server stuff.
37
00:07:28.000 --> 00:07:43.000
Yeah, I can see arguments for both ways, but yeah, I think you know, when you think about it from like the artisan or craftsperson perspective, I think I definitely agree with you that it's like nice to have the ability to turn and tweak all the knobs.
38
00:07:43.000 --> 00:08:03.000
I think where we found that server components has been such a huge hit is a companies that you know are looking to move really fast and want to hire like more of a single archetype of developer and not have people not have to have not having to have the conversation about are you a full stack developer.
39
00:08:03.000 --> 00:08:11.000
Right, are you are you do you know reacts good that's enough and I think that's that's a big hiring advantage for companies because the react market is very strong.
40
00:08:11.000 --> 00:08:26.000
It's one of the strongest markets in all of engineering and so I think you know that's where companies let lean and that for me means that we have more companies available to sponsor react and support react and so I want to see that virtue of cycle working.
41
00:08:27.000 --> 00:08:37.000
Yeah, yeah, that's definitely been so I'm an Ember guy. Oh my gosh, I was an Ember guy before react nice nice Lauren Tan was as well. Yeah, I'm familiar.
42
00:08:37.000 --> 00:08:52.000
Yeah, but yeah, that's a lot of places I've worked, you know, it's like we're chugging along they're like it has to be react now because you can't hire Ember developers and I'm like I hear you but you can also teach any developer.
43
00:08:52.000 --> 00:08:58.000
If you're a good developer, you can learn any front-end framework so it's like I don't know how do you feel about that argument.
44
00:08:58.000 --> 00:09:04.000
I think I think it depends again sort of coming back to the idea of like are you a software engineer.
45
00:09:04.000 --> 00:09:20.000
That's a crafts person and you're really caring about spending your lifetime minutes in the code or are you a builder or are you someone a company is hired to build something and the two equations are very different.
46
00:09:20.000 --> 00:09:32.000
Right, if you're if you're building a table like right here, you decide to be a carpenter, you want to do woodworking. If you're building that table, you're going to obsess over every corner, every edge, you know, every nook and cranny, every joint and so forth.
47
00:09:32.000 --> 00:09:42.000
But if someone if you go to, you know, restoration hardware bedbath and beyond to buy a table or something, I don't think they have tables at bedbath and be out.
48
00:09:42.000 --> 00:09:54.000
If you went to front-end framework, you're showing my age. So if you go to these companies, like you're not going to have the same attention to detail on this table you're buying as the table that you're building.
49
00:09:54.000 --> 00:10:05.000
And I think this is how companies feel about software development. I mean, I was reading a series of tweets on the bad place today that was like nobody cares the code is messy.
50
00:10:05.000 --> 00:10:19.000
And ultimately nobody cares what the code is messing. That's where the crafts people come in. And so I think there's still room for crafts in software, but I think that companies, expectations of you as a developer have changed.
51
00:10:19.000 --> 00:10:34.000
And what they want is speed, they want efficiency, and they want a delightful outcome. And for me, that's where frameworks like Ember and React and others, you know, I think of rising tide lifts all boats are so so powerful because they provide primitive tools.
52
00:10:34.000 --> 00:10:46.000
Because they provide primitives that AI can use to lead to a delightful outcome, where I think if AI were forced to live in the completely imperative space, as we've seen, like you see this all the time, it's just not as good.
53
00:10:46.000 --> 00:10:59.000
There's lots of edge cases, there's lots of bugs, and that's where frameworks are so important, even for AI. React has an advantage because in the training set, we have the preponderance of code.
54
00:10:59.000 --> 00:11:05.000
And so the models understand React better than I think they build terrible react. I don't know if you've looked at the code.
55
00:11:05.000 --> 00:11:09.000
Oh, yeah. I mean, it's not limited to react. They build terrible code in general.
56
00:11:09.000 --> 00:11:27.000
True. But it's still that question of like does it matter if it's done, right? And that's how business is thinking about it. And so I think we have to as a discipline, you know, as a center of excellence in engineering, we have to accept that there is that trade off.
57
00:11:27.000 --> 00:11:33.000
And you have to decide when you need to lean into the code and craft, and when you need to lean into the get it done.
58
00:11:33.000 --> 00:11:43.000
Yeah, Adam and I have talked about this some kind of like making an analogy to like a car, an engine of like, okay, so if you vibe code your engine, right?
59
00:11:43.000 --> 00:11:48.000
And then you take it to a mechanic, see me like, what? I don't know how to.
60
00:11:48.000 --> 00:11:58.000
So I think that's the only time that it matters if the code is messy or not is like, if you're going to need someone to go fix it later, is it readable at all?
61
00:11:58.000 --> 00:12:07.000
But maybe we're getting to an age where that doesn't matter. Like if AI gets good enough to where it's building stuff and you're sure it works, maybe you never care.
62
00:12:07.000 --> 00:12:11.000
And it'll fix its own problems. Is there a cliff will fall off where it won't be able to fix it?
63
00:12:11.000 --> 00:12:24.000
I think about it a little bit differently. This is also how I think about the why would you choose in this age where it's super easy to just ask Claude to convert your iOS app to Android?
64
00:12:24.000 --> 00:12:27.000
Like why would you choose a cross platform framework?
65
00:12:27.000 --> 00:12:28.000
No, that's true.
66
00:12:28.000 --> 00:12:36.000
It's the same question to me actually, which is that it doesn't, the economics of tokens right now are unbelievably unsustainable.
67
00:12:36.000 --> 00:12:51.000
Right, they're so heavily subsidized by the big enterprise companies paying open AI and anthropic. I think this is more true of anthropic than open AI, but you have these big enterprise contracts that are subsidizing our tokens in order that we can afford them.
68
00:12:51.000 --> 00:13:04.000
At some point, the economics is going to have to be worked out and I think tokens are either going to be driven to commodity prices by open models, which is to be transparent what I hope happens.
69
00:13:05.000 --> 00:13:23.000
But these tokenomics are still going to be a factor for a while. So if I'm having to pay for three or four or five times the number of tokens to get cross platform, or if I'm having to pay for many more tokens in order to achieve like, you know, perfectly crafted outcome or something,
70
00:13:23.000 --> 00:13:37.000
then I'm going to be spending way more money on my product than my competitor who chose to do something that was already codified like reactor, ember or angular or whatever this very well-worn practices and we know how to do things.
71
00:13:37.000 --> 00:13:45.000
I was talking about in my talk this morning, my brief talk was like, we're in this phase of like refiguring everything out.
72
00:13:45.000 --> 00:13:53.000
So all we had is all figured out and buttoned up, right? And now we're like, wait, how do we do this now? Because we're not actually writing the code. How do we cure it?
73
00:13:53.000 --> 00:14:02.000
And so I think it's going to be about that you can't abdicate your responsibility. The code the agent writes is your code.
74
00:14:02.000 --> 00:14:10.000
And so if it's not writing the code, it should be writing for long-term maintainability and to reduce later maintenance tokens cost, that's on you.
75
00:14:10.000 --> 00:14:18.000
So you have to be thinking about like the stuff to just like we've always done is engineering. This hasn't changed. Think about the future. Who's going to pick this up later, even if it's an agent.
76
00:14:18.000 --> 00:14:23.000
You want that agent to be able to pick it up and understand and work with it quickly because that's much less expensive.
77
00:14:23.000 --> 00:14:34.000
Yeah, that's true. I think about it too. Like we've got factories which make things out of plastic. They've got molds, right? Everything's pre-made, fast to make, cheap to make.
78
00:14:35.000 --> 00:14:40.000
You know, it's got the fast and cheap side down, but you got a crafter who's kind of got the opposite thing going on, right?
79
00:14:40.000 --> 00:14:45.000
It's slow, but the quality is super high. You can get something bespoke that perfectly fits your scenario.
80
00:14:45.000 --> 00:14:52.000
And I think we're just going to have those tensions forever components. I've seen so many times where you pull them off the shelf and they seem to just be exactly what you wanted.
81
00:14:52.000 --> 00:15:01.000
And then a year in, you're like, we want to modify this one thing a bit. You're like, oh crap, it's a black box to us though. We bought it off the shelf. We got to go off the rails now and build our own thing.
82
00:15:01.000 --> 00:15:09.000
And so you've got this pendulum that just won't stop swinging and everyone wants the pendulum to stop except until you want something bespoke.
83
00:15:09.000 --> 00:15:15.000
They both need to exist just like they do building homes. You got people building homes that are cookie cutter. You got crafters still.
84
00:15:15.000 --> 00:15:21.000
And so there's just tension between factory creation of something and bespoke and I kind of like it.
85
00:15:21.000 --> 00:15:29.000
Yeah, I need both. I want to go to a local market and get something handmade, but I also want to go pick up something fast from the store so they can both coexist.
86
00:15:29.000 --> 00:15:40.000
I think that tension drives innovation. I mean, I think it drives us to innovate because you know, you get started, you get in, you get your product moving and then you have a need that isn't served by your component.
87
00:15:40.000 --> 00:15:49.000
So you have to invent, right? And so I think that tension is incredibly healthy. That's why I love the fact that there's multiple competing reactive matter frameworks.
88
00:15:49.000 --> 00:15:57.000
At some point, the remix guys are like, you know, React is not for us right now. React is no longer for us. We're going to we're going to fork off and do this thing.
89
00:15:57.000 --> 00:16:09.000
And they're doing really interesting things that all of us can learn from. So, you know, to me, I've never been somebody who thinks that that innovate or the competition is like this thing to be resisted or to be to be squashed.
90
00:16:09.000 --> 00:16:17.000
That's something that to me celebrate, like people are out there inventing and creating and building. That's going to be something I'm always excited about.
91
00:16:17.000 --> 00:16:25.000
Hell yeah, I love that. Yeah. Okay. Is HTML programming language?
92
00:16:25.000 --> 00:16:29.000
You're trying to get me in trouble. Sure. Why not?
93
00:16:29.000 --> 00:16:49.000
Okay. There's CSS. I mean, sorry to all the designers. I don't think it's as much of a programming language as it is, you know, a declarative manifest, but we have things like variables and they have some ability to do functions and stuff now.
94
00:16:49.000 --> 00:17:03.000
Yeah. It can do calculations. It's it's it's blurrier than it used to be. I mean, I don't particularly use CSS that way. You know, I'm definitely on the tailwind bag and bandwagon for the most part.
95
00:17:03.000 --> 00:17:15.000
Hell yeah. What do you get called yesterday fail wind? Yeah, I never know. Not happy about tailwind yesterday. I didn't I did not hear the I did not hear the confuffle.
96
00:17:15.000 --> 00:17:32.000
Yeah, there was, um, were you at the party thing last night? Yeah, I was there briefly. Yeah. Okay. Yeah. So when they did the thing on stage, something about tailwind and everyone was just like, like, no tailwind, like, like, learns CSS. Like, okay, it's it is CSS. But all right. Yeah.
97
00:17:32.000 --> 00:17:47.000
You know, I mean, like, I've been I've been a big advocate for semantic approaches to programming and declarative approaches to programming. And I think that the, um, I think folks that are hanging on to like being able to tell the computer what to do.
98
00:17:47.000 --> 00:18:00.000
Um, I think you're missing out. Like, it's just much better to describe state and the things you want to see when a particular state is present. I feel like that's what you get with with tailwind. You know, it's very semantic and declarative. And I can read it.
99
00:18:00.000 --> 00:18:15.000
Yeah. The year later and still understand what it's doing. Yeah. I don't have to hunt through six different files to figure it out. It's right there. Uh, to me, it's, I'm sorry to ever, I'm sorry to the tailwind team for people calling it fail. Yeah.
100
00:18:15.000 --> 00:18:28.000
Yeah. Um, all right. So you mentioned a few things that you wanted to chat about. And I think this is a good one. Um, do you think when you frameworks at all is, is AI getting rid of the need for any of this?
101
00:18:28.000 --> 00:18:46.000
Uh, I think I kind of already answered this accidentally, forgetting that we had this question on the list, but I do think frameworks will play a vital part of even the agentic programming world simply because it provides a well thought out and well tested primitives for AI to use.
102
00:18:46.000 --> 00:19:15.000
If AI is writing everything from scratch, you're going to end up with a slightly different version of everything every, every, every single time because it's not to turn on deterministic. And so wouldn't we rather know that the boundaries are the same so that we can plug and play pieces. Right. So if you're writing using AI to generate your team's design system and then that design system needs to be plugged into a different application is gets developed later because you have developed it with a framework that provides contracts and the way you expose those things to other.
103
00:19:16.000 --> 00:19:29.000
Applications, you're going to be able to drop that in in music. If it were slightly different than you're always going to have to AI be like AI retrofit this thing and then, thus, you're spending more tokens and it's the same thing for cross platform and so forth.
104
00:19:29.000 --> 00:19:43.000
The fact that you have people like, you know, I'll shout out shout out to my expo team, obsessing about like the smallest details of how an API works on, you know, the, you know, to adopt.
105
00:19:43.000 --> 00:19:53.000
iOS is new glass views or something right like they've obsessed about those details so that the animations are fluid and buttery and smooth and the refractions are great and all that stuff right people have obsessed about that.
106
00:19:53.000 --> 00:20:04.000
So the agent doesn't have to and so the agent who's quickly by just dropping something in and now you're not waiting for five minutes while code cloud comes up with something you're waiting for five seconds or 15 seconds.
107
00:20:04.000 --> 00:20:20.000
So I think frameworks still play an incredibly important part and I would rather see agents using and this is what you're generally seeing that the agents are smart enough that the models are smart enough to use well, you know, well to find libraries or well, well respected libraries.
108
00:20:20.000 --> 00:20:27.000
I don't know if they're doing it based on forks or star count or what but they're picking they're definitely picking good libraries for the most part.
109
00:20:27.000 --> 00:20:42.000
You do have to educate it and that's where I think the community has such a huge role to play and like, you know, creating the MCP of how, how you think right and creating creating the skills of how you think about those things and to help people get the same for similar results.
110
00:20:42.000 --> 00:20:52.000
But ultimately, I think frameworks are here to stay and going to play a vital role for as far as I can see into the future, which I spend a lot of time thinking pretty far in the future.
111
00:20:52.000 --> 00:21:02.000
Yeah, it's almost like the framework that was made to optimize all of us to keep us all within the same kind of confounds and bounce and APIs so that things were predictable as you move forward.
112
00:21:02.000 --> 00:21:09.000
Those also play into what LLM's want. They need to know that there's rails. They need to know what's a copycat. They need to follow the framework.
113
00:21:09.000 --> 00:21:16.000
No, but you know, like I'm in on rails like you're in a cart, you know, I'm just giving you shit.
114
00:21:16.000 --> 00:21:21.000
It was great. I was about to go Donkey Kong on you. Remember that level you're on rails.
115
00:21:21.000 --> 00:21:29.000
But yeah, all those things you need to provide those patterns and it's either going to discover them from your your mess that you've made as a code base or it's going to try to pull them from its memory.
116
00:21:29.000 --> 00:21:37.000
But if you're there providing them really explicitly and a framework can help do that even more, then there's success on that horizon naturally.
117
00:21:37.000 --> 00:21:44.000
So the same things that empowered your team are now empowering your agents. I think that's important to continue on.
118
00:21:44.000 --> 00:21:53.000
100% agree. I think, you know, the thing I've learned about using Claude and others is that they do much better just like human beings.
119
00:21:53.000 --> 00:22:00.000
They do just way better with constraints. You know, if you just say, build me a website, what are you going to get out of Claude?
120
00:22:00.000 --> 00:22:10.000
But if you give it all of the different things that you want to see, the stack it should use, the best practices it should apply, it does way better job.
121
00:22:10.000 --> 00:22:13.000
If you heard that you're not supposed to be mean to your LLM though.
122
00:22:13.000 --> 00:22:19.000
No, I personally have found they responded really well to like harsh criticism.
123
00:22:19.000 --> 00:22:25.000
Yeah, you and Wes Boss saying there's a lot of people out there cousin and then you'd see in the Claude code leak that it tracks all of your cuss words at it.
124
00:22:25.000 --> 00:22:28.000
They're like monitoring how angry people are.
125
00:22:28.000 --> 00:22:32.000
Yeah, I've not seen that, but I would I would imagine I'm on a list somewhere.
126
00:22:32.000 --> 00:22:40.000
Yeah, I do like the Claude now. I mean, so I usually use open code, but I've been using Claude code because I got the like free open source maintainer one or whatever.
127
00:22:40.000 --> 00:22:46.000
I was going to mention it all the time. I didn't even get that.
128
00:22:46.000 --> 00:22:52.000
I'm just important, I guess. No, I think I was one of the first people like within minutes of them posting it.
129
00:22:52.000 --> 00:22:55.000
I applied. So I think that was what it's news.
130
00:22:55.000 --> 00:23:03.000
But now it asks you in your Claude session. I don't know if it's based on how long you've been talking to it or like, how's your session going?
131
00:23:03.000 --> 00:23:09.000
Like rated one to four or whatever. So if I'm having a bad time, I'm like one, you know, like terrible.
132
00:23:09.000 --> 00:23:16.000
I think I think that's super smart that they put that in there, but it's always I have I have answered.
133
00:23:16.000 --> 00:23:25.000
I've given a lie so many times because they get me just the right wrong time where I actually hit like trying to type 20 and I give them a heads going fine.
134
00:23:25.000 --> 00:23:31.000
Yeah, when I really am not happy. And then other times I've given it like a really bad rating when it's kicking ass.
135
00:23:32.000 --> 00:23:36.000
You're confusing. Yes, I'm very confusing. Claude does not understand me.
136
00:23:36.000 --> 00:23:39.000
Yeah. So I do encourage.
137
00:23:39.000 --> 00:23:55.000
Reverb back to like the the previous point kind of for a minute. Do you think I feel like as a developer or as an AI consuming JavaScript error messages and things like I feel like we do a really bad job of telling you what went wrong.
138
00:23:55.000 --> 00:24:03.000
It's like, hey, something broke and you're like, cool. Let me manually step through everything to find where it actually broke.
139
00:24:03.000 --> 00:24:15.000
Do you think that there will be a push to improve a lot of that so that like because if you're using rust, like LLMs can just build you whatever you want in rust because it tells you exactly what went wrong and how and it can just go to town.
140
00:24:15.000 --> 00:24:21.000
Like if we could get that with like various JavaScript things, I feel like that could be really helpful.
141
00:24:21.000 --> 00:24:31.000
Yeah, I think it's kind of ironic that the impetus to improve error messages is going to be the machines are going to be reading them.
142
00:24:31.000 --> 00:24:41.000
I think people have really tried. I don't know. Over the years, I mean, the reacting has gone through so many different permutations of how to provide error messages.
143
00:24:41.000 --> 00:24:49.000
And for a while, there were some like actual technical limitations that prevented us from like getting deep enough into the stack of what happened to give you a better error message.
144
00:24:49.000 --> 00:25:01.000
But a lot of that's been fixed. I mean, I was watching Aurora's talk today and the couple of the error messages that came up when she was like in the middle of a compile or something were so much better than they used to be.
145
00:25:01.000 --> 00:25:10.000
And I think for cells led the way on some really good improvements to error messaging. But I absolutely do think that it's incumbent upon all of us.
146
00:25:10.000 --> 00:25:23.000
Again, like we should all have a mindset of how do we make? I hope that we all agree that AI programming with AI is something that amplifies our ability to deliver.
147
00:25:23.000 --> 00:25:31.000
And so we want to all be focused on like making our tools and so forth really good for AI's as much as we want to focus on making them good for humans.
148
00:25:31.000 --> 00:25:42.000
And I think the balance is going to shift such that eventually we might care more about making tools work well for AI than we do about people because people are using a completely different user interface than they used to.
149
00:25:42.000 --> 00:25:54.000
They're not reading the error messages like the user or their copy pasting them in an ideal world. You have an integrated system, an IDE kind of from from the bottom to the top that is watching the error messages for you.
150
00:25:54.000 --> 00:26:00.000
And what I always do is I always tell Claude or whoever I'm using spawn these tasks in the background so you can monitor the logs.
151
00:26:00.000 --> 00:26:07.000
I don't want to do copy paste. And so I think what we want is systems that do all of those kinds of things by default.
152
00:26:07.000 --> 00:26:14.000
And in order for those to be successful, we're going to have to be really good as two builders in making the agents completely understand what it is that's wrong.
153
00:26:14.000 --> 00:26:19.000
And you're right about last. That's just a wonderful experience using an agent to build for us.
154
00:26:19.000 --> 00:26:22.000
And I think it's going to be a great experience.
155
00:26:22.000 --> 00:26:25.000
I think it's going to be a great experience.
156
00:26:25.000 --> 00:26:28.000
I think it's going to be a great experience.
157
00:26:28.000 --> 00:26:30.000
I think it's going to be a great experience.
158
00:26:30.000 --> 00:26:32.000
I think it's going to be a great experience.
159
00:26:32.000 --> 00:26:34.000
I think it's going to be a great experience.
160
00:26:34.000 --> 00:26:36.000
I think it's going to be a great experience.
161
00:26:36.000 --> 00:26:38.000
I think it's going to be a great experience.
162
00:26:38.000 --> 00:26:40.000
I think it's going to be a great experience.
163
00:26:40.000 --> 00:26:42.000
I think it's going to be a great experience.
164
00:26:42.000 --> 00:26:44.000
I think it's going to be a great experience.
165
00:26:44.000 --> 00:26:46.000
I think it's going to be a great experience.
166
00:26:46.000 --> 00:26:51.000
Yesterday, I think somebody opened source the same thing for iOS simulator builds.
167
00:26:51.000 --> 00:26:57.000
So you can now control, automate iOS simulator builds and get the error messages back from that.
168
00:26:57.000 --> 00:26:59.000
Wow.
169
00:26:59.000 --> 00:27:03.000
And that has React Dev Tools built in, which is based on Chrome MCP.
170
00:27:03.000 --> 00:27:07.000
So I'm imagining you can probably automate that with the Chrome MCP too.
171
00:27:07.000 --> 00:27:11.000
Don't take my word for it.
172
00:27:11.000 --> 00:27:12.000
All right.
173
00:27:12.000 --> 00:27:17.000
So what are some of the goals for the React Foundation?
174
00:27:17.000 --> 00:27:18.000
Yeah.
175
00:27:18.000 --> 00:27:19.000
Let's just stop with that.
176
00:27:19.000 --> 00:27:21.000
I answered that one first, I guess.
177
00:27:21.000 --> 00:27:27.000
I think the big one for this year is making sure that we transition out of being a single company,
178
00:27:27.000 --> 00:27:31.000
steward into a multi company foundation.
179
00:27:31.000 --> 00:27:32.000
Successfully.
180
00:27:32.000 --> 00:27:34.000
You know, it's a lot of voices.
181
00:27:34.000 --> 00:27:37.000
The founding partners all have different perspectives on thing.
182
00:27:37.000 --> 00:27:39.000
They've been great partners so far.
183
00:27:39.000 --> 00:27:42.000
But they all have different perspectives and different priorities.
184
00:27:42.000 --> 00:27:46.000
And so making sure that we're able to successfully take care of everybody.
185
00:27:46.000 --> 00:27:49.000
It's going to be a challenge for a framework that's never done that.
186
00:27:49.000 --> 00:27:52.000
I talk a lot when I talk about the story of the React Foundation.
187
00:27:52.000 --> 00:27:58.000
For those that don't know, it took over four years to get it done, which is a long time.
188
00:27:58.000 --> 00:28:02.000
And that's like a web standard.
189
00:28:02.000 --> 00:28:03.000
Twice that.
190
00:28:03.000 --> 00:28:06.000
Twice that for web standard.
191
00:28:06.000 --> 00:28:10.000
We were first looking at it and starting to like write, you know, put pen to paper.
192
00:28:10.000 --> 00:28:14.000
What we recognized pretty quickly was like the React team itself was not.
193
00:28:14.000 --> 00:28:17.000
Ed Metta was not ready to operate like a foundation.
194
00:28:17.000 --> 00:28:19.000
We were so used to Metta's tools.
195
00:28:19.000 --> 00:28:24.000
We were so used to being able to move at a breakneck speed and only like release what we had done.
196
00:28:24.000 --> 00:28:26.000
We've been using for two years.
197
00:28:26.000 --> 00:28:28.000
We release it two years later.
198
00:28:28.000 --> 00:28:33.000
And so there are a lot of different like points of dissonance when they came to being able to operate as a foundation.
199
00:28:33.000 --> 00:28:37.000
And so we pulled back from doing the foundation for a couple years and said let's fix.
200
00:28:37.000 --> 00:28:42.000
Let's fix everything internally first such that our interface boundary is better.
201
00:28:42.000 --> 00:28:43.000
That happened.
202
00:28:43.000 --> 00:28:51.000
Things like, you know, React Native went from releasing like on a very ad hoc schedule and not very often to doing six reliable releases a year.
203
00:28:51.000 --> 00:28:54.000
React core is like one solid release a year.
204
00:28:54.000 --> 00:29:00.000
And so and where it's like before you could be like, I, you know, I don't know when React is going to do a release.
205
00:29:00.000 --> 00:29:04.000
But you know, at least it's super backwards compatible, right?
206
00:29:04.000 --> 00:29:07.000
So like there's there's different equities people are bouncing.
207
00:29:07.000 --> 00:29:09.000
So that's kind of coming together.
208
00:29:09.000 --> 00:29:14.000
So the big goals this year is kind of to come back to your question really about like stability.
209
00:29:14.000 --> 00:29:17.000
Stabilizing React in a foundation.
210
00:29:17.000 --> 00:29:23.000
For the first time supporting financially maintainers events around the world communities.
211
00:29:23.000 --> 00:29:28.000
We want to help build communities where they're struggling to get those started because of resources.
212
00:29:28.000 --> 00:29:33.000
So things like for me, Asia is a big market that I want to expand to.
213
00:29:33.000 --> 00:29:38.000
We've never done a good job in Asia of localizing our documentation or reaching out to them.
214
00:29:38.000 --> 00:29:46.000
And then there's something like 10 million developers in China alone that are not counted in our surveys that are not among the people we target with things.
215
00:29:46.000 --> 00:29:52.000
So I really was just there in China and they are so excited about React and like we want to be involved.
216
00:29:52.000 --> 00:29:57.000
We want to help with stable API, which is the big project I'm excited about for React Native this year.
217
00:29:57.000 --> 00:30:02.000
That will empower more out of tree platforms, which I want to get rid of that term.
218
00:30:02.000 --> 00:30:07.000
All platforms are platforms that they want to be part of react. They're welcome.
219
00:30:07.000 --> 00:30:14.000
But we're going to basically rebuild the API layer such that the React Native things sit atop that as opposed to being forks.
220
00:30:14.000 --> 00:30:18.000
Every platform is a fork that's going to take a while.
221
00:30:18.000 --> 00:30:29.000
We're going to start on that this year such that the operating systems in China can use React just as easily as macOS, iOS, Android, and Windows.
222
00:30:29.000 --> 00:30:30.000
So there's a big ones.
223
00:30:30.000 --> 00:30:41.000
But the things I'm most excited about are actually starting to give back to the community because for too many years people have given so much blood sweat and tears to this project.
224
00:30:41.000 --> 00:30:46.000
And other than like accolades and appreciation, they haven't gotten a lot out of it.
225
00:30:46.000 --> 00:30:48.000
And so I really want to start turning that around.
226
00:30:48.000 --> 00:30:50.000
I want to see some new communities spring up.
227
00:30:50.000 --> 00:30:52.000
Those are the big ones for this year.
228
00:30:52.000 --> 00:30:55.000
Hopefully we can get React Comp again this year.
229
00:30:55.000 --> 00:31:01.000
The only reason that it's a hope and not a promise is that we want to make sure we have an event that's worth everybody attending.
230
00:31:01.000 --> 00:31:03.000
And so I'm in the process now.
231
00:31:03.000 --> 00:31:08.000
We're in the process now of curating what the program would be and making sure that it's up to the standards.
232
00:31:08.000 --> 00:31:11.000
The high standard that we set for React Comp.
233
00:31:11.000 --> 00:31:13.000
So yeah, those are the good ones.
234
00:31:13.000 --> 00:31:14.000
Nice.
235
00:31:14.000 --> 00:31:15.000
Yeah.
236
00:31:15.000 --> 00:31:24.000
So going back to your point a second ago about giving back to open source and stuff.
237
00:31:24.000 --> 00:31:34.000
Like do you think in general contributing to open source is helpful for your career?
238
00:31:34.000 --> 00:31:43.000
Like let me clarify, like directly contributes to getting hired somewhere versus is just like learning.
239
00:31:43.000 --> 00:31:45.000
Like you definitely learn from it.
240
00:31:45.000 --> 00:31:50.000
Do you think it like anyone goes, oh, I know that guy from open source.
241
00:31:50.000 --> 00:31:54.000
Let me hire him or like.
242
00:31:54.000 --> 00:32:00.000
I mean, I can think of dozens of examples of what you just described actually happening.
243
00:32:00.000 --> 00:32:01.000
Yeah.
244
00:32:01.000 --> 00:32:07.000
I think it would be pretty heavily biased if I just relied on those memories.
245
00:32:07.000 --> 00:32:12.000
So like anything else, yes, but it depends.
246
00:32:12.000 --> 00:32:19.000
It depends on your ability to network your ability to make sure that you're seen in that community.
247
00:32:19.000 --> 00:32:26.000
I think that there are a lot of unsung heroes in open source that are brilliant engineers.
248
00:32:26.000 --> 00:32:33.000
I have given just as much of themselves as other people, but nobody knows their name.
249
00:32:33.000 --> 00:32:34.000
Yeah.
250
00:32:34.000 --> 00:32:35.000
Nobody knows what they've done.
251
00:32:35.000 --> 00:32:43.000
And that's because they're not maybe into self promotion or someone else hasn't come along and sponsored them to say like,
252
00:32:43.000 --> 00:32:45.000
look at the great work this person is doing.
253
00:32:45.000 --> 00:32:46.000
Right.
254
00:32:46.000 --> 00:32:47.000
Everybody else know.
255
00:32:47.000 --> 00:32:50.000
And I think that you know, it's it's just like any other skill.
256
00:32:50.000 --> 00:32:53.000
You have to know how to make sure that your work is appreciated.
257
00:32:53.000 --> 00:32:54.000
Yeah.
258
00:32:54.000 --> 00:33:00.000
And there are too many people are focused on getting the work done and not being recognized.
259
00:33:00.000 --> 00:33:04.000
And it's sad in some ways that like you have to be promoting yourself.
260
00:33:04.000 --> 00:33:08.000
But if we're taking the lens of does it help me get hired?
261
00:33:08.000 --> 00:33:13.000
I think it does not by itself get you let you help you get hired in the last someone sponsors you.
262
00:33:13.000 --> 00:33:16.000
Or you are an advocate for yourself.
263
00:33:16.000 --> 00:33:21.000
And the not to open a whole can of worms that I'm going to get in trouble for.
264
00:33:21.000 --> 00:33:29.000
But I think the sort of newest generation of software developers that I've seen are not great itself promotion.
265
00:33:29.000 --> 00:33:31.000
They're not a great itself advocacy.
266
00:33:31.000 --> 00:33:32.000
Right.
267
00:33:32.000 --> 00:33:35.000
And need sponsorship more than ever.
268
00:33:35.000 --> 00:33:39.000
And so I would call upon those folks to develop that skill.
269
00:33:39.000 --> 00:33:44.000
But moreover, I would call on the engineers who are a little further in their career to be a sponsor.
270
00:33:44.000 --> 00:33:56.000
Be an advocate because it would be a shame to lose the kind of amazing engineering into the shadows that we're seeing from some of these folks because they didn't have someone.
271
00:33:56.000 --> 00:33:59.000
You know, vocalizing for them that they're doing good work.
272
00:33:59.000 --> 00:34:08.000
So advocacy and all is always been an important part of every career for every person always needed somebody to give them an opportunity.
273
00:34:08.000 --> 00:34:12.000
And this is the opportunity we have to advocate for people.
274
00:34:12.000 --> 00:34:20.000
Yeah, yeah, it's always been a problem of like, you know, there's every every few years somebody blows up like the fake or JS thing was a big thing.
275
00:34:20.000 --> 00:34:25.000
Or like, you know, somebody's like, hey, all these companies are using my thing for free and giving me no money.
276
00:34:25.000 --> 00:34:27.000
And I've spent a ton of time on it.
277
00:34:27.000 --> 00:34:29.000
It's like, yeah, there's got to be a fix for that.
278
00:34:29.000 --> 00:34:31.000
But there's I want to fix that problem.
279
00:34:31.000 --> 00:34:37.000
And I also want to fix the problem of, you know, AI code Providence.
280
00:34:37.000 --> 00:34:45.000
I mean, like the the elements are spitting out full copies of open source libraries rather than pulling them off the shelf.
281
00:34:45.000 --> 00:34:47.000
And I think we have to fix that.
282
00:34:47.000 --> 00:34:50.000
I think we also have to fix.
283
00:34:50.000 --> 00:34:59.000
For example, I mean, if you think about it from reacts perspective and I'm not somebody who spends time wasting my energy on being frustrated.
284
00:34:59.000 --> 00:35:09.000
But if you think about, if you go and you ask cloud or any of these systems pretty much to build you any commerce website, what technology will they use?
285
00:35:09.000 --> 00:35:11.000
With that sentence, they'll use react.
286
00:35:11.000 --> 00:35:12.000
Yeah.
287
00:35:12.000 --> 00:35:14.000
And they'll use probably next.
288
00:35:14.000 --> 00:35:19.000
You used to be tailwind, but they also, they don't necessarily love tailwind as much anymore.
289
00:35:19.000 --> 00:35:23.000
I hope that's not true.
290
00:35:23.000 --> 00:35:29.000
But, you know, react isn't seeing anything from open AI or or anthropic.
291
00:35:29.000 --> 00:35:32.000
And no one is so rampant theft of everything.
292
00:35:32.000 --> 00:35:33.000
Exactly.
293
00:35:33.000 --> 00:35:39.000
And so even, you know, even the big ones like us are struggling with the same problem as the small ones.
294
00:35:39.000 --> 00:35:44.000
And I think that as an industry, we need to stand together and figure out how to solve this problem.
295
00:35:44.000 --> 00:35:46.000
I don't have any good solutions for you.
296
00:35:46.000 --> 00:35:54.000
Like the things I'm thinking about are, as we talked about earlier, like cloud and codex and other code agents.
297
00:35:54.000 --> 00:35:57.000
They don't write very good react code.
298
00:35:57.000 --> 00:36:06.000
Can we provide the e-vows, can we provide the post training data or pre training data to help generate code that is performance?
299
00:36:06.000 --> 00:36:11.000
It's not using refs for state tracking because it doesn't like our life cycle and so forth.
300
00:36:11.000 --> 00:36:18.000
So, you know, there's opportunities there, I think maybe to partner with the AI companies in order to develop,
301
00:36:18.000 --> 00:36:21.000
help them develop products that are better for their customers.
302
00:36:21.000 --> 00:36:23.000
And then it's a win-win, right?
303
00:36:23.000 --> 00:36:29.000
So I'm looking, trying to look at it from different angles and see, you know, how can we all benefit from this?
304
00:36:29.000 --> 00:36:31.000
You know, it does feel like a gold rush, right?
305
00:36:31.000 --> 00:36:34.000
It feels like this vibrant, this energy is just percolating everywhere.
306
00:36:34.000 --> 00:36:36.000
It feels like a really good time.
307
00:36:36.000 --> 00:36:43.000
But it's also important that we keep our minds and keep ourselves focused on the outcomes that affect human beings.
308
00:36:43.000 --> 00:36:45.000
And this is what I said earlier too.
309
00:36:45.000 --> 00:36:54.000
It's like, you can look at the efficiency gains you get from your engineers at your company using AI as an opportunity to save money.
310
00:36:54.000 --> 00:37:03.000
I think the smart money is on using the opportunity and the efficiency that you're saving to do more of the things you've been unable to do throughout the years
311
00:37:03.000 --> 00:37:06.000
because you have to make hard decisions of prioritization.
312
00:37:06.000 --> 00:37:10.000
You still have to be good about prioritizing, but I think this opens the door to like,
313
00:37:10.000 --> 00:37:14.000
explore those business vectors that you've not been prioritizing because you were scared.
314
00:37:14.000 --> 00:37:16.000
Like, now you can do it. Now you can afford it.
315
00:37:16.000 --> 00:37:21.000
You have 10 times as much money as you did before because you're engineers with 10 times more valuable.
316
00:37:21.000 --> 00:37:24.000
Yeah. So, laying people off is not the way to save money.
317
00:37:24.000 --> 00:37:28.000
It's build more, like Adam and I talked about this a lot of like,
318
00:37:28.000 --> 00:37:30.000
you probably have a lot of SaaS products you use, right?
319
00:37:31.000 --> 00:37:33.000
Make a whole team, have them build that.
320
00:37:33.000 --> 00:37:34.000
That'll save you some money.
321
00:37:34.000 --> 00:37:39.000
Like firing people is such a short-sighted way of saving money.
322
00:37:39.000 --> 00:37:40.000
Yeah.
323
00:37:40.000 --> 00:37:41.000
I agree.
324
00:37:41.000 --> 00:37:45.000
I think also the thing you just said,
325
00:37:45.000 --> 00:37:48.000
it's something like I worry about a little bit which is like,
326
00:37:48.000 --> 00:37:51.000
how will I reshape the SaaS market?
327
00:37:51.000 --> 00:37:54.000
There's so many brilliant tools out there that...
328
00:37:54.000 --> 00:37:56.000
Yeah, like clerk. Check it out.
329
00:37:56.000 --> 00:37:59.000
Like, I'm a clerk, I'm a clerk customer.
330
00:37:59.000 --> 00:38:00.000
Yeah.
331
00:38:00.000 --> 00:38:03.000
But I have, I have also rolled my own off.
332
00:38:03.000 --> 00:38:06.000
I've been in a lot of customer, a lot of zero customers as well.
333
00:38:06.000 --> 00:38:13.000
And I just like so, you know, not wanting to go through the experience of setting up off,
334
00:38:13.000 --> 00:38:14.000
setting up off again.
335
00:38:14.000 --> 00:38:18.000
I'm like, I'm just going to do magic links and that's it because it's easy.
336
00:38:18.000 --> 00:38:21.000
But then you guys decided to add billing and I was like,
337
00:38:22.000 --> 00:38:24.000
now I'm like, now I'm like interested again, right?
338
00:38:24.000 --> 00:38:25.000
Yeah.
339
00:38:25.000 --> 00:38:28.000
But I have a few apps running with clerk and a great job.
340
00:38:28.000 --> 00:38:31.000
I mean, what a great product clerk is.
341
00:38:31.000 --> 00:38:36.000
I wonder if we can learn from the music industry here where they kind of went off the wall
342
00:38:36.000 --> 00:38:40.000
where if you play eight seconds of a song, you got to open ease to the artists.
343
00:38:40.000 --> 00:38:43.000
And there's an amount of that that feels pretty silly.
344
00:38:43.000 --> 00:38:47.000
But at the same time, at least they're giving attribution and paying back
345
00:38:47.000 --> 00:38:49.000
for using somebody else's stuff.
346
00:38:50.000 --> 00:38:52.000
And I've been sent DMs already, which people said,
347
00:38:52.000 --> 00:38:55.000
hey, I invoked this LLM to make a design.
348
00:38:55.000 --> 00:39:00.000
And I literally saw your name show up in the results of either the styles that were written
349
00:39:00.000 --> 00:39:03.000
or my name was in the HTML that was producing stuff like that.
350
00:39:03.000 --> 00:39:07.000
And I'm like, I don't think I want pennies to start trickling towards me or whatever.
351
00:39:07.000 --> 00:39:10.000
But, you know, CSS tricks did the same thing.
352
00:39:10.000 --> 00:39:15.000
Chris Coyers, like I built 10 years of CSS content for LLMs to strip it and steal it
353
00:39:15.000 --> 00:39:17.000
in a couple of days and give me nothing.
354
00:39:17.000 --> 00:39:21.000
So we got the music industry that's like got trolls to pop up over all these bridges
355
00:39:21.000 --> 00:39:24.000
and they go, yeah, you used a fraction of our song.
356
00:39:24.000 --> 00:39:27.000
You know, you must pay BMG or whatever it is.
357
00:39:27.000 --> 00:39:28.000
I don't want to do that.
358
00:39:28.000 --> 00:39:33.000
But I wonder if there is something that we can learn from them as being sort of too far
359
00:39:33.000 --> 00:39:34.000
in that pendulum swing.
360
00:39:34.000 --> 00:39:36.000
Maybe AI can do something else.
361
00:39:36.000 --> 00:39:39.000
And yeah, instead of taking the money that you're saving and you're enhancing
362
00:39:39.000 --> 00:39:45.000
and pocketing it as a big company, giving some of that back to what you clearly are borrowing.
363
00:39:46.000 --> 00:39:47.000
I don't know.
364
00:39:47.000 --> 00:39:50.000
Yeah, I mean, I think it's definitely something I want to work on figuring out.
365
00:39:50.000 --> 00:39:53.000
I'm in a good position to do so at the foundation.
366
00:39:53.000 --> 00:39:58.000
So for context, those that don't know, Linux, Linux Foundation is the parent company
367
00:39:58.000 --> 00:40:00.000
of React Foundation now.
368
00:40:00.000 --> 00:40:05.000
And one of the big efforts they've started this year is the Agente AI Foundation,
369
00:40:05.000 --> 00:40:10.000
which is looking at way more than this, but looking at all of these types of things.
370
00:40:11.000 --> 00:40:16.000
You know, if you take a step back and you think about those of us who've spent a long career
371
00:40:16.000 --> 00:40:22.000
in the developer tooling space, we are excited about helping other people build things.
372
00:40:22.000 --> 00:40:29.000
And so I don't need the pennies to trickle into me because I am the executive director of the React Foundation.
373
00:40:29.000 --> 00:40:33.000
What I want is for the developers who built the code that Claude was trained on
374
00:40:33.000 --> 00:40:38.000
to be rewarded for the energy and effort and time and lifetime minutes they spent on that.
375
00:40:38.000 --> 00:40:42.000
Because my whole North Star was helping other people bring their ideas to life,
376
00:40:42.000 --> 00:40:48.000
in this case, helping other people bring their ideas to life that help other people bring their ideas to life,
377
00:40:48.000 --> 00:40:52.000
that, like I said, that chain of providence has to be preserved,
378
00:40:52.000 --> 00:40:58.000
such that people can be at the bare minimum recognized for their contributions.
379
00:40:58.000 --> 00:41:01.000
And in a better world rewarded for those contributions.
380
00:41:01.000 --> 00:41:04.000
You know, rewarding record recognition, go hand in hand.
381
00:41:05.000 --> 00:41:10.000
And I think that, you know, I think we can all agree, I don't know if this is true,
382
00:41:10.000 --> 00:41:16.000
but I think we can all agree that from helping people bring the ideas into the world perspective,
383
00:41:16.000 --> 00:41:18.000
AI is a huge unlock.
384
00:41:18.000 --> 00:41:24.000
And as somebody who's spent a career helping people do that, I'm so inspired and excited about this arrow.
385
00:41:24.000 --> 00:41:28.000
But it comes with these trade-offs that I think we have to reckon with.
386
00:41:28.000 --> 00:41:32.000
Otherwise, what will we be building upon 10 years from now?
387
00:41:32.000 --> 00:41:36.000
You know, it won't be novel, it won't be innovative, it won't be exciting.
388
00:41:36.000 --> 00:41:39.000
It'll be, again, back to what I talked about in my talk this morning,
389
00:41:39.000 --> 00:41:41.000
regurgitation of the same ideas over and over.
390
00:41:41.000 --> 00:41:42.000
Yeah.
391
00:41:42.000 --> 00:41:46.000
I could sit in a different, in a form, but it's still just all, you know, shitty ice cream.
392
00:41:46.000 --> 00:41:50.000
So I really want to see us, I really want to see us figure this problem out.
393
00:41:50.000 --> 00:41:54.000
I call that the mainstream just getting wider, where you've got a mainstream,
394
00:41:54.000 --> 00:41:58.000
and it's popular, but as we regurgitate more and more mainstream,
395
00:41:58.000 --> 00:42:02.000
the mainstream just gets wider, and the indies and the edges get smaller and smaller.
396
00:42:02.000 --> 00:42:03.000
That's true.
397
00:42:03.000 --> 00:42:05.000
And I think that's dangerous.
398
00:42:05.000 --> 00:42:08.000
The same way that you don't want pure factories, or you don't want pure craft.
399
00:42:08.000 --> 00:42:11.000
There's always a healthy middle ground here, and we've got to find some balance.
400
00:42:11.000 --> 00:42:13.000
So I'm happy to hear you say that, man.
401
00:42:13.000 --> 00:42:17.000
I do think there's a lot of catching up we have to do as an industry.
402
00:42:17.000 --> 00:42:23.000
Like, you know, Adam made a nice marketing page for us the other day.
403
00:42:23.000 --> 00:42:29.000
We have a couple of prompts done better than, like, in my opinion, our website.
404
00:42:29.000 --> 00:42:35.000
So I was like, huh, like, when that's that good, and there's still websites that suck,
405
00:42:35.000 --> 00:42:40.000
it's like, that we need to just raise everybody up to that good level first.
406
00:42:40.000 --> 00:42:41.000
Let's work on that.
407
00:42:41.000 --> 00:42:43.000
Then we can figure out what's next.
408
00:42:43.000 --> 00:42:44.000
I agree.
409
00:42:44.000 --> 00:42:47.000
You know, I think we've talked a lot about this at Expo too.
410
00:42:47.000 --> 00:42:51.000
It's like, what's going to be the differentiating factor in the future?
411
00:42:51.000 --> 00:42:54.000
Or now the future is now the future is here.
412
00:42:54.000 --> 00:43:02.000
And I think it still comes down to like taste, you know, knowing what you want to create
413
00:43:02.000 --> 00:43:05.000
and what you want to be different about that.
414
00:43:05.000 --> 00:43:07.000
And I think that that's going to be a big one.
415
00:43:07.000 --> 00:43:13.000
I think longevity and stability are going to be things that are going to be highly prized and valued,
416
00:43:13.000 --> 00:43:15.000
you know, sticking around.
417
00:43:15.000 --> 00:43:17.000
It's going to be harder than it used to be.
418
00:43:17.000 --> 00:43:21.000
Like, entire market verticals are going to get saturated with players.
419
00:43:21.000 --> 00:43:24.000
And at that point, like, how do you differentiate it?
420
00:43:24.000 --> 00:43:32.000
If every hotel has the same or like, really similar or like, really awesome digital experiences,
421
00:43:32.000 --> 00:43:35.000
how will they differentiate themselves from one another?
422
00:43:35.000 --> 00:43:39.000
You know, remember when we got the phone based hotel room key,
423
00:43:39.000 --> 00:43:43.000
and like, only a couple to it and it's helping or whatever that has this, it's awesome.
424
00:43:43.000 --> 00:43:47.000
But if every place has that, you're not going to feel like, oh, that's so cool anymore, right?
425
00:43:47.000 --> 00:43:49.000
It's just like, why find an airplane the first time you ever used it?
426
00:43:49.000 --> 00:43:52.000
You're like, oh, I got to just shift the diff from 30,000 feet.
427
00:43:52.000 --> 00:43:53.000
That's so cool.
428
00:43:53.000 --> 00:43:56.000
And now you're grumpy anytime it doesn't work, right?
429
00:43:56.000 --> 00:43:57.000
You're not amazed by it anymore.
430
00:43:57.000 --> 00:43:58.000
You're just grumpy.
431
00:43:58.000 --> 00:44:04.000
And so we're going to get to that same place, I think, with the saturation in every niche,
432
00:44:04.000 --> 00:44:11.000
which I'm hopeful about because I think what it does is it pushes us back into the analog world of differentiation.
433
00:44:11.000 --> 00:44:15.000
It puts us, pushes us to reach different heights of differentiation.
434
00:44:15.000 --> 00:44:17.000
The weird web, right?
435
00:44:17.000 --> 00:44:21.000
Yeah, going back to Photoshop slices and throwing it all on the floor.
436
00:44:21.000 --> 00:44:23.000
Please God, no.
437
00:44:23.000 --> 00:44:26.000
That is, I don't want to slice any corners.
438
00:44:26.000 --> 00:44:31.000
But I think there's a really interesting shift coming because we're going to democratize
439
00:44:31.000 --> 00:44:35.000
so much more of this development that tastes and differentiation is going to be even more huge.
440
00:44:35.000 --> 00:44:39.000
And I'm hopeful that it actually pushes us back to some degree into the analog world
441
00:44:39.000 --> 00:44:43.000
where I think differentiation matters much more.
442
00:44:43.000 --> 00:44:44.000
Yeah.
443
00:44:44.000 --> 00:44:49.000
Yeah, I hadn't considered, like, the sole way I decide is this resort dope.
444
00:44:49.000 --> 00:44:51.000
I'm like, is the website really good?
445
00:44:51.000 --> 00:44:56.000
If you put a lot of money into the website, then I know you probably put a lot of money into your experience there.
446
00:44:56.000 --> 00:44:58.000
So if everyone gets that, then yeah, you're right.
447
00:44:58.000 --> 00:45:01.000
It's like, how do I know if it's a good one or not?
448
00:45:01.000 --> 00:45:02.000
Exactly.
449
00:45:02.000 --> 00:45:04.000
You're all going to know by trying.
450
00:45:04.000 --> 00:45:05.000
Yeah.
451
00:45:05.000 --> 00:45:09.000
There is high correlation between a well thought out website where the content is there.
452
00:45:09.000 --> 00:45:12.000
It's beautiful and the experience that you get somewhere.
453
00:45:12.000 --> 00:45:15.000
So I don't think that's ever bit me really where I've gone to a beautiful website.
454
00:45:15.000 --> 00:45:18.000
And then I showed up to the brick and mortar store and I'm like, what the?
455
00:45:18.000 --> 00:45:20.000
I feel like that's a movie in the making.
456
00:45:20.000 --> 00:45:23.000
I think I should write that.
457
00:45:23.000 --> 00:45:24.000
Yeah.
458
00:45:24.000 --> 00:45:25.000
All right.
459
00:45:25.000 --> 00:45:26.000
We are about at time here.
460
00:45:26.000 --> 00:45:27.000
Is there anything that we miss?
461
00:45:27.000 --> 00:45:30.000
Do you want to mention plug, etc?
462
00:45:30.000 --> 00:45:39.000
If you have any interest for everybody out there, if you have any interest in participating in the activities at the foundation, definitely let us know.
463
00:45:39.000 --> 00:45:41.000
There's a ton of great stuff, you know, reach out to me.
464
00:45:41.000 --> 00:45:44.000
You can, there's a contact form on the website.
465
00:45:44.000 --> 00:45:46.000
That generally goes to me.
466
00:45:46.000 --> 00:45:47.000
So reach out.
467
00:45:47.000 --> 00:45:48.000
I'd love to hear from you.
468
00:45:48.000 --> 00:45:51.000
There's a lot of activities that we need help with on the website.
469
00:45:51.000 --> 00:45:59.000
I mean, on the, at the foundation, the last thing I'd say is like, I really want to encourage folks to consider this moment.
470
00:45:59.000 --> 00:46:04.000
Like a call to action to start building.
471
00:46:04.000 --> 00:46:08.000
I don't think we need to have 70 million of the same things out there.
472
00:46:08.000 --> 00:46:18.000
But getting really good at commanding agents and commanding your fleet of agents and learning how to parallelize your work and learning how to work on five or six different things in the same day at the same time is not a skill.
473
00:46:18.000 --> 00:46:22.000
A lot of engineers have who were much more used to going deep and focusing.
474
00:46:22.000 --> 00:46:25.000
So start practicing this because this is where the industry is going.
475
00:46:25.000 --> 00:46:30.000
And it's, you know, the way I think about it right now is there's never been a better time to be a builder.
476
00:46:30.000 --> 00:46:40.000
And so I'd love to see, you know, many more ideas, you know, leverage expo, leverage these framers, leverage and acts, leverage, you know, tan stack, whatever your, whatever your favorite is.
477
00:46:40.000 --> 00:46:47.000
To get your idea out there and get it into hands because you're not going to learn so much more by actually shipping something.
478
00:46:47.000 --> 00:46:53.000
Especially if it's a project of passion for yourself, then you will, uh, by reading blogs, sitting there reading blogs about air.
479
00:46:53.000 --> 00:46:59.000
Or just get your hands dirty, get in there, make all the mistakes we're all making and help us figure out this next air of software development.
480
00:46:59.000 --> 00:47:00.000
Hell yeah.
481
00:47:00.000 --> 00:47:01.000
Love that.
482
00:47:01.000 --> 00:47:02.000
Yeah.
483
00:47:02.000 --> 00:47:03.000
I got one final request though.
484
00:47:03.000 --> 00:47:04.000
All right.
485
00:47:04.000 --> 00:47:07.000
Will you say whiskey, web and whatnot in your dope ass voice?
486
00:47:07.000 --> 00:47:14.000
You're listening to whiskey, web and whatnot and react by me.
487
00:47:14.000 --> 00:47:15.000
Yeah.
488
00:47:15.000 --> 00:47:16.000
Nice.
489
00:47:16.000 --> 00:47:18.000
Is it all right?
490
00:47:18.000 --> 00:47:19.000
Thanks guys.
491
00:47:19.000 --> 00:47:20.000
It was really great to be here.
492
00:47:20.000 --> 00:47:21.000
Oh my gosh.
493
00:47:21.000 --> 00:47:22.000
Yeah. Thanks for coming on.
494
00:47:22.000 --> 00:47:23.000
Thanks everyone for listening.
495
00:47:23.000 --> 00:47:25.000
If you liked it, please subscribe, leave some comments and reviews.
496
00:47:25.000 --> 00:47:26.000
We appreciate it.
497
00:47:26.000 --> 00:47:29.000
And we will catch you in, well, I would say next time, but in a few minutes because we'll be back on.
498
00:47:29.000 --> 00:47:30.000
Yeah.
499
00:47:30.000 --> 00:47:31.000
With some other, some other requests.
500
00:47:31.000 --> 00:47:32.000
Yes, indeed.
501
00:47:32.000 --> 00:47:33.000
All right.
502
00:47:33.000 --> 00:47:34.000
This is great.
503
00:47:34.000 --> 00:47:36.000
Congratulations, citizen.
504
00:47:36.000 --> 00:47:40.000
You are now prepared to face the challenges of the modern technological world.
505
00:47:40.000 --> 00:47:48.000
With the proper tools, a steady hand and a reasonably configured terminal, any developer can orchestrate AI agents with confidence.
506
00:47:48.000 --> 00:47:50.000
You'll do just fine.
507
00:47:50.000 --> 00:47:55.000
Thank you for listening to whiskey, web and whatnot, the world's most important AI podcast.
508
00:47:55.000 --> 00:48:00.000
For additional resources including official merchandise, visit whiskey.fund.
509
00:48:00.000 --> 00:48:09.000
And remember to subscribe, rate and review so this vital information may reach others because the future of technology depends on it.
510
00:48:10.000 --> 00:48:12.000
You
1
00:00:00.000 --> 00:00:19.000
In today's modern technological world, developers face many difficult questions, artificial intelligence, autonomous agents, JavaScript frameworks, even CSS, with so much happening so quickly, how can a developer possibly keep up?
2
00:00:19.000 --> 00:00:43.000
Simple. Just listen to the world's most important AI podcast. Two experts, countless opinions, zero hesitation. The internet is complicated. These men are not. Each week they review the latest developments in artificial intelligence and modern web development. This is Whiskey, Web, and WhatNot. The world's most important AI podcast.
3
00:00:43.000 --> 00:00:54.000
Hey, what's up, everybody? Welcome to Whiskey Web and WhatNot with your host, Robbie the Wagner and Adam Thomas, our guy, the nerd. I'm here y'all. What's up?
4
00:00:54.000 --> 00:01:06.000
Yeah, we are here live from React Miami, podcasting from the clerk booth. Thanks so much to clerk for your generous sponsorship to have us here. And who's our first guest today, Adam?
5
00:01:06.000 --> 00:01:31.000
Oh, you might know them as executive director of the React Foundation, former React Lead meta, React compiler champion, relauncher of React, conf creator of React Impact Signals, mentor, leader, speaker, photographer, strategic growth advisor. Overall, Kat, that keeps the pipelines clean, so tools and devs can flow and grow. Now working at expo is chief developer evangelist, but still continues to help react and react native remain open, sustainable and community led. This is Seth Webster, y'all.
6
00:01:31.000 --> 00:01:52.000
Yeah, I need to hire you. How's it going, Seth? It's going great. Man, I'm super excited to be here at React Miami. It's my first time both to react Miami and to Miami. So it's been amazing so far. This event is blown my mind in multiple ways, even in the first few hours.
7
00:01:52.000 --> 00:02:04.000
Yeah, it makes two of us, man. Yeah, it's a great event. They do a great job. Miami's always fun. Yeah, a little loud for me. Like every event is like, what if the music was super loud?
8
00:02:04.000 --> 00:02:11.000
You know, you get to take it up every I get out to the last conference. Yeah, that's true. Sometimes volume is your only choice. Yeah.
9
00:02:12.000 --> 00:02:24.000
All right, so we have a giant list of hot takes. I don't know if we're going to get to all of them, but I want to start with one that I feel like you'll have opinions on. All right, is React a framework?
10
00:02:24.000 --> 00:02:38.000
I thought I was done with this conversation. You know, I think, I think, you know, just depends on where you draw the fault lines, man. Like to me, React is meant to be tiny.
11
00:02:38.000 --> 00:02:51.000
Yeah, it's meant to be a library. But over time, as you know, the needs of users and developers have been surfaced more and more stuff has been added to react. And I think there's a growing feeling among the react.
12
00:02:51.000 --> 00:03:01.000
The folks that are actually still working on react is is actually, you know, getting back to that react core and react native core such that such that the library.
13
00:03:01.000 --> 00:03:17.000
The library is very thin and that it's easier to bolt things on and it's easier to use these scape hatches and so forth. So I think, I think generally speaking, and it's done what every piece of software throughout time and memorial has done, which is to grow as the needs grow.
14
00:03:17.000 --> 00:03:28.000
And I think it's a good time. It has been a good time for a while to look back at scaling that back to the core and putting more things out into the community for community management and that's something foundations looking hard at.
15
00:03:28.000 --> 00:03:43.000
One of the projects I'm most excited about this year is actually working on. I have a bunch of companies that have stepped up to sponsor stable API work for React Native, which basically means that we're going to have this API that platforms can target.
16
00:03:43.000 --> 00:03:56.000
And no longer be victims of every time we do a react native release and it's going to three months catching up, they'll be able to target a stable API and we're going to send for that API such that you can depend on it as long as you're targeting a specific version.
17
00:03:56.000 --> 00:04:08.000
So like stuff like that's like long overdue and gets us back to being a library and less of a framework, but I would say we've drifted pretty, pretty squarely into the framework space over the years.
18
00:04:08.000 --> 00:04:10.000
Yeah, so it depends, you would say.
19
00:04:10.000 --> 00:04:16.000
Yeah, I mean, they, you know, I guess I'm a little bit of a politician. So, you know, they got it.
20
00:04:16.000 --> 00:04:25.000
It was at the very end, but that's what I think I think the right thing is to be a library.
21
00:04:25.000 --> 00:04:32.000
Yes, yeah. Can you move your mic just a little further this way, like like tilt. Yeah, cool.
22
00:04:32.000 --> 00:04:35.000
Because if you're facing, I'm just trying to get as much sound as we can anyway.
23
00:04:35.000 --> 00:04:42.000
That's good. Sorry. Yeah, you're good. Yeah. What about what do you think about React server components? Was it a good idea?
24
00:04:42.000 --> 00:04:54.000
I mean, yes, I was championing that from the inside of the original code name was Flight and it was worked on by Lauren Tan and I think Dan Abramov worked on it.
25
00:04:54.000 --> 00:05:01.000
And the original, the original goal was the same as it is today, which is to give React the full stack story.
26
00:05:01.000 --> 00:05:15.000
You know, the, you know, clear indications after many years of developing spas was that there was no like canonical way to do data fetching and to do secure data fetching close to the server.
27
00:05:15.000 --> 00:05:27.000
You're always having to wire something up. You're having to do API keys and bear tokens and all this stuff to do relatively simple things that Ruby on Rails developers were like, just do this.
28
00:05:27.000 --> 00:05:40.000
You know, it's so easy. And so I think, you know, the in spirit, it was definitely a good idea. One thing that was, you know, super hard in the development of it is that meta has such bespoke web infrastructure.
29
00:05:40.000 --> 00:05:49.000
We could not use server components at meta. And so we had to find an external partner to take on the work of like integrating it into some kind of full stack.
30
00:05:49.000 --> 00:06:02.000
And that's where Verself stepped in and it did an amazing job with the first version. Of course, being a being a friend and framework, we didn't have, we don't have still probably the muscles to understand like the full stack and like the security implications.
31
00:06:02.000 --> 00:06:10.000
And so now you're seeing because of that that we have for the first time in React's history, we're vulnerable to exploits, which we weren't before.
32
00:06:10.000 --> 00:06:27.000
And so I think generally it's a good idea. I think having that story and being able to say that we can operate anywhere from the server to the client and also like, you know, removed likelihood of leaking secret keys to the web, I think is an important step forward for sure.
33
00:06:27.000 --> 00:06:44.000
I don't know that the implementation has reached, excuse me, I don't know that the current like implementation of server components has reached its max yet. I don't know where necessary or like server components prime, but I do think that the continued development there is going to only make things better.
34
00:06:44.000 --> 00:06:59.000
The biggest thing that I think is confusing for people now is like things like caching and so forth. It's like there's not a really clear and Verself trying some things, but there's not really a clear like all encompassing story for caching that that really works for everybody.
35
00:06:59.000 --> 00:07:11.000
And so I think you're going to see evolution there, but I do think it was a really good idea. And I just think it's as even though it's been out for a couple of years, it's still early days because it hasn't had that many iterations.
36
00:07:11.000 --> 00:07:28.000
Yeah, I do think on the one hand, I think it's nice to be able to use the same things on the client and the server. On the other hand, I like the separation of like, I know for sure which one I'm operating on because it's a totally different language or something for server stuff.
37
00:07:28.000 --> 00:07:43.000
Yeah, I can see arguments for both ways, but yeah, I think you know, when you think about it from like the artisan or craftsperson perspective, I think I definitely agree with you that it's like nice to have the ability to turn and tweak all the knobs.
38
00:07:43.000 --> 00:08:03.000
I think where we found that server components has been such a huge hit is a companies that you know are looking to move really fast and want to hire like more of a single archetype of developer and not have people not have to have not having to have the conversation about are you a full stack developer.
39
00:08:03.000 --> 00:08:11.000
Right, are you are you do you know reacts good that's enough and I think that's that's a big hiring advantage for companies because the react market is very strong.
40
00:08:11.000 --> 00:08:26.000
It's one of the strongest markets in all of engineering and so I think you know that's where companies let lean and that for me means that we have more companies available to sponsor react and support react and so I want to see that virtue of cycle working.
41
00:08:27.000 --> 00:08:37.000
Yeah, yeah, that's definitely been so I'm an Ember guy. Oh my gosh, I was an Ember guy before react nice nice Lauren Tan was as well. Yeah, I'm familiar.
42
00:08:37.000 --> 00:08:52.000
Yeah, but yeah, that's a lot of places I've worked, you know, it's like we're chugging along they're like it has to be react now because you can't hire Ember developers and I'm like I hear you but you can also teach any developer.
43
00:08:52.000 --> 00:08:58.000
If you're a good developer, you can learn any front-end framework so it's like I don't know how do you feel about that argument.
44
00:08:58.000 --> 00:09:04.000
I think I think it depends again sort of coming back to the idea of like are you a software engineer.
45
00:09:04.000 --> 00:09:20.000
That's a crafts person and you're really caring about spending your lifetime minutes in the code or are you a builder or are you someone a company is hired to build something and the two equations are very different.
46
00:09:20.000 --> 00:09:32.000
Right, if you're if you're building a table like right here, you decide to be a carpenter, you want to do woodworking. If you're building that table, you're going to obsess over every corner, every edge, you know, every nook and cranny, every joint and so forth.
47
00:09:32.000 --> 00:09:42.000
But if someone if you go to, you know, restoration hardware bedbath and beyond to buy a table or something, I don't think they have tables at bedbath and be out.
48
00:09:42.000 --> 00:09:54.000
If you went to front-end framework, you're showing my age. So if you go to these companies, like you're not going to have the same attention to detail on this table you're buying as the table that you're building.
49
00:09:54.000 --> 00:10:05.000
And I think this is how companies feel about software development. I mean, I was reading a series of tweets on the bad place today that was like nobody cares the code is messy.
50
00:10:05.000 --> 00:10:19.000
And ultimately nobody cares what the code is messing. That's where the crafts people come in. And so I think there's still room for crafts in software, but I think that companies, expectations of you as a developer have changed.
51
00:10:19.000 --> 00:10:34.000
And what they want is speed, they want efficiency, and they want a delightful outcome. And for me, that's where frameworks like Ember and React and others, you know, I think of rising tide lifts all boats are so so powerful because they provide primitive tools.
52
00:10:34.000 --> 00:10:46.000
Because they provide primitives that AI can use to lead to a delightful outcome, where I think if AI were forced to live in the completely imperative space, as we've seen, like you see this all the time, it's just not as good.
53
00:10:46.000 --> 00:10:59.000
There's lots of edge cases, there's lots of bugs, and that's where frameworks are so important, even for AI. React has an advantage because in the training set, we have the preponderance of code.
54
00:10:59.000 --> 00:11:05.000
And so the models understand React better than I think they build terrible react. I don't know if you've looked at the code.
55
00:11:05.000 --> 00:11:09.000
Oh, yeah. I mean, it's not limited to react. They build terrible code in general.
56
00:11:09.000 --> 00:11:27.000
True. But it's still that question of like does it matter if it's done, right? And that's how business is thinking about it. And so I think we have to as a discipline, you know, as a center of excellence in engineering, we have to accept that there is that trade off.
57
00:11:27.000 --> 00:11:33.000
And you have to decide when you need to lean into the code and craft, and when you need to lean into the get it done.
58
00:11:33.000 --> 00:11:43.000
Yeah, Adam and I have talked about this some kind of like making an analogy to like a car, an engine of like, okay, so if you vibe code your engine, right?
59
00:11:43.000 --> 00:11:48.000
And then you take it to a mechanic, see me like, what? I don't know how to.
60
00:11:48.000 --> 00:11:58.000
So I think that's the only time that it matters if the code is messy or not is like, if you're going to need someone to go fix it later, is it readable at all?
61
00:11:58.000 --> 00:12:07.000
But maybe we're getting to an age where that doesn't matter. Like if AI gets good enough to where it's building stuff and you're sure it works, maybe you never care.
62
00:12:07.000 --> 00:12:11.000
And it'll fix its own problems. Is there a cliff will fall off where it won't be able to fix it?
63
00:12:11.000 --> 00:12:24.000
I think about it a little bit differently. This is also how I think about the why would you choose in this age where it's super easy to just ask Claude to convert your iOS app to Android?
64
00:12:24.000 --> 00:12:27.000
Like why would you choose a cross platform framework?
65
00:12:27.000 --> 00:12:28.000
No, that's true.
66
00:12:28.000 --> 00:12:36.000
It's the same question to me actually, which is that it doesn't, the economics of tokens right now are unbelievably unsustainable.
67
00:12:36.000 --> 00:12:51.000
Right, they're so heavily subsidized by the big enterprise companies paying open AI and anthropic. I think this is more true of anthropic than open AI, but you have these big enterprise contracts that are subsidizing our tokens in order that we can afford them.
68
00:12:51.000 --> 00:13:04.000
At some point, the economics is going to have to be worked out and I think tokens are either going to be driven to commodity prices by open models, which is to be transparent what I hope happens.
69
00:13:05.000 --> 00:13:23.000
But these tokenomics are still going to be a factor for a while. So if I'm having to pay for three or four or five times the number of tokens to get cross platform, or if I'm having to pay for many more tokens in order to achieve like, you know, perfectly crafted outcome or something,
70
00:13:23.000 --> 00:13:37.000
then I'm going to be spending way more money on my product than my competitor who chose to do something that was already codified like reactor, ember or angular or whatever this very well-worn practices and we know how to do things.
71
00:13:37.000 --> 00:13:45.000
I was talking about in my talk this morning, my brief talk was like, we're in this phase of like refiguring everything out.
72
00:13:45.000 --> 00:13:53.000
So all we had is all figured out and buttoned up, right? And now we're like, wait, how do we do this now? Because we're not actually writing the code. How do we cure it?
73
00:13:53.000 --> 00:14:02.000
And so I think it's going to be about that you can't abdicate your responsibility. The code the agent writes is your code.
74
00:14:02.000 --> 00:14:10.000
And so if it's not writing the code, it should be writing for long-term maintainability and to reduce later maintenance tokens cost, that's on you.
75
00:14:10.000 --> 00:14:18.000
So you have to be thinking about like the stuff to just like we've always done is engineering. This hasn't changed. Think about the future. Who's going to pick this up later, even if it's an agent.
76
00:14:18.000 --> 00:14:23.000
You want that agent to be able to pick it up and understand and work with it quickly because that's much less expensive.
77
00:14:23.000 --> 00:14:34.000
Yeah, that's true. I think about it too. Like we've got factories which make things out of plastic. They've got molds, right? Everything's pre-made, fast to make, cheap to make.
78
00:14:35.000 --> 00:14:40.000
You know, it's got the fast and cheap side down, but you got a crafter who's kind of got the opposite thing going on, right?
79
00:14:40.000 --> 00:14:45.000
It's slow, but the quality is super high. You can get something bespoke that perfectly fits your scenario.
80
00:14:45.000 --> 00:14:52.000
And I think we're just going to have those tensions forever components. I've seen so many times where you pull them off the shelf and they seem to just be exactly what you wanted.
81
00:14:52.000 --> 00:15:01.000
And then a year in, you're like, we want to modify this one thing a bit. You're like, oh crap, it's a black box to us though. We bought it off the shelf. We got to go off the rails now and build our own thing.
82
00:15:01.000 --> 00:15:09.000
And so you've got this pendulum that just won't stop swinging and everyone wants the pendulum to stop except until you want something bespoke.
83
00:15:09.000 --> 00:15:15.000
They both need to exist just like they do building homes. You got people building homes that are cookie cutter. You got crafters still.
84
00:15:15.000 --> 00:15:21.000
And so there's just tension between factory creation of something and bespoke and I kind of like it.
85
00:15:21.000 --> 00:15:29.000
Yeah, I need both. I want to go to a local market and get something handmade, but I also want to go pick up something fast from the store so they can both coexist.
86
00:15:29.000 --> 00:15:40.000
I think that tension drives innovation. I mean, I think it drives us to innovate because you know, you get started, you get in, you get your product moving and then you have a need that isn't served by your component.
87
00:15:40.000 --> 00:15:49.000
So you have to invent, right? And so I think that tension is incredibly healthy. That's why I love the fact that there's multiple competing reactive matter frameworks.
88
00:15:49.000 --> 00:15:57.000
At some point, the remix guys are like, you know, React is not for us right now. React is no longer for us. We're going to we're going to fork off and do this thing.
89
00:15:57.000 --> 00:16:09.000
And they're doing really interesting things that all of us can learn from. So, you know, to me, I've never been somebody who thinks that that innovate or the competition is like this thing to be resisted or to be to be squashed.
90
00:16:09.000 --> 00:16:17.000
That's something that to me celebrate, like people are out there inventing and creating and building. That's going to be something I'm always excited about.
91
00:16:17.000 --> 00:16:25.000
Hell yeah, I love that. Yeah. Okay. Is HTML programming language?
92
00:16:25.000 --> 00:16:29.000
You're trying to get me in trouble. Sure. Why not?
93
00:16:29.000 --> 00:16:49.000
Okay. There's CSS. I mean, sorry to all the designers. I don't think it's as much of a programming language as it is, you know, a declarative manifest, but we have things like variables and they have some ability to do functions and stuff now.
94
00:16:49.000 --> 00:17:03.000
Yeah. It can do calculations. It's it's it's blurrier than it used to be. I mean, I don't particularly use CSS that way. You know, I'm definitely on the tailwind bag and bandwagon for the most part.
95
00:17:03.000 --> 00:17:15.000
Hell yeah. What do you get called yesterday fail wind? Yeah, I never know. Not happy about tailwind yesterday. I didn't I did not hear the I did not hear the confuffle.
96
00:17:15.000 --> 00:17:32.000
Yeah, there was, um, were you at the party thing last night? Yeah, I was there briefly. Yeah. Okay. Yeah. So when they did the thing on stage, something about tailwind and everyone was just like, like, no tailwind, like, like, learns CSS. Like, okay, it's it is CSS. But all right. Yeah.
97
00:17:32.000 --> 00:17:47.000
You know, I mean, like, I've been I've been a big advocate for semantic approaches to programming and declarative approaches to programming. And I think that the, um, I think folks that are hanging on to like being able to tell the computer what to do.
98
00:17:47.000 --> 00:18:00.000
Um, I think you're missing out. Like, it's just much better to describe state and the things you want to see when a particular state is present. I feel like that's what you get with with tailwind. You know, it's very semantic and declarative. And I can read it.
99
00:18:00.000 --> 00:18:15.000
Yeah. The year later and still understand what it's doing. Yeah. I don't have to hunt through six different files to figure it out. It's right there. Uh, to me, it's, I'm sorry to ever, I'm sorry to the tailwind team for people calling it fail. Yeah.
100
00:18:15.000 --> 00:18:28.000
Yeah. Um, all right. So you mentioned a few things that you wanted to chat about. And I think this is a good one. Um, do you think when you frameworks at all is, is AI getting rid of the need for any of this?
101
00:18:28.000 --> 00:18:46.000
Uh, I think I kind of already answered this accidentally, forgetting that we had this question on the list, but I do think frameworks will play a vital part of even the agentic programming world simply because it provides a well thought out and well tested primitives for AI to use.
102
00:18:46.000 --> 00:19:15.000
If AI is writing everything from scratch, you're going to end up with a slightly different version of everything every, every, every single time because it's not to turn on deterministic. And so wouldn't we rather know that the boundaries are the same so that we can plug and play pieces. Right. So if you're writing using AI to generate your team's design system and then that design system needs to be plugged into a different application is gets developed later because you have developed it with a framework that provides contracts and the way you expose those things to other.
103
00:19:16.000 --> 00:19:29.000
Applications, you're going to be able to drop that in in music. If it were slightly different than you're always going to have to AI be like AI retrofit this thing and then, thus, you're spending more tokens and it's the same thing for cross platform and so forth.
104
00:19:29.000 --> 00:19:43.000
The fact that you have people like, you know, I'll shout out shout out to my expo team, obsessing about like the smallest details of how an API works on, you know, the, you know, to adopt.
105
00:19:43.000 --> 00:19:53.000
iOS is new glass views or something right like they've obsessed about those details so that the animations are fluid and buttery and smooth and the refractions are great and all that stuff right people have obsessed about that.
106
00:19:53.000 --> 00:20:04.000
So the agent doesn't have to and so the agent who's quickly by just dropping something in and now you're not waiting for five minutes while code cloud comes up with something you're waiting for five seconds or 15 seconds.
107
00:20:04.000 --> 00:20:20.000
So I think frameworks still play an incredibly important part and I would rather see agents using and this is what you're generally seeing that the agents are smart enough that the models are smart enough to use well, you know, well to find libraries or well, well respected libraries.
108
00:20:20.000 --> 00:20:27.000
I don't know if they're doing it based on forks or star count or what but they're picking they're definitely picking good libraries for the most part.
109
00:20:27.000 --> 00:20:42.000
You do have to educate it and that's where I think the community has such a huge role to play and like, you know, creating the MCP of how, how you think right and creating creating the skills of how you think about those things and to help people get the same for similar results.
110
00:20:42.000 --> 00:20:52.000
But ultimately, I think frameworks are here to stay and going to play a vital role for as far as I can see into the future, which I spend a lot of time thinking pretty far in the future.
111
00:20:52.000 --> 00:21:02.000
Yeah, it's almost like the framework that was made to optimize all of us to keep us all within the same kind of confounds and bounce and APIs so that things were predictable as you move forward.
112
00:21:02.000 --> 00:21:09.000
Those also play into what LLM's want. They need to know that there's rails. They need to know what's a copycat. They need to follow the framework.
113
00:21:09.000 --> 00:21:16.000
No, but you know, like I'm in on rails like you're in a cart, you know, I'm just giving you shit.
114
00:21:16.000 --> 00:21:21.000
It was great. I was about to go Donkey Kong on you. Remember that level you're on rails.
115
00:21:21.000 --> 00:21:29.000
But yeah, all those things you need to provide those patterns and it's either going to discover them from your your mess that you've made as a code base or it's going to try to pull them from its memory.
116
00:21:29.000 --> 00:21:37.000
But if you're there providing them really explicitly and a framework can help do that even more, then there's success on that horizon naturally.
117
00:21:37.000 --> 00:21:44.000
So the same things that empowered your team are now empowering your agents. I think that's important to continue on.
118
00:21:44.000 --> 00:21:53.000
100% agree. I think, you know, the thing I've learned about using Claude and others is that they do much better just like human beings.
119
00:21:53.000 --> 00:22:00.000
They do just way better with constraints. You know, if you just say, build me a website, what are you going to get out of Claude?
120
00:22:00.000 --> 00:22:10.000
But if you give it all of the different things that you want to see, the stack it should use, the best practices it should apply, it does way better job.
121
00:22:10.000 --> 00:22:13.000
If you heard that you're not supposed to be mean to your LLM though.
122
00:22:13.000 --> 00:22:19.000
No, I personally have found they responded really well to like harsh criticism.
123
00:22:19.000 --> 00:22:25.000
Yeah, you and Wes Boss saying there's a lot of people out there cousin and then you'd see in the Claude code leak that it tracks all of your cuss words at it.
124
00:22:25.000 --> 00:22:28.000
They're like monitoring how angry people are.
125
00:22:28.000 --> 00:22:32.000
Yeah, I've not seen that, but I would I would imagine I'm on a list somewhere.
126
00:22:32.000 --> 00:22:40.000
Yeah, I do like the Claude now. I mean, so I usually use open code, but I've been using Claude code because I got the like free open source maintainer one or whatever.
127
00:22:40.000 --> 00:22:46.000
I was going to mention it all the time. I didn't even get that.
128
00:22:46.000 --> 00:22:52.000
I'm just important, I guess. No, I think I was one of the first people like within minutes of them posting it.
129
00:22:52.000 --> 00:22:55.000
I applied. So I think that was what it's news.
130
00:22:55.000 --> 00:23:03.000
But now it asks you in your Claude session. I don't know if it's based on how long you've been talking to it or like, how's your session going?
131
00:23:03.000 --> 00:23:09.000
Like rated one to four or whatever. So if I'm having a bad time, I'm like one, you know, like terrible.
132
00:23:09.000 --> 00:23:16.000
I think I think that's super smart that they put that in there, but it's always I have I have answered.
133
00:23:16.000 --> 00:23:25.000
I've given a lie so many times because they get me just the right wrong time where I actually hit like trying to type 20 and I give them a heads going fine.
134
00:23:25.000 --> 00:23:31.000
Yeah, when I really am not happy. And then other times I've given it like a really bad rating when it's kicking ass.
135
00:23:32.000 --> 00:23:36.000
You're confusing. Yes, I'm very confusing. Claude does not understand me.
136
00:23:36.000 --> 00:23:39.000
Yeah. So I do encourage.
137
00:23:39.000 --> 00:23:55.000
Reverb back to like the the previous point kind of for a minute. Do you think I feel like as a developer or as an AI consuming JavaScript error messages and things like I feel like we do a really bad job of telling you what went wrong.
138
00:23:55.000 --> 00:24:03.000
It's like, hey, something broke and you're like, cool. Let me manually step through everything to find where it actually broke.
139
00:24:03.000 --> 00:24:15.000
Do you think that there will be a push to improve a lot of that so that like because if you're using rust, like LLMs can just build you whatever you want in rust because it tells you exactly what went wrong and how and it can just go to town.
140
00:24:15.000 --> 00:24:21.000
Like if we could get that with like various JavaScript things, I feel like that could be really helpful.
141
00:24:21.000 --> 00:24:31.000
Yeah, I think it's kind of ironic that the impetus to improve error messages is going to be the machines are going to be reading them.
142
00:24:31.000 --> 00:24:41.000
I think people have really tried. I don't know. Over the years, I mean, the reacting has gone through so many different permutations of how to provide error messages.
143
00:24:41.000 --> 00:24:49.000
And for a while, there were some like actual technical limitations that prevented us from like getting deep enough into the stack of what happened to give you a better error message.
144
00:24:49.000 --> 00:25:01.000
But a lot of that's been fixed. I mean, I was watching Aurora's talk today and the couple of the error messages that came up when she was like in the middle of a compile or something were so much better than they used to be.
145
00:25:01.000 --> 00:25:10.000
And I think for cells led the way on some really good improvements to error messaging. But I absolutely do think that it's incumbent upon all of us.
146
00:25:10.000 --> 00:25:23.000
Again, like we should all have a mindset of how do we make? I hope that we all agree that AI programming with AI is something that amplifies our ability to deliver.
147
00:25:23.000 --> 00:25:31.000
And so we want to all be focused on like making our tools and so forth really good for AI's as much as we want to focus on making them good for humans.
148
00:25:31.000 --> 00:25:42.000
And I think the balance is going to shift such that eventually we might care more about making tools work well for AI than we do about people because people are using a completely different user interface than they used to.
149
00:25:42.000 --> 00:25:54.000
They're not reading the error messages like the user or their copy pasting them in an ideal world. You have an integrated system, an IDE kind of from from the bottom to the top that is watching the error messages for you.
150
00:25:54.000 --> 00:26:00.000
And what I always do is I always tell Claude or whoever I'm using spawn these tasks in the background so you can monitor the logs.
151
00:26:00.000 --> 00:26:07.000
I don't want to do copy paste. And so I think what we want is systems that do all of those kinds of things by default.
152
00:26:07.000 --> 00:26:14.000
And in order for those to be successful, we're going to have to be really good as two builders in making the agents completely understand what it is that's wrong.
153
00:26:14.000 --> 00:26:19.000
And you're right about last. That's just a wonderful experience using an agent to build for us.
154
00:26:19.000 --> 00:26:22.000
And I think it's going to be a great experience.
155
00:26:22.000 --> 00:26:25.000
I think it's going to be a great experience.
156
00:26:25.000 --> 00:26:28.000
I think it's going to be a great experience.
157
00:26:28.000 --> 00:26:30.000
I think it's going to be a great experience.
158
00:26:30.000 --> 00:26:32.000
I think it's going to be a great experience.
159
00:26:32.000 --> 00:26:34.000
I think it's going to be a great experience.
160
00:26:34.000 --> 00:26:36.000
I think it's going to be a great experience.
161
00:26:36.000 --> 00:26:38.000
I think it's going to be a great experience.
162
00:26:38.000 --> 00:26:40.000
I think it's going to be a great experience.
163
00:26:40.000 --> 00:26:42.000
I think it's going to be a great experience.
164
00:26:42.000 --> 00:26:44.000
I think it's going to be a great experience.
165
00:26:44.000 --> 00:26:46.000
I think it's going to be a great experience.
166
00:26:46.000 --> 00:26:51.000
Yesterday, I think somebody opened source the same thing for iOS simulator builds.
167
00:26:51.000 --> 00:26:57.000
So you can now control, automate iOS simulator builds and get the error messages back from that.
168
00:26:57.000 --> 00:26:59.000
Wow.
169
00:26:59.000 --> 00:27:03.000
And that has React Dev Tools built in, which is based on Chrome MCP.
170
00:27:03.000 --> 00:27:07.000
So I'm imagining you can probably automate that with the Chrome MCP too.
171
00:27:07.000 --> 00:27:11.000
Don't take my word for it.
172
00:27:11.000 --> 00:27:12.000
All right.
173
00:27:12.000 --> 00:27:17.000
So what are some of the goals for the React Foundation?
174
00:27:17.000 --> 00:27:18.000
Yeah.
175
00:27:18.000 --> 00:27:19.000
Let's just stop with that.
176
00:27:19.000 --> 00:27:21.000
I answered that one first, I guess.
177
00:27:21.000 --> 00:27:27.000
I think the big one for this year is making sure that we transition out of being a single company,
178
00:27:27.000 --> 00:27:31.000
steward into a multi company foundation.
179
00:27:31.000 --> 00:27:32.000
Successfully.
180
00:27:32.000 --> 00:27:34.000
You know, it's a lot of voices.
181
00:27:34.000 --> 00:27:37.000
The founding partners all have different perspectives on thing.
182
00:27:37.000 --> 00:27:39.000
They've been great partners so far.
183
00:27:39.000 --> 00:27:42.000
But they all have different perspectives and different priorities.
184
00:27:42.000 --> 00:27:46.000
And so making sure that we're able to successfully take care of everybody.
185
00:27:46.000 --> 00:27:49.000
It's going to be a challenge for a framework that's never done that.
186
00:27:49.000 --> 00:27:52.000
I talk a lot when I talk about the story of the React Foundation.
187
00:27:52.000 --> 00:27:58.000
For those that don't know, it took over four years to get it done, which is a long time.
188
00:27:58.000 --> 00:28:02.000
And that's like a web standard.
189
00:28:02.000 --> 00:28:03.000
Twice that.
190
00:28:03.000 --> 00:28:06.000
Twice that for web standard.
191
00:28:06.000 --> 00:28:10.000
We were first looking at it and starting to like write, you know, put pen to paper.
192
00:28:10.000 --> 00:28:14.000
What we recognized pretty quickly was like the React team itself was not.
193
00:28:14.000 --> 00:28:17.000
Ed Metta was not ready to operate like a foundation.
194
00:28:17.000 --> 00:28:19.000
We were so used to Metta's tools.
195
00:28:19.000 --> 00:28:24.000
We were so used to being able to move at a breakneck speed and only like release what we had done.
196
00:28:24.000 --> 00:28:26.000
We've been using for two years.
197
00:28:26.000 --> 00:28:28.000
We release it two years later.
198
00:28:28.000 --> 00:28:33.000
And so there are a lot of different like points of dissonance when they came to being able to operate as a foundation.
199
00:28:33.000 --> 00:28:37.000
And so we pulled back from doing the foundation for a couple years and said let's fix.
200
00:28:37.000 --> 00:28:42.000
Let's fix everything internally first such that our interface boundary is better.
201
00:28:42.000 --> 00:28:43.000
That happened.
202
00:28:43.000 --> 00:28:51.000
Things like, you know, React Native went from releasing like on a very ad hoc schedule and not very often to doing six reliable releases a year.
203
00:28:51.000 --> 00:28:54.000
React core is like one solid release a year.
204
00:28:54.000 --> 00:29:00.000
And so and where it's like before you could be like, I, you know, I don't know when React is going to do a release.
205
00:29:00.000 --> 00:29:04.000
But you know, at least it's super backwards compatible, right?
206
00:29:04.000 --> 00:29:07.000
So like there's there's different equities people are bouncing.
207
00:29:07.000 --> 00:29:09.000
So that's kind of coming together.
208
00:29:09.000 --> 00:29:14.000
So the big goals this year is kind of to come back to your question really about like stability.
209
00:29:14.000 --> 00:29:17.000
Stabilizing React in a foundation.
210
00:29:17.000 --> 00:29:23.000
For the first time supporting financially maintainers events around the world communities.
211
00:29:23.000 --> 00:29:28.000
We want to help build communities where they're struggling to get those started because of resources.
212
00:29:28.000 --> 00:29:33.000
So things like for me, Asia is a big market that I want to expand to.
213
00:29:33.000 --> 00:29:38.000
We've never done a good job in Asia of localizing our documentation or reaching out to them.
214
00:29:38.000 --> 00:29:46.000
And then there's something like 10 million developers in China alone that are not counted in our surveys that are not among the people we target with things.
215
00:29:46.000 --> 00:29:52.000
So I really was just there in China and they are so excited about React and like we want to be involved.
216
00:29:52.000 --> 00:29:57.000
We want to help with stable API, which is the big project I'm excited about for React Native this year.
217
00:29:57.000 --> 00:30:02.000
That will empower more out of tree platforms, which I want to get rid of that term.
218
00:30:02.000 --> 00:30:07.000
All platforms are platforms that they want to be part of react. They're welcome.
219
00:30:07.000 --> 00:30:14.000
But we're going to basically rebuild the API layer such that the React Native things sit atop that as opposed to being forks.
220
00:30:14.000 --> 00:30:18.000
Every platform is a fork that's going to take a while.
221
00:30:18.000 --> 00:30:29.000
We're going to start on that this year such that the operating systems in China can use React just as easily as macOS, iOS, Android, and Windows.
222
00:30:29.000 --> 00:30:30.000
So there's a big ones.
223
00:30:30.000 --> 00:30:41.000
But the things I'm most excited about are actually starting to give back to the community because for too many years people have given so much blood sweat and tears to this project.
224
00:30:41.000 --> 00:30:46.000
And other than like accolades and appreciation, they haven't gotten a lot out of it.
225
00:30:46.000 --> 00:30:48.000
And so I really want to start turning that around.
226
00:30:48.000 --> 00:30:50.000
I want to see some new communities spring up.
227
00:30:50.000 --> 00:30:52.000
Those are the big ones for this year.
228
00:30:52.000 --> 00:30:55.000
Hopefully we can get React Comp again this year.
229
00:30:55.000 --> 00:31:01.000
The only reason that it's a hope and not a promise is that we want to make sure we have an event that's worth everybody attending.
230
00:31:01.000 --> 00:31:03.000
And so I'm in the process now.
231
00:31:03.000 --> 00:31:08.000
We're in the process now of curating what the program would be and making sure that it's up to the standards.
232
00:31:08.000 --> 00:31:11.000
The high standard that we set for React Comp.
233
00:31:11.000 --> 00:31:13.000
So yeah, those are the good ones.
234
00:31:13.000 --> 00:31:14.000
Nice.
235
00:31:14.000 --> 00:31:15.000
Yeah.
236
00:31:15.000 --> 00:31:24.000
So going back to your point a second ago about giving back to open source and stuff.
237
00:31:24.000 --> 00:31:34.000
Like do you think in general contributing to open source is helpful for your career?
238
00:31:34.000 --> 00:31:43.000
Like let me clarify, like directly contributes to getting hired somewhere versus is just like learning.
239
00:31:43.000 --> 00:31:45.000
Like you definitely learn from it.
240
00:31:45.000 --> 00:31:50.000
Do you think it like anyone goes, oh, I know that guy from open source.
241
00:31:50.000 --> 00:31:54.000
Let me hire him or like.
242
00:31:54.000 --> 00:32:00.000
I mean, I can think of dozens of examples of what you just described actually happening.
243
00:32:00.000 --> 00:32:01.000
Yeah.
244
00:32:01.000 --> 00:32:07.000
I think it would be pretty heavily biased if I just relied on those memories.
245
00:32:07.000 --> 00:32:12.000
So like anything else, yes, but it depends.
246
00:32:12.000 --> 00:32:19.000
It depends on your ability to network your ability to make sure that you're seen in that community.
247
00:32:19.000 --> 00:32:26.000
I think that there are a lot of unsung heroes in open source that are brilliant engineers.
248
00:32:26.000 --> 00:32:33.000
I have given just as much of themselves as other people, but nobody knows their name.
249
00:32:33.000 --> 00:32:34.000
Yeah.
250
00:32:34.000 --> 00:32:35.000
Nobody knows what they've done.
251
00:32:35.000 --> 00:32:43.000
And that's because they're not maybe into self promotion or someone else hasn't come along and sponsored them to say like,
252
00:32:43.000 --> 00:32:45.000
look at the great work this person is doing.
253
00:32:45.000 --> 00:32:46.000
Right.
254
00:32:46.000 --> 00:32:47.000
Everybody else know.
255
00:32:47.000 --> 00:32:50.000
And I think that you know, it's it's just like any other skill.
256
00:32:50.000 --> 00:32:53.000
You have to know how to make sure that your work is appreciated.
257
00:32:53.000 --> 00:32:54.000
Yeah.
258
00:32:54.000 --> 00:33:00.000
And there are too many people are focused on getting the work done and not being recognized.
259
00:33:00.000 --> 00:33:04.000
And it's sad in some ways that like you have to be promoting yourself.
260
00:33:04.000 --> 00:33:08.000
But if we're taking the lens of does it help me get hired?
261
00:33:08.000 --> 00:33:13.000
I think it does not by itself get you let you help you get hired in the last someone sponsors you.
262
00:33:13.000 --> 00:33:16.000
Or you are an advocate for yourself.
263
00:33:16.000 --> 00:33:21.000
And the not to open a whole can of worms that I'm going to get in trouble for.
264
00:33:21.000 --> 00:33:29.000
But I think the sort of newest generation of software developers that I've seen are not great itself promotion.
265
00:33:29.000 --> 00:33:31.000
They're not a great itself advocacy.
266
00:33:31.000 --> 00:33:32.000
Right.
267
00:33:32.000 --> 00:33:35.000
And need sponsorship more than ever.
268
00:33:35.000 --> 00:33:39.000
And so I would call upon those folks to develop that skill.
269
00:33:39.000 --> 00:33:44.000
But moreover, I would call on the engineers who are a little further in their career to be a sponsor.
270
00:33:44.000 --> 00:33:56.000
Be an advocate because it would be a shame to lose the kind of amazing engineering into the shadows that we're seeing from some of these folks because they didn't have someone.
271
00:33:56.000 --> 00:33:59.000
You know, vocalizing for them that they're doing good work.
272
00:33:59.000 --> 00:34:08.000
So advocacy and all is always been an important part of every career for every person always needed somebody to give them an opportunity.
273
00:34:08.000 --> 00:34:12.000
And this is the opportunity we have to advocate for people.
274
00:34:12.000 --> 00:34:20.000
Yeah, yeah, it's always been a problem of like, you know, there's every every few years somebody blows up like the fake or JS thing was a big thing.
275
00:34:20.000 --> 00:34:25.000
Or like, you know, somebody's like, hey, all these companies are using my thing for free and giving me no money.
276
00:34:25.000 --> 00:34:27.000
And I've spent a ton of time on it.
277
00:34:27.000 --> 00:34:29.000
It's like, yeah, there's got to be a fix for that.
278
00:34:29.000 --> 00:34:31.000
But there's I want to fix that problem.
279
00:34:31.000 --> 00:34:37.000
And I also want to fix the problem of, you know, AI code Providence.
280
00:34:37.000 --> 00:34:45.000
I mean, like the the elements are spitting out full copies of open source libraries rather than pulling them off the shelf.
281
00:34:45.000 --> 00:34:47.000
And I think we have to fix that.
282
00:34:47.000 --> 00:34:50.000
I think we also have to fix.
283
00:34:50.000 --> 00:34:59.000
For example, I mean, if you think about it from reacts perspective and I'm not somebody who spends time wasting my energy on being frustrated.
284
00:34:59.000 --> 00:35:09.000
But if you think about, if you go and you ask cloud or any of these systems pretty much to build you any commerce website, what technology will they use?
285
00:35:09.000 --> 00:35:11.000
With that sentence, they'll use react.
286
00:35:11.000 --> 00:35:12.000
Yeah.
287
00:35:12.000 --> 00:35:14.000
And they'll use probably next.
288
00:35:14.000 --> 00:35:19.000
You used to be tailwind, but they also, they don't necessarily love tailwind as much anymore.
289
00:35:19.000 --> 00:35:23.000
I hope that's not true.
290
00:35:23.000 --> 00:35:29.000
But, you know, react isn't seeing anything from open AI or or anthropic.
291
00:35:29.000 --> 00:35:32.000
And no one is so rampant theft of everything.
292
00:35:32.000 --> 00:35:33.000
Exactly.
293
00:35:33.000 --> 00:35:39.000
And so even, you know, even the big ones like us are struggling with the same problem as the small ones.
294
00:35:39.000 --> 00:35:44.000
And I think that as an industry, we need to stand together and figure out how to solve this problem.
295
00:35:44.000 --> 00:35:46.000
I don't have any good solutions for you.
296
00:35:46.000 --> 00:35:54.000
Like the things I'm thinking about are, as we talked about earlier, like cloud and codex and other code agents.
297
00:35:54.000 --> 00:35:57.000
They don't write very good react code.
298
00:35:57.000 --> 00:36:06.000
Can we provide the e-vows, can we provide the post training data or pre training data to help generate code that is performance?
299
00:36:06.000 --> 00:36:11.000
It's not using refs for state tracking because it doesn't like our life cycle and so forth.
300
00:36:11.000 --> 00:36:18.000
So, you know, there's opportunities there, I think maybe to partner with the AI companies in order to develop,
301
00:36:18.000 --> 00:36:21.000
help them develop products that are better for their customers.
302
00:36:21.000 --> 00:36:23.000
And then it's a win-win, right?
303
00:36:23.000 --> 00:36:29.000
So I'm looking, trying to look at it from different angles and see, you know, how can we all benefit from this?
304
00:36:29.000 --> 00:36:31.000
You know, it does feel like a gold rush, right?
305
00:36:31.000 --> 00:36:34.000
It feels like this vibrant, this energy is just percolating everywhere.
306
00:36:34.000 --> 00:36:36.000
It feels like a really good time.
307
00:36:36.000 --> 00:36:43.000
But it's also important that we keep our minds and keep ourselves focused on the outcomes that affect human beings.
308
00:36:43.000 --> 00:36:45.000
And this is what I said earlier too.
309
00:36:45.000 --> 00:36:54.000
It's like, you can look at the efficiency gains you get from your engineers at your company using AI as an opportunity to save money.
310
00:36:54.000 --> 00:37:03.000
I think the smart money is on using the opportunity and the efficiency that you're saving to do more of the things you've been unable to do throughout the years
311
00:37:03.000 --> 00:37:06.000
because you have to make hard decisions of prioritization.
312
00:37:06.000 --> 00:37:10.000
You still have to be good about prioritizing, but I think this opens the door to like,
313
00:37:10.000 --> 00:37:14.000
explore those business vectors that you've not been prioritizing because you were scared.
314
00:37:14.000 --> 00:37:16.000
Like, now you can do it. Now you can afford it.
315
00:37:16.000 --> 00:37:21.000
You have 10 times as much money as you did before because you're engineers with 10 times more valuable.
316
00:37:21.000 --> 00:37:24.000
Yeah. So, laying people off is not the way to save money.
317
00:37:24.000 --> 00:37:28.000
It's build more, like Adam and I talked about this a lot of like,
318
00:37:28.000 --> 00:37:30.000
you probably have a lot of SaaS products you use, right?
319
00:37:31.000 --> 00:37:33.000
Make a whole team, have them build that.
320
00:37:33.000 --> 00:37:34.000
That'll save you some money.
321
00:37:34.000 --> 00:37:39.000
Like firing people is such a short-sighted way of saving money.
322
00:37:39.000 --> 00:37:40.000
Yeah.
323
00:37:40.000 --> 00:37:41.000
I agree.
324
00:37:41.000 --> 00:37:45.000
I think also the thing you just said,
325
00:37:45.000 --> 00:37:48.000
it's something like I worry about a little bit which is like,
326
00:37:48.000 --> 00:37:51.000
how will I reshape the SaaS market?
327
00:37:51.000 --> 00:37:54.000
There's so many brilliant tools out there that...
328
00:37:54.000 --> 00:37:56.000
Yeah, like clerk. Check it out.
329
00:37:56.000 --> 00:37:59.000
Like, I'm a clerk, I'm a clerk customer.
330
00:37:59.000 --> 00:38:00.000
Yeah.
331
00:38:00.000 --> 00:38:03.000
But I have, I have also rolled my own off.
332
00:38:03.000 --> 00:38:06.000
I've been in a lot of customer, a lot of zero customers as well.
333
00:38:06.000 --> 00:38:13.000
And I just like so, you know, not wanting to go through the experience of setting up off,
334
00:38:13.000 --> 00:38:14.000
setting up off again.
335
00:38:14.000 --> 00:38:18.000
I'm like, I'm just going to do magic links and that's it because it's easy.
336
00:38:18.000 --> 00:38:21.000
But then you guys decided to add billing and I was like,
337
00:38:22.000 --> 00:38:24.000
now I'm like, now I'm like interested again, right?
338
00:38:24.000 --> 00:38:25.000
Yeah.
339
00:38:25.000 --> 00:38:28.000
But I have a few apps running with clerk and a great job.
340
00:38:28.000 --> 00:38:31.000
I mean, what a great product clerk is.
341
00:38:31.000 --> 00:38:36.000
I wonder if we can learn from the music industry here where they kind of went off the wall
342
00:38:36.000 --> 00:38:40.000
where if you play eight seconds of a song, you got to open ease to the artists.
343
00:38:40.000 --> 00:38:43.000
And there's an amount of that that feels pretty silly.
344
00:38:43.000 --> 00:38:47.000
But at the same time, at least they're giving attribution and paying back
345
00:38:47.000 --> 00:38:49.000
for using somebody else's stuff.
346
00:38:50.000 --> 00:38:52.000
And I've been sent DMs already, which people said,
347
00:38:52.000 --> 00:38:55.000
hey, I invoked this LLM to make a design.
348
00:38:55.000 --> 00:39:00.000
And I literally saw your name show up in the results of either the styles that were written
349
00:39:00.000 --> 00:39:03.000
or my name was in the HTML that was producing stuff like that.
350
00:39:03.000 --> 00:39:07.000
And I'm like, I don't think I want pennies to start trickling towards me or whatever.
351
00:39:07.000 --> 00:39:10.000
But, you know, CSS tricks did the same thing.
352
00:39:10.000 --> 00:39:15.000
Chris Coyers, like I built 10 years of CSS content for LLMs to strip it and steal it
353
00:39:15.000 --> 00:39:17.000
in a couple of days and give me nothing.
354
00:39:17.000 --> 00:39:21.000
So we got the music industry that's like got trolls to pop up over all these bridges
355
00:39:21.000 --> 00:39:24.000
and they go, yeah, you used a fraction of our song.
356
00:39:24.000 --> 00:39:27.000
You know, you must pay BMG or whatever it is.
357
00:39:27.000 --> 00:39:28.000
I don't want to do that.
358
00:39:28.000 --> 00:39:33.000
But I wonder if there is something that we can learn from them as being sort of too far
359
00:39:33.000 --> 00:39:34.000
in that pendulum swing.
360
00:39:34.000 --> 00:39:36.000
Maybe AI can do something else.
361
00:39:36.000 --> 00:39:39.000
And yeah, instead of taking the money that you're saving and you're enhancing
362
00:39:39.000 --> 00:39:45.000
and pocketing it as a big company, giving some of that back to what you clearly are borrowing.
363
00:39:46.000 --> 00:39:47.000
I don't know.
364
00:39:47.000 --> 00:39:50.000
Yeah, I mean, I think it's definitely something I want to work on figuring out.
365
00:39:50.000 --> 00:39:53.000
I'm in a good position to do so at the foundation.
366
00:39:53.000 --> 00:39:58.000
So for context, those that don't know, Linux, Linux Foundation is the parent company
367
00:39:58.000 --> 00:40:00.000
of React Foundation now.
368
00:40:00.000 --> 00:40:05.000
And one of the big efforts they've started this year is the Agente AI Foundation,
369
00:40:05.000 --> 00:40:10.000
which is looking at way more than this, but looking at all of these types of things.
370
00:40:11.000 --> 00:40:16.000
You know, if you take a step back and you think about those of us who've spent a long career
371
00:40:16.000 --> 00:40:22.000
in the developer tooling space, we are excited about helping other people build things.
372
00:40:22.000 --> 00:40:29.000
And so I don't need the pennies to trickle into me because I am the executive director of the React Foundation.
373
00:40:29.000 --> 00:40:33.000
What I want is for the developers who built the code that Claude was trained on
374
00:40:33.000 --> 00:40:38.000
to be rewarded for the energy and effort and time and lifetime minutes they spent on that.
375
00:40:38.000 --> 00:40:42.000
Because my whole North Star was helping other people bring their ideas to life,
376
00:40:42.000 --> 00:40:48.000
in this case, helping other people bring their ideas to life that help other people bring their ideas to life,
377
00:40:48.000 --> 00:40:52.000
that, like I said, that chain of providence has to be preserved,
378
00:40:52.000 --> 00:40:58.000
such that people can be at the bare minimum recognized for their contributions.
379
00:40:58.000 --> 00:41:01.000
And in a better world rewarded for those contributions.
380
00:41:01.000 --> 00:41:04.000
You know, rewarding record recognition, go hand in hand.
381
00:41:05.000 --> 00:41:10.000
And I think that, you know, I think we can all agree, I don't know if this is true,
382
00:41:10.000 --> 00:41:16.000
but I think we can all agree that from helping people bring the ideas into the world perspective,
383
00:41:16.000 --> 00:41:18.000
AI is a huge unlock.
384
00:41:18.000 --> 00:41:24.000
And as somebody who's spent a career helping people do that, I'm so inspired and excited about this arrow.
385
00:41:24.000 --> 00:41:28.000
But it comes with these trade-offs that I think we have to reckon with.
386
00:41:28.000 --> 00:41:32.000
Otherwise, what will we be building upon 10 years from now?
387
00:41:32.000 --> 00:41:36.000
You know, it won't be novel, it won't be innovative, it won't be exciting.
388
00:41:36.000 --> 00:41:39.000
It'll be, again, back to what I talked about in my talk this morning,
389
00:41:39.000 --> 00:41:41.000
regurgitation of the same ideas over and over.
390
00:41:41.000 --> 00:41:42.000
Yeah.
391
00:41:42.000 --> 00:41:46.000
I could sit in a different, in a form, but it's still just all, you know, shitty ice cream.
392
00:41:46.000 --> 00:41:50.000
So I really want to see us, I really want to see us figure this problem out.
393
00:41:50.000 --> 00:41:54.000
I call that the mainstream just getting wider, where you've got a mainstream,
394
00:41:54.000 --> 00:41:58.000
and it's popular, but as we regurgitate more and more mainstream,
395
00:41:58.000 --> 00:42:02.000
the mainstream just gets wider, and the indies and the edges get smaller and smaller.
396
00:42:02.000 --> 00:42:03.000
That's true.
397
00:42:03.000 --> 00:42:05.000
And I think that's dangerous.
398
00:42:05.000 --> 00:42:08.000
The same way that you don't want pure factories, or you don't want pure craft.
399
00:42:08.000 --> 00:42:11.000
There's always a healthy middle ground here, and we've got to find some balance.
400
00:42:11.000 --> 00:42:13.000
So I'm happy to hear you say that, man.
401
00:42:13.000 --> 00:42:17.000
I do think there's a lot of catching up we have to do as an industry.
402
00:42:17.000 --> 00:42:23.000
Like, you know, Adam made a nice marketing page for us the other day.
403
00:42:23.000 --> 00:42:29.000
We have a couple of prompts done better than, like, in my opinion, our website.
404
00:42:29.000 --> 00:42:35.000
So I was like, huh, like, when that's that good, and there's still websites that suck,
405
00:42:35.000 --> 00:42:40.000
it's like, that we need to just raise everybody up to that good level first.
406
00:42:40.000 --> 00:42:41.000
Let's work on that.
407
00:42:41.000 --> 00:42:43.000
Then we can figure out what's next.
408
00:42:43.000 --> 00:42:44.000
I agree.
409
00:42:44.000 --> 00:42:47.000
You know, I think we've talked a lot about this at Expo too.
410
00:42:47.000 --> 00:42:51.000
It's like, what's going to be the differentiating factor in the future?
411
00:42:51.000 --> 00:42:54.000
Or now the future is now the future is here.
412
00:42:54.000 --> 00:43:02.000
And I think it still comes down to like taste, you know, knowing what you want to create
413
00:43:02.000 --> 00:43:05.000
and what you want to be different about that.
414
00:43:05.000 --> 00:43:07.000
And I think that that's going to be a big one.
415
00:43:07.000 --> 00:43:13.000
I think longevity and stability are going to be things that are going to be highly prized and valued,
416
00:43:13.000 --> 00:43:15.000
you know, sticking around.
417
00:43:15.000 --> 00:43:17.000
It's going to be harder than it used to be.
418
00:43:17.000 --> 00:43:21.000
Like, entire market verticals are going to get saturated with players.
419
00:43:21.000 --> 00:43:24.000
And at that point, like, how do you differentiate it?
420
00:43:24.000 --> 00:43:32.000
If every hotel has the same or like, really similar or like, really awesome digital experiences,
421
00:43:32.000 --> 00:43:35.000
how will they differentiate themselves from one another?
422
00:43:35.000 --> 00:43:39.000
You know, remember when we got the phone based hotel room key,
423
00:43:39.000 --> 00:43:43.000
and like, only a couple to it and it's helping or whatever that has this, it's awesome.
424
00:43:43.000 --> 00:43:47.000
But if every place has that, you're not going to feel like, oh, that's so cool anymore, right?
425
00:43:47.000 --> 00:43:49.000
It's just like, why find an airplane the first time you ever used it?
426
00:43:49.000 --> 00:43:52.000
You're like, oh, I got to just shift the diff from 30,000 feet.
427
00:43:52.000 --> 00:43:53.000
That's so cool.
428
00:43:53.000 --> 00:43:56.000
And now you're grumpy anytime it doesn't work, right?
429
00:43:56.000 --> 00:43:57.000
You're not amazed by it anymore.
430
00:43:57.000 --> 00:43:58.000
You're just grumpy.
431
00:43:58.000 --> 00:44:04.000
And so we're going to get to that same place, I think, with the saturation in every niche,
432
00:44:04.000 --> 00:44:11.000
which I'm hopeful about because I think what it does is it pushes us back into the analog world of differentiation.
433
00:44:11.000 --> 00:44:15.000
It puts us, pushes us to reach different heights of differentiation.
434
00:44:15.000 --> 00:44:17.000
The weird web, right?
435
00:44:17.000 --> 00:44:21.000
Yeah, going back to Photoshop slices and throwing it all on the floor.
436
00:44:21.000 --> 00:44:23.000
Please God, no.
437
00:44:23.000 --> 00:44:26.000
That is, I don't want to slice any corners.
438
00:44:26.000 --> 00:44:31.000
But I think there's a really interesting shift coming because we're going to democratize
439
00:44:31.000 --> 00:44:35.000
so much more of this development that tastes and differentiation is going to be even more huge.
440
00:44:35.000 --> 00:44:39.000
And I'm hopeful that it actually pushes us back to some degree into the analog world
441
00:44:39.000 --> 00:44:43.000
where I think differentiation matters much more.
442
00:44:43.000 --> 00:44:44.000
Yeah.
443
00:44:44.000 --> 00:44:49.000
Yeah, I hadn't considered, like, the sole way I decide is this resort dope.
444
00:44:49.000 --> 00:44:51.000
I'm like, is the website really good?
445
00:44:51.000 --> 00:44:56.000
If you put a lot of money into the website, then I know you probably put a lot of money into your experience there.
446
00:44:56.000 --> 00:44:58.000
So if everyone gets that, then yeah, you're right.
447
00:44:58.000 --> 00:45:01.000
It's like, how do I know if it's a good one or not?
448
00:45:01.000 --> 00:45:02.000
Exactly.
449
00:45:02.000 --> 00:45:04.000
You're all going to know by trying.
450
00:45:04.000 --> 00:45:05.000
Yeah.
451
00:45:05.000 --> 00:45:09.000
There is high correlation between a well thought out website where the content is there.
452
00:45:09.000 --> 00:45:12.000
It's beautiful and the experience that you get somewhere.
453
00:45:12.000 --> 00:45:15.000
So I don't think that's ever bit me really where I've gone to a beautiful website.
454
00:45:15.000 --> 00:45:18.000
And then I showed up to the brick and mortar store and I'm like, what the?
455
00:45:18.000 --> 00:45:20.000
I feel like that's a movie in the making.
456
00:45:20.000 --> 00:45:23.000
I think I should write that.
457
00:45:23.000 --> 00:45:24.000
Yeah.
458
00:45:24.000 --> 00:45:25.000
All right.
459
00:45:25.000 --> 00:45:26.000
We are about at time here.
460
00:45:26.000 --> 00:45:27.000
Is there anything that we miss?
461
00:45:27.000 --> 00:45:30.000
Do you want to mention plug, etc?
462
00:45:30.000 --> 00:45:39.000
If you have any interest for everybody out there, if you have any interest in participating in the activities at the foundation, definitely let us know.
463
00:45:39.000 --> 00:45:41.000
There's a ton of great stuff, you know, reach out to me.
464
00:45:41.000 --> 00:45:44.000
You can, there's a contact form on the website.
465
00:45:44.000 --> 00:45:46.000
That generally goes to me.
466
00:45:46.000 --> 00:45:47.000
So reach out.
467
00:45:47.000 --> 00:45:48.000
I'd love to hear from you.
468
00:45:48.000 --> 00:45:51.000
There's a lot of activities that we need help with on the website.
469
00:45:51.000 --> 00:45:59.000
I mean, on the, at the foundation, the last thing I'd say is like, I really want to encourage folks to consider this moment.
470
00:45:59.000 --> 00:46:04.000
Like a call to action to start building.
471
00:46:04.000 --> 00:46:08.000
I don't think we need to have 70 million of the same things out there.
472
00:46:08.000 --> 00:46:18.000
But getting really good at commanding agents and commanding your fleet of agents and learning how to parallelize your work and learning how to work on five or six different things in the same day at the same time is not a skill.
473
00:46:18.000 --> 00:46:22.000
A lot of engineers have who were much more used to going deep and focusing.
474
00:46:22.000 --> 00:46:25.000
So start practicing this because this is where the industry is going.
475
00:46:25.000 --> 00:46:30.000
And it's, you know, the way I think about it right now is there's never been a better time to be a builder.
476
00:46:30.000 --> 00:46:40.000
And so I'd love to see, you know, many more ideas, you know, leverage expo, leverage these framers, leverage and acts, leverage, you know, tan stack, whatever your, whatever your favorite is.
477
00:46:40.000 --> 00:46:47.000
To get your idea out there and get it into hands because you're not going to learn so much more by actually shipping something.
478
00:46:47.000 --> 00:46:53.000
Especially if it's a project of passion for yourself, then you will, uh, by reading blogs, sitting there reading blogs about air.
479
00:46:53.000 --> 00:46:59.000
Or just get your hands dirty, get in there, make all the mistakes we're all making and help us figure out this next air of software development.
480
00:46:59.000 --> 00:47:00.000
Hell yeah.
481
00:47:00.000 --> 00:47:01.000
Love that.
482
00:47:01.000 --> 00:47:02.000
Yeah.
483
00:47:02.000 --> 00:47:03.000
I got one final request though.
484
00:47:03.000 --> 00:47:04.000
All right.
485
00:47:04.000 --> 00:47:07.000
Will you say whiskey, web and whatnot in your dope ass voice?
486
00:47:07.000 --> 00:47:14.000
You're listening to whiskey, web and whatnot and react by me.
487
00:47:14.000 --> 00:47:15.000
Yeah.
488
00:47:15.000 --> 00:47:16.000
Nice.
489
00:47:16.000 --> 00:47:18.000
Is it all right?
490
00:47:18.000 --> 00:47:19.000
Thanks guys.
491
00:47:19.000 --> 00:47:20.000
It was really great to be here.
492
00:47:20.000 --> 00:47:21.000
Oh my gosh.
493
00:47:21.000 --> 00:47:22.000
Yeah. Thanks for coming on.
494
00:47:22.000 --> 00:47:23.000
Thanks everyone for listening.
495
00:47:23.000 --> 00:47:25.000
If you liked it, please subscribe, leave some comments and reviews.
496
00:47:25.000 --> 00:47:26.000
We appreciate it.
497
00:47:26.000 --> 00:47:29.000
And we will catch you in, well, I would say next time, but in a few minutes because we'll be back on.
498
00:47:29.000 --> 00:47:30.000
Yeah.
499
00:47:30.000 --> 00:47:31.000
With some other, some other requests.
500
00:47:31.000 --> 00:47:32.000
Yes, indeed.
501
00:47:32.000 --> 00:47:33.000
All right.
502
00:47:33.000 --> 00:47:34.000
This is great.
503
00:47:34.000 --> 00:47:36.000
Congratulations, citizen.
504
00:47:36.000 --> 00:47:40.000
You are now prepared to face the challenges of the modern technological world.
505
00:47:40.000 --> 00:47:48.000
With the proper tools, a steady hand and a reasonably configured terminal, any developer can orchestrate AI agents with confidence.
506
00:47:48.000 --> 00:47:50.000
You'll do just fine.
507
00:47:50.000 --> 00:47:55.000
Thank you for listening to whiskey, web and whatnot, the world's most important AI podcast.
508
00:47:55.000 --> 00:48:00.000
For additional resources including official merchandise, visit whiskey.fund.
509
00:48:00.000 --> 00:48:09.000
And remember to subscribe, rate and review so this vital information may reach others because the future of technology depends on it.
510
00:48:10.000 --> 00:48:12.000
You
