<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Ai on Lets Automate It</title>
		<link>https://letsautomate.it/tags/ai/</link>
		<description>Recent content in Ai on Lets Automate It</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Mon, 29 Jun 2026 00:00:00 -0600</lastBuildDate>
		
			<atom:link href="https://letsautomate.it/tags/ai/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Beyond the Prompt: The Social Costs of Generative Artificial Intelligence</title>
				<link>https://letsautomate.it/article/beyond-the-prompt-social-costs-of-generative-ai/</link>
				<pubDate>Mon, 29 Jun 2026 00:00:00 -0600</pubDate>
				<guid>https://letsautomate.it/article/beyond-the-prompt-social-costs-of-generative-ai/</guid>
				<description>&lt;p&gt;The rapid commercialization of generative artificial intelligence has produced extraordinary value for technology companies while systematically externalizing costs onto society. Co-authored with J. Scott Christianson, this article provides a review of these externalities across three domains: environmental, human health, and digital infrastructure. The environmental burden includes massive energy and water consumption alongside ecologically destructive mining for rare earth elements and accelerating electronic waste.&lt;/p&gt;&#xA;&lt;p&gt;The human toll encompasses a documented pattern of AI-induced mental health crises, including suicide and self-harm linked to anthropomorphic chatbot design, raising novel questions of product liability. The digital commons face degradation through industrialized data scraping that has effectively stripped platforms of their primary legal defenses. Our argument is straightforward: the AI industry&amp;rsquo;s business model is predicated on a fundamental market failure—the privatization of benefit and socialization of cost.&lt;/p&gt;</description>
			</item>
			<item>
				<title>How I Use LLMs for Security Work: Part 2</title>
				<link>https://letsautomate.it/article/how-i-use-llms-for-security-work-part-2/</link>
				<pubDate>Thu, 05 Mar 2026 14:00:00 -0600</pubDate>
				<guid>https://letsautomate.it/article/how-i-use-llms-for-security-work-part-2/</guid>
				<description>&lt;p&gt;I previously wrote a blog for THOR Collective Dispatch about some basic examples of different approaches when it comes to LLMs. It was cool and I hope it truly helps those starting out but I wanted to follow up and share some other more specific examples, including more &amp;ldquo;advanced&amp;rdquo; patterns that have worked for me over the past year or so.&lt;/p&gt;&#xA;&lt;p&gt;We&amp;rsquo;ve all seen the scope, complexity and rise of usage of LLMs from products which integrate them, to all new product categories to ClawdBot. If you&amp;rsquo;re not familiar with all the facets of LLMs that&amp;rsquo;s okay but before I dive into these more advanced use cases, I think it&amp;rsquo;s advantageous to understand some terminology (at a high-level) when it comes to LLMs.&lt;/p&gt;</description>
			</item>
			<item>
				<title>How I Use LLMs for Security Work</title>
				<link>https://letsautomate.it/article/how-i-use-llms-for-security-work/</link>
				<pubDate>Tue, 03 Feb 2026 14:00:00 -0600</pubDate>
				<guid>https://letsautomate.it/article/how-i-use-llms-for-security-work/</guid>
				<description>&lt;p&gt;I&amp;rsquo;ve been using LLM tools like Claude, Cursor, and ChatGPT extensively in my security &amp;amp; engineering work for the past couple years. Not as a replacement for thinking—but they genuinely help me move faster through complex problems. If you&amp;rsquo;re a security analyst, SOC analyst, threat hunter or engineer who hasn&amp;rsquo;t found a rhythm with these tools yet, I&amp;rsquo;ll try to share what&amp;rsquo;s been working for me with the hope it helps you too.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
