<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Coding-Standards on No Semicolons</title><link>https://nosemicolons.com/tags/coding-standards/</link><description>Recent content in Coding-Standards on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 10 Apr 2026 09:01:32 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/coding-standards/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Consistency Problem: How to Maintain Coding Standards When Every AI Has Different Opinions</title><link>https://nosemicolons.com/posts/ai-code-consistency-standards/</link><pubDate>Fri, 10 Apr 2026 09:01:32 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-consistency-standards/</guid><description>&lt;p>Ever notice how Claude writes functions differently than ChatGPT? Or how Copilot&amp;rsquo;s suggestions sometimes clash with your team&amp;rsquo;s established patterns? You&amp;rsquo;re not alone in this AI code consistency puzzle.&lt;/p>
&lt;p>I&amp;rsquo;ve been wrestling with this challenge across multiple projects lately. One day I&amp;rsquo;m pair programming with Claude and getting beautifully structured TypeScript with detailed JSDoc comments. The next day, I switch to GitHub Copilot and suddenly my codebase is filled with terse variable names and inline logic that would make my past self cringe.&lt;/p></description></item></channel></rss>