<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Code-Quality on Advancing Engineering</title><link>https://www.advancingengineering.dev/tags/code-quality/</link><description>Recent content in Code-Quality on Advancing Engineering</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 09 May 2026 16:04:11 +0100</lastBuildDate><atom:link href="https://www.advancingengineering.dev/tags/code-quality/index.xml" rel="self" type="application/rss+xml"/><item><title>The Anti-Pattern: One Language Inside Another</title><link>https://www.advancingengineering.dev/posts/2026-05-anti-patterns-one-language-inside-another/</link><pubDate>Fri, 08 May 2026 10:54:36 +0100</pubDate><guid>https://www.advancingengineering.dev/posts/2026-05-anti-patterns-one-language-inside-another/</guid><description>&lt;p&gt;Placing one language inside another is one of those anti-patterns that seems harmless until you&amp;rsquo;re trying to lint it, test it, or ask an LLM to reason about it. The moment you embed a language inside a string in another language, its entire toolchain disappears.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;We &lt;strong&gt;contain multitudes&lt;/strong&gt;. Our code should be singular, not polyglot.&lt;/p&gt;
&lt;/blockquote&gt;</description></item></channel></rss>