Why Your Agency Needs To Embrace AI - CourtneyR.dev's 2nd Brain

Why Your Agency Needs To Embrace AI 🔗 **Source:** [Why Your Agency Needs To Embrace AI](https://www.youtube.com/watch?v=T6sSrbpR2e4) > [!note]+ Document Notes > tags: [wordpress-development, ai-tools, web-agency, developer-productivity] > author: The WP Minute > source: YouTube > reference: https://www.youtube.com/watch?v=T6sSrbpR2e4 > date created: 2024-12-28 21:30 > > # 🏷️ Title: Why Your Agency Needs To Embrace AI >  ## 🧰 Action Inbox - [H1] Test AI code generation with WordPress plugin settings pages — validate against known best practices #testing - [H2] Set up instruction files for AI coding assistants with WordPress standards — improve code quality #configuration - [H3] Run all AI-generated code through plugin-check tool — catch security vulnerabilities #security ## 🧭 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 - [The WP Minute](https://thewpmin.com) - [WebDev Studios](https://webdevstudios.com) ## 📝 Summary - Brad Williams from WebDev Studios discusses how agencies must embrace AI tools for WordPress development - Why it matters: Agencies not using AI will fall behind competitors who leverage these productivity tools - Key stakeholders: WordPress developers, agency owners, development teams - Risks and tradeoffs: AI generates insecure code by default, requires verification and testing - Bottom line takeaway: Use AI as a coding assistant but always trust and verify output through proper testing ## 📖 Main Content Brad Williams argues that AI tools have become essential for WordPress agencies and developers. He recommends testing AI capabilities by having it build WordPress plugins with settings pages, as this reveals whether the AI uses modern WordPress APIs (Settings API) or deprecated methods. Many AI tools default to older, less secure approaches that bypass WordPress's built-in sanitization and escaping. The key to effective AI usage is providing proper instruction files that define the AI as an expert WordPress developer following specific coding standards. This context dramatically improves output quality. However, all AI-generated code should be run through security tools like plugin-check and tested in staging environments before production deployment. Williams emphasizes that while AI won't replace developers, those not using these productivity tools will be outpaced by peers who leverage AI for routine tasks. The technology is also advancing marketing automation, with increasingly sophisticated personalized outreach based on scraped professional data. ## 🗒️ Notes #### ⏱️ [00:00](https://www.youtube.com/watch?v=T6sSrbpR2e4?t=0) — [H1] Introduction to AI Testing Strategy - Key idea: Test AI code generation with WordPress plugin settings pages to evaluate quality - Evidence: "There's about 50 different ways you could do this...one recommended way which is use the settings API" #### ⏱️ [00:30](https://www.youtube.com/watch?v=T6sSrbpR2e4?t=30) — [H2] AI Often Uses Deprecated WordPress Methods - Key idea: AI tools frequently generate insecure legacy WordPress code instead of modern APIs - Evidence: "A lot of the responses...would be the old way...rather than the settings API which does all the escaping all the sanitizing" #### ⏱️ [01:15](https://www.youtube.com/watch?v=T6sSrbpR2e4?t=75) — [H1] Importance of Instruction Files for AI Context - Key idea: AI coding assistants perform better with detailed instruction files defining expertise and standards - Evidence: "You can kind of give it like an instruction file...saying you're an expert level WordPress developer" #### ⏱️ [01:45](https://www.youtube.com/watch?v=T6sSrbpR2e4?t=105) — [H2] Providing Standards Documentation Improves AI Output - Key idea: Linking coding standards and documentation in prompts makes AI responses more accurate - Evidence: "You follow the WordPress coding standards linked to the standards...it gets super sharp once you start feeding it those rules" #### ⏱️ [02:15](https://www.youtube.com/watch?v=T6sSrbpR2e4?t=135) — [H1] Trust But Verify Principle for AI Code - Key idea: Always validate AI-generated code rather than using it directly in production - Evidence: "Always trust but verify...I like to challenge it sometimes when I know what the answer should be" #### ⏱️ [02:45](https://www.youtube.com/watch?v=T6sSrbpR2e4?t=165) — [H2] Plugin-Check Tool Reveals Security Issues - Key idea: WordPress's official plugin-check tool catches many security vulnerabilities in AI code - Evidence: "I'm always amazed at how many things come out unescaped" #### ⏱️ [03:00](https://www.youtube.com/watch?v=T6sSrbpR2e4?t=180) — [H1] Never Deploy AI Code Directly to Production - Key idea: All AI-generated code must go through development and staging environments first - Evidence: "Don't go straight to production, please. Just check it first, put it on a staging site" #### ⏱️ [03:30](https://www.youtube.com/watch?v=T6sSrbpR2e4?t=210) — [H2] AI Systems Learn and Adapt Over Time - Key idea: AI coding assistants can learn team processes and custom coding standards - Evidence: "These systems are smart and they can learn...understand your team's processes, your coding standards" #### ⏱️ [04:00](https://www.youtube.com/watch?v=T6sSrbpR2e4?t=240) — [H1] AI as Modern Rubber Duck Debugging - Key idea: AI tools serve as interactive debugging partners for problem-solving - Evidence: "You have that rubber duck...now you got AI you can rubber duck with AI" #### ⏱️ [04:30](https://www.youtube.com/watch?v=T6sSrbpR2e4?t=270) — [H1] Competitive Necessity of AI Adoption - Key idea: Developers not using AI tools will fall behind peers who embrace automation - Evidence: "You need to get on board or you're going to get passed...if you're not using these tools...all your peers are" #### ⏱️ [05:00](https://www.youtube.com/watch?v=T6sSrbpR2e4?t=300) — [H2] AI Enhances Productivity Across All Skill Levels - Key idea: AI tools benefit developers at every experience level by automating routine tasks - Evidence: "It has made my day a lot easier...every level should probably be digging into this deeply" #### ⏱️ [05:30](https://www.youtube.com/watch?v=T6sSrbpR2e4?t=330) — [H2] AI Marketing Automation Becoming More Sophisticated - Key idea: AI-powered marketing outreach is increasingly personalized and harder to identify - Evidence: "They're getting so specific like 'Hey, I saw you worked on this project'...it's just scraping your LinkedIn" ## 📚 References - [WordPress Settings API Documentation](https://developer.wordpress.org/plugins/settings/settings-api/) - [Plugin Check Tool](https://wordpress.org/plugins/plugin-check/) - [WordPress Coding Standards](https://developer.wordpress.org/coding-standards/) ## 🗣️ Paraphrase - WordPress agencies must adopt AI coding tools to remain competitive, as peers using these productivity enhancers will outpace those who don't - AI-generated WordPress code often uses deprecated methods that lack proper security sanitization, requiring developers to verify output against modern standards - The most effective approach involves configuring AI assistants with detailed instruction files specifying WordPress expertise and coding standards, then testing all output in staging environments ## 📰 Newsletter **AI Tools Transform WordPress Development Workflows** WordPress agencies are discovering that AI coding assistants can dramatically accelerate development - but only when used properly. Brad Williams from WebDev Studios shares a smart testing strategy: have AI build a WordPress plugin settings page to see if it uses the modern Settings API or insecure legacy methods. The key insight? AI performs much better with context. Create instruction files that define your AI as an expert WordPress developer following specific coding standards. This simple step dramatically improves code quality and security. Remember to always run AI-generated code through WordPress's plugin-check tool and test in staging environments. The goal isn't replacement - it's acceleration of routine tasks while you focus on higher-level problem solving. Resources: [WordPress Settings API](https://developer.wordpress.org/plugins/settings/settings-api/), [Plugin Check Tool](https://wordpress.org/plugins/plugin-check/), [Coding Standards](https://developer.wordpress.org/coding-standards/) ## ✅ Action Items #### WordPress - Core: Evaluate AI-generated contributions for security compliance - Training: Develop AI-assisted WordPress development curriculum - Documentation: Create AI prompt templates for WordPress coding standards - Security: Expand plugin-check tool to catch more AI-generated vulnerabilities - Community: Share best practices for AI tool usage in WordPress development #### DevRel - Education: Workshop on secure AI-assisted WordPress development - Developer experience: AI prompt libraries for common WordPress patterns - Community management: Guidelines for AI-generated code contributions #### Community - Maintainers: Code review standards for AI-generated submissions - Contributors: Training on validating AI output before pull requests - Ecosystem: Cross-project AI coding standards coordination ## 🧪 Hypotheses - AI coding assistants trained with WordPress-specific instruction files produce more secure code than generic prompts - Developers using AI tools for routine WordPress tasks complete projects 30-50% faster than those without - Plugin-check integration into AI workflows reduces security vulnerabilities by 70% - Agencies adopting AI-assisted development maintain competitive advantages over traditional-only shops ### 📊 Methodology - A/B testing: Compare code quality between generic AI prompts vs WordPress-specific instruction files - Time tracking: Measure development velocity before and after AI tool adoption - Security scanning: Analyze vulnerability rates in AI-generated vs human-written WordPress code ### ❓ Questions - How can WordPress Core better support AI-assisted development workflows? - What instruction file templates would most benefit the WordPress developer community? - Should WordPress.org provide official AI prompt libraries for common development patterns? ### 🔮 Future Research - Integration patterns between AI coding tools and WordPress development environments - Community standards for reviewing and merging AI-generated code contributions - Training programs for transitioning traditional WordPress developers to AI-assisted workflows ### 💡 Implications - Practice: WordPress developers need AI literacy as core competency alongside PHP and JavaScript skills - Security: Enhanced code review processes required to catch AI-generated vulnerabilities before deployment - Education: WordPress training curricula must include AI tool usage and validation techniques - Funding: Agency budgets should allocate resources for AI tool subscriptions and developer training ### 🧠 Learning Styles Assessment Reading level estimate: 10th grade #### 👀 Visual learners - Present: Video format with speaker demonstration - Improve: Code comparison diagrams showing secure vs insecure AI output #### 🔊 Aural learners - Present: Podcast-style interview format available - Improve: Audio summary highlighting key testing strategies #### 🗣️ Verbal learners - Present: Clear analogies like "rubber duck debugging" with AI - Improve: Glossary of AI development terms and WordPress API comparisons #### 🧩 Kinesthetic learners - Present: Specific testing methodology with plugin settings pages - Improve: Step-by-step checklist for validating AI-generated WordPress code #### 🧠 Logical learners - Present: Clear cause-effect relationship between AI training and code quality - Improve: Decision tree for when to use vs avoid AI coding assistance #### 🧑‍🤝‍🧑 Social learners - Present: Interview format with expert sharing experiences - Improve: Community discussion prompts about AI adoption challenges #### 🧘‍♀️ Solitary learners - Present: Individual testing strategies and validation methods - Improve: Self-assessment rubric for evaluating AI tool effectiveness #### 🌿 Naturalistic learners - Present: Discussion of technology evolution and adaptation - Improve: Ecosystem thinking about AI's role in WordPress development lifecycle ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Clear heading structure in transcript format - Improve: Timestamped section headings with descriptive labels #### Keyboard navigation - Present: YouTube player supports keyboard controls - Improve: Transcript navigation with skip-to-section links #### Contrast and readability - Present: Standard YouTube video player interface - Improve: High-contrast transcript option for easier reading #### Text resizing and reflow - Present: Responsive video player and transcript text - Improve: Zoom-friendly transcript formatting with preserved line breaks #### Media and captions - Present: Auto-generated captions available on YouTube - Improve: Professional captions with technical term accuracy, downloadable transcript #### Forms and interactions - Present: Standard YouTube commenting and sharing interfaces - Improve: Accessible feedback forms for content suggestions ### 🌍 DEIB Assessment #### Cultural breadth - Present: Focus on globally-used WordPress platform and standards - Improve: Examples from international WordPress development teams and practices #### Inclusive language - Present: Technical discussion avoids exclusionary jargon - Improve: Define technical terms for developers at various experience levels #### Neurodiversity support - Present: Clear section breaks with consistent interview structure - Improve: Visual timestamps and topic summaries for better cognitive load management #### Representation - Present: Industry expert sharing practical development experience - Improve: Diverse voices discussing AI adoption across different types of WordPress organizations #### Psychological safety - Present: Non-judgmental tone about skill levels and AI adoption - Improve: Explicit encouragement for developers at all stages of AI learning ### ✅ Logical Validity #### Strong reasoning - Deductive strength: If AI lacks WordPress context, then it produces insecure code (supported by Settings API example) - Inductive strength: Multiple testing examples support general principle of "trust but verify" - Causal reasoning: Clear connection between instruction file quality and AI output improvement - Analogical strength: Rubber duck debugging comparison effectively explains AI's role as coding partner #### Fallacies - Appeal to consequences: "You need to get on board or you're going to get passed" - while practical, lacks evidence for timeline/inevitability - Hasty generalization: Plugin settings page test may not represent all AI coding capabilities #### Tone of voice - Overall tone: Practical and encouraging, balancing enthusiasm for AI tools with appropriate caution about security risks ### 🛡️ DARVO Analysis - Deny: No denials present - speaker acknowledges AI limitations upfront - Attack: No attacks on critics of AI adoption - respectful of different perspectives - Reverse victim/offender: Not applicable - discussion focuses on tool adoption rather than conflict - Emotional cues and rhetoric: Positive framing emphasizes opportunity rather than fear-based adoption ## 🎯 Conclusion WordPress agencies and developers must embrace AI coding tools to remain competitive, but success requires proper implementation with security-first practices. The key is configuring AI assistants with WordPress-specific expertise and always validating output through established security tools and staging environments. Rather than replacing developers, AI serves as an accelerant for routine tasks while humans focus on higher-level architecture and problem-solving. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad Purpose: Stage CEE units that become Literature notes. Split level: H3 ### [H1] AI coding assistants require WordPress-specific training > [!quote] [Why Your Agency Needs To Embrace AI](https://www.youtube.com/watch?v=T6sSrbpR2e4) by [[Brad Williams]] via [[The WP Minute]]. Published 2024. Accessed 2024-12-28. > "You can give it an instruction file saying you're an expert level WordPress developer following coding standards." Proper AI configuration dramatically improves WordPress code quality an --- ## Full Transcript [00:00] Hi everyone and welcome to the WP [00:02] Minute. I'm your host Eric Karkovac. [00:05] Today's episode features a segment of my [00:08] interview with Brad Williams. Brad is [00:10] the partner and co-founder of WebDev [00:13] Studios. [00:15] Now to hear the entire interview, check [00:17] out our WP Minute Plus podcast. Visit us [00:20] over at thewpmin.com [00:22] for details and to become a member. [00:25] Thanks and we'll see you next time. [00:30] This is a great way to test it, right? [00:31] Especially as a developer is have it [00:32] build a set a plugin with a settings [00:34] page. Um, and that was how I generally [00:37] will test AI code to see what it does [00:39] because if you've done any development [00:40] WordPress and plugins and setting pages, [00:42] there's about 50 different ways you [00:43] could do this, right? Um, there is like [00:46] one recommended way which is use the [00:47] settings API. Um, and a lot of the [00:51] responses and things that would come [00:52] back from chat GPT, from Gemini, um, [00:54] other things would be the old way. It [00:57] would be either using the you know add [00:59] settings you know update setting or [01:01] update options I think it is functions [01:03] like the direct functions to work with [01:04] settings blah blah blah rather than the [01:07] settings API which does all the escaping [01:09] all the sanitizing does all that for you [01:11] right where this other method does not [01:12] so if you're not including that extra [01:13] stuff now you're you know potentially [01:15] compromise so test it out give it [01:18] something that you know what it should [01:19] do you know what the right answer is and [01:21] tell it like test these things out and [01:23] see if it comes back wrong that oh maybe [01:25] this isn't the tool Maybe it's the [01:27] prompt or the way that you set it, [01:28] right? Like making sure that you're um [01:31] really instructing it. That's the cool [01:32] thing about cursor and some of these [01:33] other platforms. You can kind of give it [01:34] like a I forget what exactly it's [01:36] called, but it's like an instruction [01:37] file and it's basically setting the [01:39] stage for this bot so it understands [01:41] what it is and how it needs to work. And [01:42] it's like saying you're a you know an [01:43] expert level WordPress developer. You [01:45] follow the WordPress coding standards [01:47] linked to the standards. You follow [01:48] these PHP standards linked to the you [01:50] know, you give it these instructions so [01:52] it knows who it is and how it needs to [01:54] act. the the standards it needs to [01:56] follow and then it really tightens up [01:58] what it's doing. Right now it knows I'm [01:59] a expert level WordPress. I'm gonna [02:01] follow all these standards, right? [02:02] Here's the whole documentation I can go [02:04] off of, you know? So, it it gets super [02:06] sharp once you start feeding it those [02:07] those rules rather than just saying code [02:09] me something and chat GBT and it's like, [02:11] okay, and it spits out something [02:12] completely wrong. So, always trust but [02:14] verify, but I like to challenge it [02:15] sometimes when I know what the answer [02:17] should be. See [02:18] >> what it comes back with. It's [02:19] interesting. Yeah, I I've uh taken to [02:21] running anything I generate through [02:23] plug-in check, which is what the uh the [02:26] official plug-in repository uses to s to [02:29] check against security and best [02:31] practices and things like that. And I'm [02:33] always amazed at how many things come [02:35] out unescaped. Uh you know, and so that [02:38] that's kind of like, you know, the the [02:39] um the process of kind of going through [02:42] that and just verifying that, okay, now [02:44] I can look at this and say, okay, this [02:46] isn't secure. I've got to I I've got to [02:48] fix this. Don't go straight to [02:49] production, please. Just [02:52] >> check it first, [02:53] >> put it on a staging site and then see [02:55] what it does. [02:56] >> Yeah, I mean that that's exactly it. [02:57] Trust by verify. Um, you know, make sure [02:59] what it's producing. Always Yeah. Never [03:02] do it directly in prod. Always dev, [03:03] always staging. Work in local [03:04] environments. Um, you know, these [03:06] systems are smart and they they can [03:08] learn, right? Like so they can learn [03:09] over time. They can understand your [03:10] team's processes, your processes, your [03:11] coding, your own coding standards, [03:13] right? It doesn't just have to follow [03:14] WordPress. You might have your own tweak [03:16] on those standards and you just feed it [03:18] all that right and train it to be your [03:19] coding assistant your you know we always [03:22] what we call the rubber duck right like [03:23] you have that rubber duck when now you [03:25] got AI you can rubber duck with AI say [03:26] hey something's not right here I'm not [03:28] quite sure you know what's going on what [03:29] do you think and it's pretty wild um [03:32] it's fun though it's it's just a new way [03:34] of coding you know and I think people [03:35] either honestly you need to get on board [03:37] or or you're going to get passed at this [03:38] point from from development again it's [03:40] not there to replace you but if you're [03:41] not using these tools to help accelerate [03:43] what you're doing and do some of the [03:44] more routine monotonous stuff. All your [03:47] all your peers are right. So, it's going [03:49] to catch up to you at some point. [03:51] >> Yeah. And you're pretty happy with the [03:53] time you save, I think, too. I mean, it [03:54] it it has made my day a lot easier. I [03:57] know that. So, I it's something that, [03:59] like I said, every level should probably [04:01] be uh digging into this deeply now. [04:04] >> Yeah. Yeah. I mean, and we haven't [04:06] talked about the marketing angle of it, [04:07] right? Like all the emails we get now, [04:08] like it's even more and there's there's [04:10] they're getting so specific like, "Hey, [04:11] I saw you worked on this project at that [04:12] blah blah blah." like it's just scraping [04:14] your LinkedIn and autogenerate like but [04:16] they're getting smarter, right? They're [04:17] getting smarter in what they say to try [04:18] to get you to interact and be like, [04:19] "Wait, how'd you know that?" you know, [04:21] it's all coming through these AI [04:23] systems, you know, and that's that [04:24] they're just getting smarter because [04:25] they can figure out the data and what [04:26] you want to read or what you want to  ## 📺 Video ![](https://www.youtube.com/watch?v=T6sSrbpR2e4) --- # 📄 Full Transcript *Auto-generated from YouTube captions · timestamps roughly every 30 seconds · [watch on YouTube](https://www.youtube.com/watch?v=T6sSrbpR2e4)* **[00:00]** Hi everyone and welcome to the WP Minute. I'm your host Eric Karkovac. Today's episode features a segment of my interview with Brad Williams. Brad is the partner and co-founder of WebDev Studios. Now to hear the entire interview, check out our WP Minute Plus podcast. Visit us over at thewpmin.com for details and to become a member. Thanks and we'll see you next time. **[00:30]** This is a great way to test it, right? Especially as a developer is have it build a set a plugin with a settings page. Um, and that was how I generally will test AI code to see what it does because if you've done any development WordPress and plugins and setting pages, there's about 50 different ways you could do this, right? Um, there is like one recommended way which is use the settings API. Um, and a lot of the responses and things that would come back from chat GPT, from Gemini, um, other things would be the old way. It would be either using the you know add settings you know update setting or **[01:01]** update options I think it is functions like the direct functions to work with settings blah blah blah rather than the settings API which does all the escaping all the sanitizing does all that for you right where this other method does not so if you're not including that extra stuff now you're you know potentially compromise so test it out give it something that you know what it should do you know what the right answer is and tell it like test these things out and see if it comes back wrong that oh maybe this isn't the tool Maybe it's the prompt or the way that you set it, right? Like making sure that you're um really instructing it. That's the cool **[01:32]** thing about cursor and some of these other platforms. You can kind of give it like a I forget what exactly it's called, but it's like an instruction file and it's basically setting the stage for this bot so it understands what it is and how it needs to work. And it's like saying you're a you know an expert level WordPress developer. You follow the WordPress coding standards linked to the standards. You follow these PHP standards linked to the you know, you give it these instructions so it knows who it is and how it needs to act. the the standards it needs to follow and then it really tightens up what it's doing. Right now it knows I'm a expert level WordPress. I'm gonna follow all these standards, right? **[02:02]** Here's the whole documentation I can go off of, you know? So, it it gets super sharp once you start feeding it those those rules rather than just saying code me something and chat GBT and it's like, okay, and it spits out something completely wrong. So, always trust but verify, but I like to challenge it sometimes when I know what the answer should be. See >> what it comes back with. It's interesting. Yeah, I I've uh taken to running anything I generate through plug-in check, which is what the uh the official plug-in repository uses to s to check against security and best practices and things like that. And I'm **[02:33]** always amazed at how many things come out unescaped. Uh you know, and so that that's kind of like, you know, the the um the process of kind of going through that and just verifying that, okay, now I can look at this and say, okay, this isn't secure. I've got to I I've got to fix this. Don't go straight to production, please. Just >> check it first, >> put it on a staging site and then see what it does. >> Yeah, I mean that that's exactly it. Trust by verify. Um, you know, make sure what it's producing. Always Yeah. Never do it directly in prod. Always dev, **[03:03]** always staging. Work in local environments. Um, you know, these systems are smart and they they can learn, right? Like so they can learn over time. They can understand your team's processes, your processes, your coding, your own coding standards, right? It doesn't just have to follow WordPress. You might have your own tweak on those standards and you just feed it all that right and train it to be your coding assistant your you know we always what we call the rubber duck right like you have that rubber duck when now you got AI you can rubber duck with AI say hey something's not right here I'm not quite sure you know what's going on what do you think and it's pretty wild um it's fun though it's it's just a new way **[03:34]** of coding you know and I think people either honestly you need to get on board or or you're going to get passed at this point from from development again it's not there to replace you but if you're not using these tools to help accelerate what you're doing and do some of the more routine monotonous stuff. All your all your peers are right. So, it's going to catch up to you at some point. >> Yeah. And you're pretty happy with the time you save, I think, too. I mean, it it it has made my day a lot easier. I know that. So, I it's something that, like I said, every level should probably be uh digging into this deeply now. >> Yeah. Yeah. I mean, and we haven't **[04:06]** talked about the marketing angle of it, right? Like all the emails we get now, like it's even more and there's there's they're getting so specific like, "Hey, I saw you worked on this project at that blah blah blah." like it's just scraping your LinkedIn and autogenerate like but they're getting smarter, right? They're getting smarter in what they say to try to get you to interact and be like, "Wait, how'd you know that?" you know, it's all coming through these AI systems, you know, and that's that they're just getting smarter because they can figure out the data and what you want to read or what you want to