Bad Code Existed Long Before AI - CourtneyR.dev's 2nd Brain

"Bad" Code Existed Long Before AI ![rw-book-cover](https://img.youtube.com/vi/svZ7lD_KkZ0/maxresdefault.jpg) 🔗 **Source:** ["Bad" Code Existed Long Before AI](https://www.youtube.com/watch?v=svZ7lD_KkZ0) > [!note]+ Document Notes > tags: #ai-coding #software-development #code-quality #developer-education > author: Modern Builder > source: YouTube > reference: https://www.youtube.com/watch?v=svZ7lD_KkZ0 > date created: 2024-12-28 14:30 > > # 🏷️ Title: "Bad" Code Existed Long Before AI >  ## 🧰 Action Inbox - [H1] Examine pre-AI code quality standards — challenge assumptions about AI impact #ai-coding - [H2] Document historical software vulnerabilities — context for current AI debates #software-development - [H3] Research transitional periods in tech adoption — patterns for AI integration #developer-education ## 🧭 Table of Contents - [[#📝 Summary]] - [[#📖 Main Content]] - [[#🗒️ Notes]] - [[#📚 References]] - [[#🗣️ Paraphrase]] - [[#📰 Newsletter]] - [[#✅ Action Items]] - [[#🧪 Hypotheses]] - [[#📊 Methodology]] - [[#❓ Questions]] - [[#🔮 Future Research]] - [[#💡 Implications]] - [[#🧠 Learning Styles Assessment]] - [[#📊 Accessibility Assessment]] - [[#🌍 DEIB Assessment]] - [[#✅ Logical Validity]] - [[#🛡️ DARVO Analysis]] - [[#🎯 Conclusion]] ### 🔗 References - [Modern Builder Society Community](URL) - [Previous Video on Code Purists](URL) ## 📝 Summary - Creator responds to criticism about AI-generated code quality and market release concerns - Argues that poor code quality, vulnerabilities, and inexperienced developers existed long before AI - Claims current period is transitional "wild west" that will naturally settle as AI tools mature - Challenges assumptions that hand-coded software was inherently better or more secure - Bottom line: AI coding criticism often lacks historical perspective on pre-existing software quality issues ## 📖 Main Content The video addresses a viewer comment criticizing AI-assisted coding, specifically concerns about inexperienced developers releasing AI-generated products with security vulnerabilities. The creator argues this perspective lacks intellectual honesty about historical software development. Key arguments include that junior developers have always produced poor code with vulnerabilities, scammers have always existed in software markets, and the current criticism stems partly from developers feeling threatened by democratized coding tools. The creator suggests the market will naturally filter out poor products as AI tools mature. The discussion touches on broader themes of technological transition periods, drawing parallels to web design industry changes with platforms like Shopify and Wix. Multiple perspectives exist on whether AI democratization helps or harms software quality. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/svZ7lD_KkZ0?t=0) — [H1] Setting up the response to criticism - Key idea: Creator addresses viewer comment about AI coding concerns - Evidence: "The problem is all these people aren't using it for learning and education. They're releasing vibe coded products to market" #### ⏱️ [02:15](https://youtu.be/svZ7lD_KkZ0?t=135) — [H2] Core question about historical code quality - Key idea: Challenges assumption that pre-AI developers were universally good - Evidence: "Were there shitty developers back then? Were there people that were objectively bad or was everyone that developed something a good developer?" #### ⏱️ [03:30](https://youtu.be/svZ7lD_KkZ0?t=210) — [H3] Junior developers have always existed - Key idea: Inexperienced developers releasing poor code is not new - Evidence: "Weren't those junior developers putting out like objectively shitty products or objectively shitty code perhaps?" #### ⏱️ [04:45](https://youtu.be/svZ7lD_KkZ0?t=285) — [H2] Human vs machine bias - Key idea: Questions why hand-written bad code was more acceptable than AI-generated bad code - Evidence: "Just because somebody built it with their hands before and it was bad, now you know, it's fine" #### ⏱️ [06:00](https://youtu.be/svZ7lD_KkZ0?t=360) — [H3] Scammers always existed - Key idea: Bad actors in software development predate AI - Evidence: "We're getting products that are either made by scammers looking for quick bucks, which always has happened" #### ⏱️ [07:20](https://youtu.be/svZ7lD_KkZ0?t=440) — [H2] Transitional period perspective - Key idea: Current chaos is temporary wild west phase - Evidence: "We are in a period of flux right now where everybody is losing their mind. It's the wild west" #### ⏱️ [08:45](https://youtu.be/svZ7lD_KkZ0?t=525) — [H3] Non-coders assumption concerns - Key idea: Acknowledges legitimate concern about overconfidence in AI code - Evidence: "Non-coders who dangerously assume the code is great and secure and all that" #### ⏱️ [10:15](https://youtu.be/svZ7lD_KkZ0?t=615) — [H2] Empowerment through tools - Key idea: More people will gain coding capabilities as tools improve - Evidence: "This is going to continue to ramp up. There's going to be continued more people that like try to do this stuff" #### ⏱️ [11:30](https://youtu.be/svZ7lD_KkZ0?t=690) — [H3] Developer identity concerns - Key idea: Some criticism stems from professional identity protection - Evidence: "Developers, they've put their entire life, soul, and energy in the and they've built up the skill" #### ⏱️ [13:00](https://youtu.be/svZ7lD_KkZ0?t=780) — [H2] Training on bad code concern - Key idea: Addresses worry about AI training on poor quality code - Evidence: "Newer AI is getting trained on the crap code of yesterday's AI" #### ⏱️ [14:20](https://youtu.be/svZ7lD_KkZ0?t=860) — [H3] Historical technology parallels - Key idea: Compares to web design industry disruption - Evidence: "3-4 years ago we're bitching about like Shopify and Wix and Squarespace" #### ⏱️ [15:45](https://youtu.be/svZ7lD_KkZ0?t=945) — [H2] Call for intellectual honesty - Key idea: Requests fair comparison between AI and pre-AI era issues - Evidence: "Just be intellectually honest between like what is happening now with AI and then also what has happened in the past" ## 📚 References - [Modern Builder Society](https://modernbuilder.com) - [Previous Video on Code Purists](URL) - [Anthropic Glass Wing Research](URL) ## 🗣️ Paraphrase - Poor code quality, security vulnerabilities, and inexperienced developers releasing products existed long before AI-assisted coding became prevalent - The current criticism of AI-generated code often applies double standards, where hand-written bad code was more socially acceptable than machine-generated bad code - The software industry is in a transitional period that will eventually stabilize as AI tools mature and market forces filter out poor products ## 📰 Newsletter AI coding debates are heating up, but are we missing historical context? A recent discussion highlights how concerns about poor code quality, security vulnerabilities, and inexperienced developers aren't new - they've existed throughout software development history. The key insight: we may be applying different standards to AI-generated versus human-written code. While legitimate concerns exist about overconfidence in AI tools, the fundamental challenges of code quality, developer experience levels, and market dynamics remain consistent. For WordPress developers, this perspective matters as AI tools become more integrated into our workflows. Rather than dismissing these tools entirely, focus on using them thoughtfully while maintaining security best practices. Resources: [Learn WordPress](https://learn.wordpress.org/), [Developer Docs](https://developer.wordpress.org/), [WP-CLI](https://wp-cli.org/) ## ✅ Action Items #### DevRel - Developer education: Create content comparing historical vs current code quality standards - Community management: Moderate AI coding discussions with historical context - Developer experience: Document best practices for AI tool integration #### WordPress - Training: Develop lesson plans on AI-assisted WordPress development best practices - Documentation: Create guidelines for secure AI code generation in WordPress context - Community: Foster balanced discussions about AI tools in WordPress development ## 🧪 Hypotheses - Software quality issues attributed to AI coding existed at similar rates in pre-AI development - Market forces will naturally filter out poor quality AI-generated products over time - Developer resistance to AI tools partly stems from professional identity protection rather than purely technical concerns - Current "wild west" period of AI adoption will stabilize as tools and practices mature ### 📊 Methodology - Historical analysis: Compare vulnerability rates in pre-AI vs AI-assisted code - Market research: Track quality metrics of AI-generated vs traditional software products - Survey study: Measure developer attitudes toward AI tools and underlying motivations ### ❓ Questions - What quantitative data exists on code quality differences between eras? - How do we measure and compare software security across development methodologies? - What role should quality control mechanisms play in AI-assisted development? ### 🔮 Future Research - Longitudinal study of AI tool impact on software quality metrics - Analysis of market filtering mechanisms for poor quality software - Investigation of developer identity and professional adaptation patterns ### 💡 Implications - Practice: Encourage balanced perspective on AI tools while maintaining quality standards - Education: Include historical context in AI coding curriculum and training - Security: Develop consistent security practices regardless of code generation method - Policy: Consider evidence-based rather than assumption-based AI coding guidelines ### 🧠 Learning Styles Assessment Reading level estimate: 10-12 (conversational but technical) #### 👀 Visual learners - Present: None in original video - Improve: Add timeline comparing pre-AI and AI-era development issues, quality metrics charts #### 🔊 Aural learners - Present: Full video discussion with conversational tone - Improve: Add structured audio summary with key points #### 🗣️ Verbal learners - Present: Clear analogies to web design industry changes - Improve: Add more concrete examples and case studies #### 🧩 Kinesthetic learners - Present: None - Improve: Create hands-on comparison exercises between AI and traditional coding approaches #### 🧠 Logical learners - Present: Logical argument structure comparing past and present - Improve: Add data tables, metrics, and structured decision trees #### 🧑‍🤝‍🧑 Social learners - Present: Community discussion prompts and comment engagement - Improve: Facilitate structured debate sessions on AI coding practices #### 🧘‍♀️ Solitary learners - Present: Individual reflection prompts throughout - Improve: Add self-assessment worksheets on AI tool usage #### 🌿 Naturalistic learners - Present: None directly - Improve: Connect to technology evolution patterns and natural selection analogies ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Video has spoken content but lacks transcript - Improve: Add full transcript with proper heading structure #### Keyboard navigation - Present: Standard YouTube controls - Improve: Ensure video player is fully keyboard accessible #### Contrast and readability - Present: Standard video format - Improve: Add high-contrast subtitle options #### Text resizing and reflow - Present: Video content scales appropriately - Improve: Provide text-based version of key points #### Media and captions - Present: Spoken content available - Improve: Add accurate captions and downloadable transcript #### Forms and interactions - Present: Basic comment interaction - Improve: Ensure comment system meets accessibility standards ### 🌍 DEIB Assessment #### Cultural breadth - Present: US-centric perspective on software development - Improve: Include global development perspectives and practices #### Inclusive language - Present: Generally inclusive but uses some casual language - Improve: Define technical terms, avoid industry-specific idioms #### Neurodiversity support - Present: Conversational pace allows for processing time - Improve: Add structured outline and chapter markers #### Representation - Present: Single male creator perspective - Improve: Include diverse voices in AI coding discussions #### Psychological safety - Present: Respectful tone toward commenters - Improve: Establish clearer community guidelines for technical debates ### ✅ Logical Validity #### Strong reasoning - Inductive strength: Uses historical patterns to predict future trends - Analogical strength: Compares AI adoption to previous technology transitions - Causal reasoning: Links developer resistance to identity protection #### Fallacies - False dichotomy: Presents choice between accepting AI tools or being "purist" without middle ground - Hasty generalization: Assumes all criticism stems from personal bias rather than legitimate concerns - Appeal to tradition: Suggests because problems existed before, current problems are acceptable #### Tone of voice - Overall tone: Conversational, defensive but respectful, seeking dialogue rather than confrontation ### 🛡️ DARVO Analysis - Deny: Minimizes legitimate concerns about AI code quality - Attack: Subtle criticism of "code purists" as being intellectually dishonest - Reverse victim/offender: Positions AI critics as the problem rather than addressing underlying concerns - Emotional cues: Defensive tone when discussing developer expertise and gatekeeping ## 🎯 Conclusion The video raises important questions about historical context in AI coding debates, challenging assumptions that current problems are entirely new. While the creator makes valid points about pre-existing software quality issues, the discussion would benefit from more concrete data and acknowledgment of legitimate security concerns. The core insight about transitional periods being chaotic before stabilizing offers a useful framework, but practitioners should maintain rigorous quality standards regardless of development methodology. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad ### [H1] Poor code quality predates AI development tools > [!quote] "Bad" Code Existed Long Before AI by Modern Builder via YouTube. Published 2024. Accessed 2024-12-28. > "Were there shitty developers back then? Were there people that were objectively bad?" Historical perspective on software quality challenges transcending technological tools. [view highlight](https://youtu.be/svZ7lD_KkZ0?t=135#H1) #xref #articleseed ID:rw_001 ### [H2] Technology transitions create temporary market chaos > [!quote] "Bad" Code Existed Long Before AI > "We are in a period of flux right now where everybody is losing their mind. It's the wild west." Pattern recognition for understanding current AI adoption challenges. [view highlight](https://youtu.be/svZ7lD_KkZ0?t=360#H2) #xref ID:rw_002 ### 📖 Atomic Split Pad (Zettel Candidates) #### [Z1] Developer identity affects technology adoption attitudes - Professional investment in skills influences resistance to automation tools - Pointer to 11:30 timestamp discussion - Links: [[Technology-Adoption]] [[Professional-Identity]] #### [Z2] Market forces filter software quality over time - Natural selection applies to software products regardless of development method - Pointer to transitional period discussion at 7:20 - Links: [[Market-Dynamics]] [[Software-Quality]] ### ✏️ Fleeting Queue - [F1] Research vulnerability statistics pre-AI vs post-AI development — quantify claims #fleeting #inbox - [F2] Document web design industry transition parallels — Shopify/Wix case study #fleeting #inbox - [F3] Create balanced AI coding guidelines — acknowledge both benefits and risks #fleeting #inbox --- ## Full Transcript [00:00] I want to share some thoughts on a topic [00:02] that I get a lot and I hear a lot about [00:04] in this AI vibe coding AI assisted [00:07] realm, everything like that. Uh it stems [00:09] from a comment on recent video. I've [00:10] been doing a lot more of these recently [00:11] and I think this is a great way to kind [00:14] of just not directly answer the [00:15] comments, but just share my thoughts so [00:17] more people can [00:18] think about it because my current [00:19] thought process is if one person's [00:21] commenting like this, then other people [00:22] probably have that thought and I'm [00:23] always down to provide some some [00:26] thoughts and stuff. So, I'm just going [00:27] to read the comment real quick. I'm [00:28] going to provide my thoughts and then [00:29] you can throw yours in the comments of [00:31] this video because I just want to [00:32] continue to navigate this with all of [00:34] you. So, um the problem is all these [00:37] people aren't using it for learning and [00:40] education. They're releasing vibe coded [00:42] products to market, which all these have [00:44] problems and real developers are the [00:46] real developers are exposing. So, we get [00:48] products that are either made by [00:50] scammers looking for quick bucks or [00:51] non-coders who are dangerously assume [00:53] the code is great and secure and all [00:55] that. Newer AI get getting trained on [00:57] the crap code of yesterday's AI. Uh [01:00] there needs to be some quality control [01:01] somewhere. So, this was based off of a [01:03] video that I was kind of saying that [01:05] like code purists have lost the plot on [01:07] AI. I was basically actually making the [01:09] point more that people are I mean you [01:11] can go watch that video. I'll put the [01:12] link up there, but effectively I was [01:14] saying that like if you were a purist [01:16] and you're somebody that's like super [01:17] traditional developer and you definitely [01:18] want to [01:20] you know, you're you're kind of like [01:21] anti-AI in a sense or anti-in of [01:25] what it can do and you want to everybody [01:26] to like know all the syntax and all that [01:28] stuff and you think that's the future. I [01:29] just think it's not great when you're [01:32] you kind of putting down people that are [01:34] trying to use these things to learn and [01:35] everything. So, [01:37] in this comment here, um I mean it's a [01:38] fair analysis and I was like thinking [01:40] again, I was about to write a comment. I [01:41] was just like let me just make a video. [01:42] So, [01:43] I think that the concept here, I don't [01:46] entirely disagree with it. I do think [01:48] that some people are you know, possibly [01:50] not using it for just education and [01:53] learning like maybe they are maybe [01:54] that's part of it. [01:55] Um but I'm going to be honest like the [01:56] thing that comes to mind is I've heard [01:57] this objection before. The really big [01:59] thing is [02:01] are people is hasn't this always been [02:04] the case? Like it kind of seems like I'm [02:06] not interpreting this particular [02:07] comment, but anybody that says like this [02:09] particular thing, isn't this strikes me [02:11] as like you want there to be some sort [02:14] of like police force or some sort of [02:16] again quality control. Now, ideally in a [02:19] in a nice world we would love for [02:20] everything to be [02:21] you know, the best quality and all that. [02:23] But I just want to go here for a second. [02:25] I want to ask you this question [02:26] directly. Uh to any of you guys that [02:28] probably know more than me potentially [02:29] if you're like you've been developing [02:31] for like 30 years. Let Let's Let's have [02:34] an honest conversation just for a second [02:35] cuz I actually don't know the answer to [02:36] this question, but I'm using my critical [02:37] thought. Um let's say 10 years ago when [02:40] AI wasn't a thing. I know it was, but it [02:42] wasn't nearly obviously as prevalent. [02:44] Nobody was using it at scale, whatever. [02:46] If you wanted to code something, you had [02:47] to code it from scratch essentially, [02:49] right? [02:50] Let's just make up that number of 10 [02:51] years ago. [02:53] Were there shitty developers back then? [02:55] Were there Were there people that were [02:57] objectively bad or was everyone that [02:58] developed something a good developer? [03:00] So, that's like the first question. The [03:02] second question is did some of those [03:04] shitty developers put out products? [03:07] Like is it is it inconceiv- Maybe I'm [03:10] misunderstanding. Is it inconceivable to [03:12] think that there were bad like [03:14] objectively, no disrespect, just on a [03:16] totem pole of developers, there had to [03:18] be like junior developers, right? Like [03:20] amateur developers that weren't very [03:21] good. But they wanted to put out their [03:23] first projects or whatever and they [03:25] wanted to put that stuff out. And they [03:27] and they did things. Now, [03:29] maybe your your junior or your layperson [03:31] developer now is putting out a different [03:33] type of product that they don't know cuz [03:35] they maybe they're getting in over their [03:36] heads. That's a slightly different [03:38] thing. What I'm saying is at first, [03:41] weren't those junior developers putting [03:42] out like objectively shitty products or [03:45] objectively shitty code perhaps? [03:47] Like they weren't good, right? They [03:49] probably had vulnerabilities in them [03:51] that they didn't know about. But us [03:53] being human, we were empathetic to the [03:55] fact that other humans didn't know as [03:57] much as Well, some people aren't and [03:59] some people never were. But I'm saying [04:00] like a a lot of people human to human, [04:02] it's like okay, you're a human, you're [04:03] trying to do stuff, whatever, that's [04:05] fine. [04:06] You there's problems with this, but at [04:07] least you did it by yourself. Why is [04:09] like doing things by yourself like give [04:11] you like it's like if you reverse this [04:13] argument, it's like doing things by [04:14] yourself manually somehow is like not a [04:17] problem. And I don't think I don't think [04:19] either should be a problem. I think that [04:21] the answer to this long term is like we [04:24] are in a period of flux right now where [04:25] everybody [04:27] is losing their mind. It's the wild west [04:30] and I just think that's the [04:31] transitionary period that we're in right [04:33] now. That's why everything is crazy. But [04:35] I think if we zoom, you know, if we if [04:37] we fast forward [04:39] a few years or whatever, it's going to [04:41] be the market is going to settle down a [04:43] little bit more and this AI whole thing [04:45] is going to be more mature and all the [04:46] is going to naturally fade [04:47] away. So, some of this stuff isn't even [04:50] you know, we're talking about it just [04:51] because it's the current topic. But my [04:53] whole thing is like [04:55] it's like [04:56] there again to the comment, they're [04:58] releasing vibe coded products to market [05:00] which have all these problems that real [05:01] developers are exposing. Did that not [05:03] happen before? Like I mean maybe I'm [05:05] wrong, but did that not happen before [05:07] with like developers that didn't know [05:08] what they were doing and they had [05:09] vulnerabilities and they had all these [05:11] things, but now because a machine is [05:13] creating the code and we don't like that [05:14] that machine bad machine code bad like [05:17] whatever. Like [05:18] that is that is that the problem? Is [05:20] that part of the problem? [05:22] I I just feel like that's slightly like [05:24] missing [05:26] like the the the point or not being [05:28] intellectually honest about what used to [05:29] happen. [05:31] And just because somebody built it with [05:32] their hands before and it was bad, now [05:35] you know, it's fine it's fine. Whatever [05:37] it had vulnerabilities, had all these [05:38] other things which software always has [05:39] that. So, I don't get that argument [05:40] either. I talk about them in different [05:41] videos. But yeah, so I mean so we're [05:43] getting products that are either made by [05:44] scammers looking for quick bucks, which [05:47] always has happened. It's always [05:49] happened, okay, right? Like that's [05:51] hasn't this hasn't this part always [05:52] happened? [05:53] Or or non-coders who dangerously assume [05:55] the code is great and secure and all [05:57] that. I think we got to be real careful. [05:59] Last thing I want I'll I'll Can I mark [06:01] on this? No, I don't think so. Um There [06:03] we go. Like the last thing I would say [06:05] is just this part right here. Well, I [06:06] can't type it all here. Um this [06:09] part right here. [06:11] I just would love for us all and again, [06:13] no no um [06:14] no uh shade here on specific comment [06:17] here, but I'm just saying in general the [06:18] avatar. This part right here, um I would [06:22] just I would be wary of this because [06:26] just like how more people are learning [06:29] to do all sorts of things with you know, [06:32] AI or whatever the whatever the [06:33] technical tool has been throughout you [06:34] know, the thing. It's like this is going [06:36] to continue to ramp up. There's going to [06:38] be continued more people that like try [06:40] to do this stuff and they're going to [06:41] get better because the tools are getting [06:42] better and then they're going to get [06:44] more empowered and they're going to want [06:46] to do more of that stuff. So, I [06:48] understand the sentiment here of like [06:49] non-coders who dangerously assume code [06:51] is great and all and secure and all [06:52] that. There's definitely a lot of people [06:53] like that and I try to do my best to not [06:55] be that person. Um [06:58] but at the same time like you know, I [07:01] just still see this as like [07:03] I see this no differently than like [07:05] people that wanted to do this type of [07:07] work and they just didn't know a lot at [07:09] first. [07:11] I mean, I don't know. I think there's I [07:12] think there's also there's a lot of [07:13] other motifs I don't want to dive into [07:14] this video dive into because again, I [07:16] talk about it all the time. I think [07:18] there's a lot of like [07:19] personal [07:21] like stuff like wrapped up in a lot of [07:22] these these arguments not just not in [07:24] this comment necessarily, but I'm just [07:25] saying in general like [07:27] people are developers, they've put their [07:30] entire life, soul, and energy in the and [07:31] they've built up the skill and they feel [07:33] like other people that haven't put in [07:34] the time, sweat, and energy couldn't [07:36] can't do it. [07:37] I just don't think that's going to be [07:38] the case for a very long time. I'm not [07:40] saying they're going to do it at the [07:41] same level as you and I talked about in [07:42] the other video. You you should continue [07:43] to to be better because you can [07:45] orchestrate better than them because you [07:46] know more than them. But I just still [07:48] think that it's not I don't think that's [07:49] like a winning argument long term. I [07:50] don't see how it could possibly be cuz [07:52] the stuff is getting so so much better [07:53] so fast. Like I don't I don't even I [07:56] don't even get it. There's something in [07:57] my eye here. But uh yeah. [07:59] So, um I mean just last very very last [08:02] thing on this cuz that is such a great [08:03] comment here is um [08:05] newer AI is getting trained on the crap [08:07] code of yesterday's AI. I don't know if [08:09] that's like entirely true. I don't I [08:10] mean like I guess I guess in a certain [08:12] way that ends up being the case. Like if [08:14] you would put out software and then it [08:16] would get trained on that. [08:18] That's a concern, but I don't I'm not [08:21] saying that that developers are going to [08:23] be gone or anything like that. I don't [08:24] think that's the case. I just think that [08:26] more people are going to be able to do [08:28] like do that type of work or not even do [08:30] that work professionally, but like kind [08:32] of help themselves do it a little bit [08:34] more themselves and things like that. [08:35] This is just a natural progression. This [08:37] has happened with so many other pieces [08:38] of technology where it's like really [08:39] hard to do it first and now it's like [08:41] really easy to do it first. I come from [08:42] the web design industry specifically, so [08:44] I know exactly what it is. 3 4 years ago [08:47] we're bitching about or maybe 5 years [08:49] ago bitching about like Shopify and Wix [08:51] and Squarespace and all that stuff. They [08:53] didn't want to do that, but now it's way [08:54] easier for people to like do that. Uh [08:57] and it's just like a different, you [08:58] know, it just it's just it just changes. [09:00] So, [09:01] um [09:02] went a little bit [09:04] out you know, out of the I I kind of had [09:06] like a thought process for this video [09:08] and I I think I felt I think I hit it [09:09] like well enough, but [09:11] I don't know. You tell me. My whole [09:12] thing is just I I see this and I just [09:14] think that [09:15] we if we're going to have these [09:17] arguments, all I would like all I'd like [09:18] us to do is just be or these [09:20] discussions, I wouldn't call them [09:21] arguments. I just like us to be [09:22] intellectually honest between like what [09:23] is happening now with AI and then also [09:25] what has happened in the past with like [09:26] just pre-AI with like people developing [09:29] and and all of that. Um there's always [09:32] been vulnerabilities. There's always [09:34] been problems. Those are actually going [09:36] to get worse and it has it's going to [09:38] have nothing to do with [09:41] uh it's going to have nothing to do with [09:42] like AI vi- AI coded whatever. It's it's [09:45] it's being found even in stuff that was [09:47] fully like human written. Uh talk about [09:49] that in the you know, in the glass wing [09:50] stuff and all that from Anthropic. So, [09:53] yeah. Uh that's just that's just my take [09:54] on this. [09:56] Um I think that it's a weird time and [09:59] it's just can continue to get weirder [10:01] until it starts to kind of like settle [10:02] down a little bit. But who knows when [10:04] that's going to happen, so until then [10:05] I'm just going to keep trying to learn, [10:07] try and share the things that I do. [10:09] If you're interested and you like the [10:10] way that I think and and do all the [10:11] stuff and you want to navigate this [10:12] together, yes, I do have a community. [10:14] It's called Modern Builder Society. It's [10:15] in the description. If you're a business [10:17] owner and you're trying to navigate this [10:18] stuff, I I do that. That's my main gig [10:20] to do [10:21] client work and things like that to [10:22] implement types of systems, automations, [10:25] uh you know, websites, those types of [10:26] things in businesses. The link is in the [10:28] description as well. You can check it [10:29] out. Regardless though, thank you so [10:31] much for watching. I greatly appreciate [10:32] it. If you have a thought, leave it in [10:34] the comments down below. If it's really [10:36] great and and insightful and I can't fit [10:37] it into a comment reply, I may make a [10:39] video about it. Thank you so much. I [10:41] greatly appreciate it. I'll talk to you [10:42] in the next one.  📄 **Full text:** ![[Full Document Contents/Articles/Bad Code Existed Long Before AI.md|"Bad" Code Existed Long Before AI by YouTube]] ## Highlights - which have all these problems that real developers are exposing. Did that not happen before? Like I mean maybe I'm wrong, but did that not happen before with like developers that didn't know what they were doing and they had vulnerabilities and they had all these things, but now because a machine is creating the code and we don't like that that machine bad machine code bad like whatever. Like that is that is that the problem? Is that part of the problem? I I just feel like that's slightly like missing like the the the point or not being intellectually honest about what used to happen. ([View Highlight](https://read.readwise.io/read/01krgqnzg3f47zw4k1kfqsrqgx)) - Tags: 👻 ai highlighted - on this? No, I don't think so. Um There we go. Like the last thing I would say is just this part right here. Well, I can't type it all here. Um this part right here. I just would love for us all and again, no no um no uh shade here on specific comment here, but I'm just saying in general the avatar. This part right here, um I would just I would be wary of this because just like how more people are learning to do all sorts of things with you know, ([View Highlight](https://read.readwise.io/read/01krgqnzh06bsb29aw6dczbezn)) - Tags: 👻 ai highlighted