<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: AI Assistants and Their Failings	</title>
	<atom:link href="https://ivorphotography.co.uk/ai-assistants/feed/" rel="self" type="application/rss+xml" />
	<link>https://ivorphotography.co.uk/ai-assistants/</link>
	<description>Leading Quality Photography in Northumberland</description>
	<lastBuildDate>Tue, 04 Aug 2026 17:29:01 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0.3</generator>
	<item>
		<title>
		By: Ivor		</title>
		<link>https://ivorphotography.co.uk/ai-assistants/#comment-15250</link>

		<dc:creator><![CDATA[Ivor]]></dc:creator>
		<pubDate>Tue, 04 Aug 2026 17:29:01 +0000</pubDate>
		<guid isPermaLink="false">https://ivorphotography.co.uk/?p=8305#comment-15250</guid>

					<description><![CDATA[Hi Emmet, I suspected that your comment was AI-generated, so I pasted it into various AI detection tools. They all confirm that you have used AI to write it. 

Generative AI is a useful tool, but I enjoy writing to my clients. I think they appreciate the personal replies too. While I might use it to automate mundane tasks, I prefer the human touch both when sending and receiving correspondence. 

Each to their own, of course. 

You are right that it needs to be double-checked. I recently, for fun, got Copilot to write a document, then got it fact-checked by ChatGPT, which found errors. It corrected the errors, and I ran it through Google. It found more faults. I fed that back into Copilot and asked it to check, and it found fault with the corrections.  

Thanks for taking the time to comment.]]></description>
			<content:encoded><![CDATA[<p>Hi Emmet, I suspected that your comment was AI-generated, so I pasted it into various AI detection tools. They all confirm that you have used AI to write it. </p>
<p>Generative AI is a useful tool, but I enjoy writing to my clients. I think they appreciate the personal replies too. While I might use it to automate mundane tasks, I prefer the human touch both when sending and receiving correspondence. </p>
<p>Each to their own, of course. </p>
<p>You are right that it needs to be double-checked. I recently, for fun, got Copilot to write a document, then got it fact-checked by ChatGPT, which found errors. It corrected the errors, and I ran it through Google. It found more faults. I fed that back into Copilot and asked it to check, and it found fault with the corrections.  </p>
<p>Thanks for taking the time to comment.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Emmet		</title>
		<link>https://ivorphotography.co.uk/ai-assistants/#comment-15171</link>

		<dc:creator><![CDATA[Emmet]]></dc:creator>
		<pubDate>Sat, 01 Aug 2026 23:00:55 +0000</pubDate>
		<guid isPermaLink="false">https://ivorphotography.co.uk/?p=8305#comment-15171</guid>

					<description><![CDATA[The self-destruction point is the structurally interesting one. If AI assistants route people away from the original sources they were trained on, and those sources lose enough revenue to close, the training pool shrinks — a loop that degrades the tool over time.

The confidence problem can be worse than the accuracy problem. When Copilot gives the wrong operating temperature for your camera, it delivers that answer in exactly the same tone and format as when it&#039;s correct, with no signal in the output to tell you which situation you&#039;re in. The cross-checking approach described here is the sensible response, but it eats most of the time-saving the tool was supposed to deliver.

I use AI for client correspondence and the admin side of running a photography business. For broad questions it holds up well enough. For anything specific (particular gear specs, venues I regularly work with through LemonLens, current supplier pricing) checking is still necessary. A tool that confidently gives the wrong answer to a specific question can be more hazardous than no answer at all.]]></description>
			<content:encoded><![CDATA[<p>The self-destruction point is the structurally interesting one. If AI assistants route people away from the original sources they were trained on, and those sources lose enough revenue to close, the training pool shrinks — a loop that degrades the tool over time.</p>
<p>The confidence problem can be worse than the accuracy problem. When Copilot gives the wrong operating temperature for your camera, it delivers that answer in exactly the same tone and format as when it&#8217;s correct, with no signal in the output to tell you which situation you&#8217;re in. The cross-checking approach described here is the sensible response, but it eats most of the time-saving the tool was supposed to deliver.</p>
<p>I use AI for client correspondence and the admin side of running a photography business. For broad questions it holds up well enough. For anything specific (particular gear specs, venues I regularly work with through LemonLens, current supplier pricing) checking is still necessary. A tool that confidently gives the wrong answer to a specific question can be more hazardous than no answer at all.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
