<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>2026 on Andy M Mallon - AM²</title><link>https://am2.co/2026/</link><description>Recent content in 2026 on Andy M Mallon - AM²</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 27 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://am2.co/2026/index.xml" rel="self" type="application/rss+xml"/><item><title>am2.co just got a new look</title><link>https://am2.co/2026/10/27/new-look/</link><pubDate>Tue, 27 Oct 2026 00:00:00 +0000</pubDate><guid>https://am2.co/2026/10/27/new-look/</guid><description>&lt;p&gt;This site was starting to get a little dusty. Things change fast in tech&amp;mdash;as database folk, we often think of technologies, languages, and capabilities&amp;mdash;but design and UX are constantly evolving, too. The styling and the design were both starting to look a bit dated, and &amp;ldquo;a bit dated&amp;rdquo; is not a term I want associated with my professional blog/website. I haven&amp;rsquo;t been writing a ton of new content, so I also haven&amp;rsquo;t been putting in the incremental upkeep. Anyway&amp;hellip;let&amp;rsquo;s talk about my updates.&lt;/p&gt;</description></item><item><title>Crawling out of my hole to write more</title><link>https://am2.co/2026/10/26/back-to-writing/</link><pubDate>Mon, 26 Oct 2026 00:00:00 +0000</pubDate><guid>https://am2.co/2026/10/26/back-to-writing/</guid><description>&lt;p&gt;I haven&amp;rsquo;t been blogging much over the past couple of years. I&amp;rsquo;m crawling out of my hole to write again, and I hope to post more regularly. That&amp;rsquo;s what everyone says when they come back, though, so we&amp;rsquo;ll see if I actually follow through.&lt;/p&gt;&#10;&lt;p&gt;What&amp;rsquo;s bringing me back to writing? One reason is that AI has become a practical tool in my day-to-day work, and I want to write about how I use it. Expect the familiar topics—HA/DR, performance tuning, and professional development—with AI alongside SSMS as a standard part of the toolkit.&lt;/p&gt;</description></item><item><title>Your documentation belongs with your code</title><link>https://am2.co/2026/10/your-documentation-belongs-with-the-code/</link><pubDate>Tue, 13 Oct 2026 11:02:59 -0400</pubDate><guid>https://am2.co/2026/10/your-documentation-belongs-with-the-code/</guid><description>&lt;p&gt;For years, I&amp;rsquo;ve advocated for keeping developer documentation in the same code repository as the code it describes. In the age of AI, that practice has become even more important.&lt;/p&gt;&#10;&lt;p&gt;The reason is simple: &lt;strong&gt;the easier we make it to maintain documentation, the more likely it is to stay current.&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>Clear, Concise, Complete, and Correct: Avoiding AI Slop</title><link>https://am2.co/2026/09/clear-concise-complete-and-correct-avoiding-ai-slop/</link><pubDate>Mon, 28 Sep 2026 16:58:36 -0400</pubDate><guid>https://am2.co/2026/09/clear-concise-complete-and-correct-avoiding-ai-slop/</guid><description>&lt;p&gt;There’s a particular kind of writing that has become increasingly easy to produce: technically plausible, grammatically correct, reasonably well organized, and almost completely exhausting to read.&lt;/p&gt;&#10;&lt;p&gt;You know the stuff&amp;ndash;it has a lot of words. It has headings for everything. It explains things that don&amp;rsquo;t need explaining, repeats the same point three different ways, and somehow manages to leave out the details you actually needed.&lt;/p&gt;</description></item></channel></rss>