AI Can’t Replace Juniors - AWS CEO - CourtneyR.dev's 2nd Brain

"AI Can’t Replace Juniors" - AWS CEO 🔗 **Source:** ["AI Can’t Replace Juniors" - AWS CEO](https://www.youtube.com/watch?v=fP5URbP30j0) > [!note]+ Document Notes > tags: [ai-development, software-engineering, workforce-strategy] > author: ThePrimeagen > source: YouTube > reference: https://www.youtube.com/watch?v=fP5URbP30j0 > date created: 2024-12-19 14:30 > > # 🏷️ Title: AI Can't Replace Juniors - AWS CEO >  ## 🧰 Action Inbox - [H1] Evaluate junior developer hiring strategy against AI replacement pressure — 00:00 #workforce - [H2] Document knowledge transfer processes for junior to senior progression — 08:15 #mentorship - [H3] Build systems for exploration and iteration over pure efficiency — 12:30 #innovation ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - [Original Video](https://www.youtube.com/watch?v=fP5URbP30j0) ## 📝 Summary - AWS CEO Matt Garman pushes back against AI hype by defending junior developer value - Contrasts with aggressive AI replacement narratives from other tech leaders - Why quality software requires human exploration, iteration, and genuine care - Companies that rush to replace juniors with AI will likely face hiring backlash - Bottom line: Junior devs provide irreplaceable value through curiosity, adaptability, and genuine investment in products ## 📖 Main Content ThePrimeagen examines AWS CEO Matt Garman's contrarian stance on AI replacing junior developers, positioning it against the broader tech industry's "embrace AI or die" mentality. While companies like Microsoft struggle with broken core features despite AI advancements, Garman argues that replacing junior developers with AI is fundamentally misguided. Garman provides three reasons: junior devs often know AI tools better, they shouldn't be the default cost-cutting target, and removing them breaks the talent pipeline. However, ThePrimeagen argues the real value lies in junior developers' ability to explore, iterate, and grow into collaborative partners who can read between the lines and contribute genuine innovation. The core tension is between quantity and quality - while AI can help produce more code faster, it requires precise problem specification, whereas junior developers can navigate ambiguity, explore wrong paths to find right solutions, and develop emotional investment in products that leads to unexpected improvements. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/fP5URbP30j0?t=0) — [H1] Cold water on AI hype beasts - Key idea: Channel consistently challenges all-or-nothing AI replacement narratives - Evidence: "3 to 6 months 90% of all code will be just written by AI" - prediction from 9 months ago that hasn't materialized #### ⏱️ [01:30](https://youtu.be/fP5URbP30j0?t=90) — [H2] Golden age paradox - Key idea: Highest quantity of software ever written, yet lowest quality - Evidence: "Microsoft finally admits almost all major Windows 11 core features are broken" #### ⏱️ [02:45](https://youtu.be/fP5URbP30j0?t=165) — [H1] AWS CEO's contrarian stance - Key idea: Matt Garman calls AI replacing juniors "one of the dumbest things I've heard" - Evidence: Response to leadership group suggesting AI can replace all junior employees #### ⏱️ [04:15](https://youtu.be/fP5URbP30j0?t=255) — [H2] Garman's first reason: AI tool knowledge - Key idea: Junior devs supposedly know AI tools better than seniors - Evidence: ThePrimeagen finds this reasoning "lackluster" - usage doesn't equal expertise #### ⏱️ [05:00](https://youtu.be/fP5URbP30j0?t=300) — [H2] Garman's second reason: Cost-saving fallacy - Key idea: Junior developers shouldn't be default cost-cutting targets - Evidence: "30% of companies that laid off workers expecting savings ended up increasing expenses" #### ⏱️ [05:45](https://youtu.be/fP5URbP30j0?t=345) — [H1] Garman's third reason: Talent pipeline - Key idea: Removing juniors breaks long-term talent development - Evidence: Without junior hires today, teams struggle to fill roles tomorrow #### ⏱️ [06:30](https://youtu.be/fP5URbP30j0?t=390) — [H2] Historical precedent from 2010s - Key idea: Developer shortage led to wage inflation when pipeline broke - Evidence: Post-dotcom boom recovery created scarcity and higher costs #### ⏱️ [08:15](https://youtu.be/fP5URbP30j0?t=495) — [H1] The exploration and growth value - Key idea: Junior devs explore problems and evolve into collaborative partners - Evidence: "They actually cared about the product... had emotional investment in making the place better" #### ⏱️ [09:30](https://youtu.be/fP5URbP30j0?t=570) — [H2] Reading between the lines - Key idea: Juniors grow from executing orders to understanding intent and improving solutions - Evidence: "Instead of just simply being someone that does exactly what I say... they start making changes that are not what I'm saying" #### ⏱️ [10:15](https://youtu.be/fP5URbP30j0?t=615) — [H1] AI's fundamental limitation - Key idea: AI requires accurate problem description, but that's the core challenge - Evidence: "The moment PMs can accurately describe a problem is the day that software development no longer exists, which by the way is never" #### ⏱️ [11:00](https://youtu.be/fP5URbP30j0?t=660) — [H2] Value multiplication through communication - Key idea: Junior devs become collaborative partners who can discuss ideas and see unrealized possibilities - Evidence: Individual communication, idea bouncing, seeing things that "don't currently exist and weren't even spoken of" #### ⏱️ [12:30](https://youtu.be/fP5URbP30j0?t=750) — [H1] Necessity of doing wrong things - Key idea: Understanding right solutions requires exploring wrong approaches first - Evidence: Harpoon plugin example - "built so many different versions... trying to figure out how I wanted to navigate" #### ⏱️ [13:15](https://youtu.be/fP5URbP30j0?t=795) — [H2] Problem identification vs code writing - Key idea: Real challenge is understanding what problem to solve, not implementation speed - Evidence: "It was almost never a problem of writing code. It was a problem of understanding what the right problem is to solve" #### ⏱️ [14:00](https://youtu.be/fP5URbP30j0?t=840) — [H1] Quality over quantity thesis - Key idea: Software needs enthusiasm and exploration, not just faster code production - Evidence: "We don't have a quantity problem. We have a quality problem" ## 📚 References - [AI Can't Replace Juniors - AWS CEO](https://www.youtube.com/watch?v=fP5URbP30j0) ## 🗣️ Paraphrase - AWS CEO Matt Garman challenges the tech industry's rush to replace junior developers with AI, calling it fundamentally misguided - While AI can increase code quantity, junior developers provide irreplaceable value through exploration, growth, and genuine product investment - The real software development challenge is problem identification and iteration, not code generation speed ## 📰 Newsletter The AWS CEO just dropped some serious wisdom that WordPress developers need to hear. While everyone's panicking about AI replacing junior devs, Matt Garman reminds us why fresh perspectives and growth mindsets matter more than code generation speed. Think about your WordPress projects - the magic happens when team members explore, iterate, and genuinely care about user experience. That's not something you can prompt-engineer. For WordPress teams: invest in junior developers who can learn your codebase, understand your users, and grow into collaborative partners. They'll read between the lines of your feature requests and surprise you with solutions you never imagined. Resources: [Learn WordPress](https://learn.wordpress.org/), [Developer Docs](https://developer.wordpress.org/), [WP-CLI](https://wp-cli.org/) ## ✅ Action Items #### DevRel - Developer advocacy: Create content defending junior developer value against AI replacement narratives, metrics on mentorship ROI - Education: Design junior-to-senior progression workshops, document exploration methodologies - Developer experience: Build onboarding that emphasizes problem exploration over code generation - Developer marketing: Campaign highlighting human creativity and iteration in software quality - Community management: Foster mentorship programs, junior developer showcases #### Community - Maintainers: Create junior-friendly first issues that require exploration and iteration - Contributors: Develop mentorship matching programs for senior-junior collaboration - Sponsors: Fund junior developer stipends and exploration time rather than just code production #### WordPress - Core: Establish junior contributor pathways that emphasize understanding over implementation speed - Community: Design mentorship tracks at WordCamps focused on problem exploration - Training: Create curricula that balance AI tool usage with human creativity and iteration - Design: Include junior perspectives in UX research and iterative design processes - Documentation: Develop guides for effective junior-senior collaboration patterns ## 🧪 Hypotheses - Companies that maintain junior developer pipelines during AI hype will have competitive advantages in 3-5 years - Software quality correlates more with exploration and iteration processes than code generation speed - Junior developers provide unique value in problem identification that AI cannot replicate - Organizations that replace juniors with AI will face higher rehiring costs within 18 months ### 📊 Methodology - Longitudinal study comparing software quality metrics between AI-first and junior-inclusive teams - Survey analysis of companies that eliminated junior roles and their subsequent hiring patterns - Case studies of successful junior-to-senior progression in high-quality software organizations ### ❓ Questions - How do we measure the exploration and iteration value that junior developers provide? - What specific mentorship structures maximize junior developer growth into collaborative partners? - How can organizations balance AI efficiency with human creativity and problem exploration? ### 🔮 Future Research - Long-term career progression patterns in AI-augmented development environments - Quantitative analysis of software quality correlation with team experience diversity - Cross-industry comparison of talent pipeline strategies during technological transitions ### 💡 Implications - Practice: Develop structured mentorship and exploration processes for junior developers - Policy: Resist pressure to eliminate junior roles based on AI capabilities alone - Education: Emphasize problem identification and iteration skills alongside technical implementation - Funding: Investment in long-term talent pipelines over short-term cost cutting ### 🧠 Learning Styles Assessment Reading level estimate: Flesch-Kincaid Grade Level 9 #### 👀 Visual learners - Present: Video format with speaker emphasis and examples - Improve: Career progression diagrams, AI vs human capability comparisons #### 🔊 Aural learners - Present: Audio commentary and discussion format - Improve: Interview segments with junior developers sharing experiences #### 🗣️ Verbal learners - Present: Clear definitions of junior vs senior value, concrete examples - Improve: Glossary of mentorship terms, analogy-driven explanations #### 🧩 Kinesthetic learners - Present: Concrete code exploration examples (Harpoon plugin development) - Improve: Hands-on mentorship exercises, problem exploration workflows #### 🧠 Logical learners - Present: Statistical evidence on rehiring costs, historical precedents - Improve: Decision frameworks for hiring vs AI investment, ROI calculations #### 🧑‍🤝‍🧑 Social learners - Present: Discussion of team dynamics and collaboration - Improve: Group mentorship models, peer learning structures #### 🧘‍♀️ Solitary learners - Present: Individual reflection on career development and growth - Improve: Self-assessment tools for mentorship readiness #### 🌿 Naturalistic learners - Present: Ecosystem thinking about talent pipelines and industry health - Improve: Sustainability models for software development careers ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Video has clear spoken content structure - Improve: Detailed transcript with speaker identification, heading structure #### Keyboard navigation - Present: Standard YouTube player accessibility - Improve: Chapter navigation, timestamp accessibility #### Contrast and readability - Present: High contrast video player interface - Improve: Transcript formatting with sufficient contrast ratios #### Text resizing and reflow - Present: Responsive video player design - Improve: Scalable transcript text, mobile-friendly formatting #### Media and captions - Present: Auto-generated captions available - Improve: Human-reviewed captions, downloadable transcript #### Forms and interactions - Present: Standard video controls - Improve: Custom playback speed controls, bookmark functionality ### 🌍 DEIB Assessment #### Cultural breadth - Present: Tech industry perspective from major platform (AWS) - Improve: Global examples of mentorship models, non-US tech perspectives #### Inclusive language - Present: Gender-neutral development terminology - Improve: Avoid military metaphors ("command a fleet"), more inclusive team language #### Neurodiversity support - Present: Clear logical structure and concrete examples - Improve: Multiple explanation formats, reduced aggressive language #### Representation - Present: Discussion of diverse career paths in tech - Improve: Highlight underrepresented groups in junior development roles #### Psychological safety - Present: Defensive stance for junior developers against replacement fears - Improve: Content warnings for job security anxiety, supportive framing ### ✅ Logical Validity #### Strong reasoning - Deductive strength: If AI requires precise problem specification and PMs cannot provide this, then AI cannot replace problem-solving developers - Inductive strength: Historical pattern of developer shortages leading to wage inflation supports talent pipeline argument - Causal reasoning: Clear connection between junior developer growth and collaborative value creation - Analogical strength: Harpoon plugin development example effectively illustrates exploration necessity #### Fallacies - Ad hominem: Attacking "AI hype beasts" and CEOs rather than addressing their arguments directly - Appeal to authority: Using AWS CEO status as primary credibility without examining reasoning quality #### Tone of voice - Overall tone: Combative and dismissive toward AI proponents, protective of developer community, uses humor and mild profanity for engagement ### 🛡️ DARVO Analysis - Deny: No denial patterns present - Attack: Attacks on "AI overlord hype beasts" and dismissive language toward opposing viewpoints - Reverse victim/offender: No victim/offender reversal detected - Emotional cues and rhetoric: Strong protective stance for junior developers, uses humor and community solidarity to build argument ## 🎯 Conclusion The AWS CEO's defense of junior developers cuts through AI hype to highlight fundamental software development realities. While AI can accelerate code production, the core challenges remain problem identification, exploration, and iteration - areas where human creativity and growth mindset provide irreplaceable value. Organizations should resist the temptation to eliminate junior roles based on AI capabilities alone, instead focusing on developing mentorship structures that maximize both human potential and AI augmentation for long-term competitive advantage. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad Purpose: Stage CEE units that become Literature notes. Split level: H3 ### [H1] AI requires precise problem specification but PMs cannot provide this > [!quote] AI Can't Replace Juniors - AWS CEO by [[ThePrimeagen]] via [[YouTube]]. Published 2024-12-19. Accessed 2024-12-19. > "The moment PMs can accurately describe a problem is the day that software development no longer exists, which by the way is never." Core limitation of AI in software development - dependency on accurate problem description when problem identification is the fundamental challenge. --- ## Full Transcript [00:00] One thing this channel has always [00:01] attempted to do is to try to like [00:03] downplay or try to put a little bit of [00:06] cold water on AI hype beasts, okay? It's [00:08] just been something that I've found to [00:10] be very annoying about these last couple [00:12] years is that there's this all or [00:15] nothing approach that you often see from [00:17] Y Combinator or from CEOs of uh major AI [00:22] companies like Daario right here. 3 to 6 [00:23] months 90% of all code will be just [00:25] written by AIA, you know. But again, [00:27] this was 9 months ago and that's [00:29] currently not happening. Also, you just [00:31] see all these like CEOs of major [00:33] companies going out there being like, [00:34] "Embrace AI or get the hell out of [00:37] here." And yet, in this golden age of [00:38] software, honestly, I do think we're in [00:40] a golden age of software. In this golden [00:42] age, we have the highest quantity of [00:45] software ever written. Yet, it feels [00:47] like we have some of the lowest quality [00:49] of software ever written. I think [00:51] Microsoft is one of the best single [00:53] examples of this. Microsoft finally [00:55] admits almost all major Windows 11 core [00:59] features are broken. And yes, that [01:00] includes startup menu experience, [01:02] search, system settings, taskbar, and [01:04] explorer. In other words, Microsoft [01:06] Windows. So, in this day and age, when I [01:08] heard of a man named Matt Garmin give [01:10] his opinion, I was actually pretty [01:12] shocked. And you're probably a lot like [01:14] me. You're you were like, "Who who who's [01:17] Matt Garin? I don't know. Should I know [01:18] Matt Garmin?" Well, the funny thing is [01:20] is you know of his position. You just [01:22] probably don't know him. Matt Garmin is [01:25] CEO of AWS. Yep, that little old hosting [01:29] company AWS. And here is what he has to [01:32] say. I was at a group, a leadership [01:34] group, and people were telling me they [01:36] are like, we think that AI we can [01:38] replace all of our junior people in our [01:40] company. I was like, that's like one of [01:43] the dumbest things I've heard. This [01:46] amazing. Absolutely amazing. There is a [01:49] CEO out there that does have a more [01:52] level head when it comes to some of [01:54] these AI things. I would have loved, by [01:56] the way, to be sitting in there, a bunch [01:58] of people. We're going to get all those [02:00] juniors out. EVERYONE AT THE TABLE. HELL [02:02] YEAH. YOU KNOW, THEY'RE ALL LIKE [02:03] HIGH-FIVING, I don't know, doing [02:05] whatever CEO people do, like, I don't [02:07] know, insult their blood boy and [02:09] whatever. Whatever it is, and then just [02:10] to have this guy be like, "Yeah, okay. [02:12] Yeah, yeah, yeah." That's the dumbest [02:14] idea I have ever heard. Dude, what an [02:18] actual boss. Now, I have a lot to say [02:20] about why I think junior devs are [02:22] actually significantly more valuable [02:24] than a lot of these cucked AI overlord [02:26] hype beasts have been pushing lately, [02:28] but we'll get there. All right, so Matt [02:30] actually ends up giving us three reasons [02:32] why junior devs will remain kind of a [02:35] value valuable commodity in the day and [02:38] age of AI. Now, his reasons, honestly, [02:41] for how based his statement was, I I [02:43] didn't really like him. His first [02:44] reason, junior devs often know uh AI [02:47] tools better. I honestly I don't know if [02:49] that's true or not. Like I truly don't [02:51] know if that's true. Now, you could [02:52] convince me that junior devs use AI [02:55] tools more. That doesn't necessarily [02:57] mean they know them better. And so, of [02:59] the three reasons why junior devs are [03:01] valuable, I do find this one to be h [03:04] rather lackluster. Matt's second reason [03:07] also just has this air of big company, [03:09] right? It's just like they they're so [03:11] used to just firing orgs and firing [03:14] large amounts of people. The second one [03:15] really kind of like lines up with that [03:17] mentality, which is junior developers [03:18] shouldn't be the default cost-saving [03:20] move, which like at least how I read it [03:25] is like, hey, if you're going to fire [03:26] someone, you got to get those more [03:28] experienced people. Those pieces of crap [03:31] are expensive. But at the bottom, he [03:33] does say something that's pretty [03:34] amazing, which is in fact 30% of [03:35] companies that laid off workers [03:37] expecting savings ended up increasing [03:39] expenses, and many had to rehire later. [03:42] And this is true. I actually personally [03:44] know some stories that involve firing [03:46] people just to later rehire the exact [03:49] same person at a higher wage due to the [03:53] laying off to begin with. But lastly, [03:54] his last point I think is probably the [03:56] most interesting one, which is removing [03:58] juniors break the talent pipeline. and [04:01] he's kind of looking at it and in this [04:02] like long horizon. In other words, when [04:05] there are not enough junior hires being [04:07] trained today, teams struggle to fill [04:09] roles tomorrow, especially at project [04:11] scales. And I agree with him, but this [04:13] is like on much larger time scales, [04:15] which this is always just true. If [04:17] there's not new people coming in and as [04:20] the old people age out, you could find [04:22] yourself in kind of a tricky situation [04:24] where you have to pay an [04:25] everinccreasingly large amount of money [04:27] just to hire anybody. And honestly, this [04:29] is kind of what the 2010s genuinely felt [04:31] like. It was still that kind of hold [04:33] over from the dotcom boom era where [04:35] everybody was going to be a software [04:37] engineer. Then nobody was going to be a [04:38] software engineer and the numbers never [04:40] quite recovered and all a sudden you're [04:41] hitting 2008 2010 and people are [04:43] starting to pay more and more money [04:45] because there's just not that many [04:47] developers available. And with Daario [04:49] and all these kind of dummies on the [04:51] internet keep telling everybody that [04:52] software engineering is going to be [04:54] dead. Well, they're going to be causing [04:55] a similaresque problem. they're going to [04:57] be causing a less and less amount of [04:59] people entering into the workforce which [05:01] thus will kind of have this like second [05:03] order effect in 5 years. So I do yes I [05:06] actually do agree with Matt in the [05:08] overall statement that AI is not going [05:10] to be replacing junior devs. Junior devs [05:12] are actually incredibly value valuable [05:14] and it's really valuable long term in [05:16] the pipeline. Though I think his points [05:18] are a bit weak. I do think I have a [05:20] better reason why junior devs are [05:22] valuable. But I got to tell you a little [05:24] bit of a story. Here's the problem with [05:25] AI and junior devs. When I had I used to [05:28] have some junior devs, I used to be able [05:30] to command a fleet of them. And what I [05:33] used to be able to do is be like, "Hey, [05:34] this part of the system I want you to [05:36] take a look at. We need to go from here [05:38] to here, and I just want you to go [05:40] explore, think about things, and kind of [05:42] give me what you think." And it'd go on, [05:44] you know, they'd go off and they would [05:45] work for some amount of time. Uh, and [05:47] then come back with a bunch of different [05:49] ideas or, you know, some of them very [05:50] unique. And unique doesn't mean good or [05:52] bad, just they they were very unique. [05:54] But nonetheless, they actually cared [05:56] about the product. Like they actually [05:58] had an emotional investment in making [06:00] the place better. So often their changes [06:03] weren't simply exactly what I asked for, [06:05] but they were able to morph it and set [06:07] it and be able to kind of grow into this [06:09] position of expertise where instead of [06:11] just simply being someone that does [06:12] exactly what I say in the exact way that [06:15] I say, they start making changes that [06:17] are not what I'm saying, they're reading [06:18] between the lines. are able to do so [06:20] much more and it requires less and less [06:22] communication from me over time. Whereas [06:24] uh obviously with AI, the biggest [06:26] problem with AI is I have to accurately [06:28] describe my problem. And let's just face [06:30] it, the moment PMs can accurately [06:32] describe a problem is the day that [06:33] software development no longer exists, [06:35] which by the way is never. And so it's [06:38] like that's the thing that I think is [06:39] missing from this discussion is the [06:41] value multiplication that starts [06:43] happening as junior devs go from [06:45] complete novice into someone that can [06:47] start navigating this, you know, the org [06:50] structure and the large codebase. Then [06:52] all of a sudden they become super [06:54] valuable co-workers in which you start [06:56] going into different places and you're [06:58] like, "Hey, I need your help. Tell me [06:59] about this. What do you think?" and all [07:00] of a sudden their value starts [07:02] skyrocketing much more than an AI or [07:04] anything else has because I can [07:06] individually communicate with them. We [07:08] can talk about ideas. We can see things [07:10] that don't currently exist and weren't [07:12] even spoken of. There's like this whole [07:14] problem a lot with uh people kind of [07:16] miss is that you sometimes have to do [07:18] something wrong for a little bit or do [07:20] something that's less efficient to [07:22] understand what the actual correct [07:24] answer is. You need to do the wrong [07:26] thing to figure out what the right thing [07:28] is. Like one of the plugins I developed, [07:30] Harpoon, I I built like so many [07:33] different versions of the exact same [07:34] plugin, but with completely different [07:36] ideas trying to figure out how I wanted [07:39] to navigate cuz I couldn't quite I [07:41] didn't know quite what it was. And sure, [07:43] AI could have made that process of doing [07:45] these little explorations much much [07:47] faster, but then I still had to just sit [07:48] down and use it for two weeks. And so it [07:51] was almost never a problem of writing [07:53] code. It was a problem of understanding [07:55] what the right problem is to solve. So [07:57] again, I have to say this. I don't think [08:00] we have a quantity problem. We have a [08:02] quality problem. And I think that having [08:04] junior devs is an excellent way to [08:07] explore space, bounce off ideas, and [08:09] genuinely have people that are [08:11] enthusiastic and excited about what [08:14] they're doing. So, do I think junior [08:15] devs are going to get replaced with AI? [08:17] No. But do I think a lot of companies [08:19] are going to replace junior devs with [08:20] AI? Yeah, for some amount of time until [08:22] they realize it was a huge mistake. [08:28] The name [08:30] is the primogen. The two biggest [08:32] problems in computer science is cash [08:34] invalidation and pronouncing things. I [08:36] personally spent all day on teams [08:38] arguing whether it's SQL or Squeal. [08:40] Well, I have great news for you. Today [08:42] we have a company that solves both of [08:44] these problems. Convex. Uh I'm pretty [08:47] sure that's Convex. Teach. Get out of my [08:50] ad. Convex lets you ship your backend [08:52] without a backend team. Its real-time [08:54] database makes it easy to keep all of [08:56] your queries up to date. Convex allows [08:58] you to stop worrying about complicated [09:00] SQL and untyped messes. Instead, you can [09:03] embrace Convex's deep TypeScript [09:05] integration with type completion and [09:07] validation and database queries that are [09:09] just pure uncut TypeScript functions. [09:12] Try Convex today in your language of [09:14] choice, TypeScript, Python, and even [09:16] Rust. Visit convex.dev.