<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>System Design on Brent Hollers</title><link>https://brenthollers.com/tags/system-design/</link><description>Recent content in System Design on Brent Hollers</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 20 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://brenthollers.com/tags/system-design/index.xml" rel="self" type="application/rss+xml"/><item><title>A Real Take on the Practical Implications of AI in Tech</title><link>https://brenthollers.com/posts/ai-in-the-workforce/my-take-on-ai/</link><pubDate>Fri, 20 Mar 2026 00:00:00 +0000</pubDate><guid>https://brenthollers.com/posts/ai-in-the-workforce/my-take-on-ai/</guid><description>&lt;h1 id="ai-is-a-powerful-tool-its-not-a-replacement-for-knowing-what-youre-doing"&gt;AI Is a Powerful Tool. It&amp;rsquo;s Not a Replacement for Knowing What You&amp;rsquo;re Doing.&lt;/h1&gt;
&lt;p&gt;&lt;em&gt;By Dr. Brent Hollers&lt;/em&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;There&amp;rsquo;s a conversation happening in nearly every tech team, IT department, and engineering org right now. It usually goes one of two ways: either AI is going to replace us all, or AI is completely overhyped and we should stop worrying about it. The truth, as usual, lives somewhere in the middle — and it&amp;rsquo;s a lot more interesting than either extreme.&lt;/p&gt;</description></item><item><title>How I Built a $7/Month DNS Caching Resolver for a K-12 School Using AWS and Terraform</title><link>https://brenthollers.com/posts/dns-cache-system/building-low-cost-dns-service/</link><pubDate>Fri, 20 Mar 2026 00:00:00 +0000</pubDate><guid>https://brenthollers.com/posts/dns-cache-system/building-low-cost-dns-service/</guid><description>&lt;h1&gt;&lt;/h1&gt;
&lt;p&gt;&lt;em&gt;By Dr. Brent Hollers | Director of Information Technology, St. Mary&amp;rsquo;s Academy&lt;/em&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;Every year, PSAT morning arrives like a controlled fire drill. Hundreds of Chromebooks come online simultaneously, every student navigating to the same handful of testing URLs. The network holds. The internet connection holds. But something subtle bogs down the experience in those first critical minutes: DNS.&lt;/p&gt;
&lt;p&gt;Most IT professionals don&amp;rsquo;t think about DNS until something breaks. I didn&amp;rsquo;t either — until I started looking at where time was actually being lost during high-concurrency events at our school. Every single device was firing DNS queries at external resolvers (Cloudflare, Google) independently, with no local caching. The same hostname, resolved a thousand times, with zero shared benefit. It was like every student in the building individually calling 411 to ask for the same phone number.&lt;/p&gt;</description></item><item><title>IaC Part 1: From Manual Chaos to Infrastructure as Code: Designing a School Absence System</title><link>https://brenthollers.com/posts/absence-system-iac/part-1-building-with-terraform/</link><pubDate>Sun, 15 Feb 2026 00:00:00 +0000</pubDate><guid>https://brenthollers.com/posts/absence-system-iac/part-1-building-with-terraform/</guid><description>&lt;h1 id="from-manual-chaos-to-infrastructure-as-code-designing-a-school-absence-system"&gt;From Manual Chaos to Infrastructure as Code: Designing a School Absence System&lt;/h1&gt;
&lt;p&gt;&lt;em&gt;Part 1 of 4: Building Production-Grade Infrastructure&lt;/em&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="the-745-am-problem"&gt;The 7:45 AM Problem&lt;/h2&gt;
&lt;p&gt;It&amp;rsquo;s 7:45 AM on a Tuesday morning. The school secretary&amp;rsquo;s phone rings. It&amp;rsquo;s Mrs. Johnson calling in sick—again. The secretary scribbles a note on a sticky pad, crosses off Mrs. Johnson&amp;rsquo;s name on the coverage spreadsheet, and starts making calls to find a substitute for periods 3, 5, and 7.&lt;/p&gt;</description></item></channel></rss>