<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Posts on Corrupted Glitch</title>
		<link>https://corruptedglitch.netlify.app/posts/</link>
		<description>Recent content in Posts on Corrupted Glitch</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sat, 18 Jul 2026 23:13:02 -0400</lastBuildDate>
		
			<atom:link href="https://corruptedglitch.netlify.app/posts/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Field Manual: The CORRUPTED_GLITCH Shortcode Arsenal</title>
				<link>https://corruptedglitch.netlify.app/posts/shortcode-field-manual/</link>
				<pubDate>Sat, 18 Jul 2026 10:00:00 -0500</pubDate>
				<guid>https://corruptedglitch.netlify.app/posts/shortcode-field-manual/</guid>
				<description>&lt;p&gt;This transmission is a live-fire range for the theme&amp;rsquo;s component arsenal. Every shortcode in &lt;code&gt;layouts/shortcodes/&lt;/code&gt; fires at least once below — copy the source of this file as your reference when writing new articles.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Automating the Great Escape: Cloud Migration Pipelines with an AI Copilot in the Loop</title>
				<link>https://corruptedglitch.netlify.app/posts/sample-devops-migration/</link>
				<pubDate>Tue, 14 Jul 2026 09:00:00 -0500</pubDate>
				<guid>https://corruptedglitch.netlify.app/posts/sample-devops-migration/</guid>
				<description>&lt;p&gt;Every datacenter exit starts the same way: someone opens a spreadsheet with 1,400 rows, and someone else says &amp;ldquo;we&amp;rsquo;ll just lift and shift.&amp;rdquo; Eighteen months later, half the estate is still on-prem and the spreadsheet has become sentient.&lt;/p&gt;&#xA;&lt;p&gt;This is a field report from a migration that didn&amp;rsquo;t go that way — 140 production workloads moved in 11 months, zero rollback events. The difference wasn&amp;rsquo;t heroics. It was treating the migration as a &lt;strong&gt;factory&lt;/strong&gt;, not a project, and putting an AI copilot inside the loop where humans were the bottleneck.&lt;/p&gt;</description>
			</item>
			<item>
				<title>MSP Migrations by the Numbers: What 200 Client Moves Taught Us</title>
				<link>https://corruptedglitch.netlify.app/posts/msp-migrations-by-the-numbers/</link>
				<pubDate>Tue, 30 Jun 2026 09:00:00 -0500</pubDate>
				<guid>https://corruptedglitch.netlify.app/posts/msp-migrations-by-the-numbers/</guid>
				<description>&lt;p&gt;Managed service providers migrate other people&amp;rsquo;s infrastructure for a living, which means the dataset is bigger and more honest than any single enterprise&amp;rsquo;s war story. This post aggregates anonymized data from &lt;strong&gt;214 client migrations&lt;/strong&gt; executed between 2021 and 2026 — SMB to mid-market, 20 to 2,000 seats.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Managing macOS at Scale with Fleet: MDM Without the Black Box</title>
				<link>https://corruptedglitch.netlify.app/posts/macos-mdm-with-fleet/</link>
				<pubDate>Tue, 26 May 2026 09:00:00 -0500</pubDate>
				<guid>https://corruptedglitch.netlify.app/posts/macos-mdm-with-fleet/</guid>
				<description>&lt;p&gt;Most MDM products are black boxes: you click checkboxes in a vendor console and &lt;em&gt;trust&lt;/em&gt; that the right profile landed on the right Mac. Fleet inverts that. It&amp;rsquo;s open source, it&amp;rsquo;s built on osquery, and every piece of device state is a queryable table. Here&amp;rsquo;s how to run macOS management on it without regretting your choices.&lt;/p&gt;</description>
			</item>
			<item>
				<title>The DevOps Home Lab: A Production Mindset on a Power Strip</title>
				<link>https://corruptedglitch.netlify.app/posts/devops-home-lab/</link>
				<pubDate>Tue, 21 Apr 2026 09:00:00 -0500</pubDate>
				<guid>https://corruptedglitch.netlify.app/posts/devops-home-lab/</guid>
				<description>&lt;p&gt;A home lab is only useful if it teaches you habits that transfer to production. A pile of Raspberry Pis running hand-configured containers teaches you how to hand-configure containers. This guide builds the opposite: a small estate you operate &lt;em&gt;like an SRE&lt;/em&gt;, because the operating model — not the hardware — is the thing you&amp;rsquo;re practicing.&lt;/p&gt;</description>
			</item>
			<item>
				<title>AWS vs. Google Cloud vs. Azure: A Field Guide for People Who Sign the Bill</title>
				<link>https://corruptedglitch.netlify.app/posts/aws-gcp-azure-field-guide/</link>
				<pubDate>Tue, 17 Mar 2026 09:00:00 -0500</pubDate>
				<guid>https://corruptedglitch.netlify.app/posts/aws-gcp-azure-field-guide/</guid>
				<description>&lt;p&gt;Every cloud comparison ends the same way: &amp;ldquo;it depends on your workload.&amp;rdquo; True, useless. After running production estates on all three, here&amp;rsquo;s the comparison that actually matters — how each cloud &lt;em&gt;behaves&lt;/em&gt; as an operating environment, and which organizational failure mode each one invites.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
