<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blog</title><link>https://blog.rickwaterman.com/</link><description>Recent content on Blog</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sat, 27 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.rickwaterman.com/index.xml" rel="self" type="application/rss+xml"/><item><title>MacBooks in Enterprise IT: A Practical Modernization Playbook for Technical Leadership</title><link>https://blog.rickwaterman.com/posts/macbooks-in-enterprise-it/</link><pubDate>Sat, 27 Jun 2026 00:00:00 +0000</pubDate><guid>https://blog.rickwaterman.com/posts/macbooks-in-enterprise-it/</guid><description>For engineering roles, MacBooks are a first-class enterprise endpoint — manageable through modern identity and MDM controls, supportable inside Microsoft-centered environments, and worth standardizing for secure, low-friction execution.</description></item><item><title>Vercel Is Great for Frontend Teams</title><link>https://blog.rickwaterman.com/posts/vercel-is-great-for-frontend-teams/</link><pubDate>Tue, 24 Feb 2026 00:00:00 +0000</pubDate><guid>https://blog.rickwaterman.com/posts/vercel-is-great-for-frontend-teams/</guid><description>Vercel&amp;rsquo;s developer experience is the best in the business, and for a frontend team without cloud depth it is the right call. But if your organization already has AWS CDK or Terraform specialization, you are paying a markup on Lambda and CloudFront for an abstraction you do not need, with spend controls that lag, private networking behind an Enterprise contract, and a self-hosting story that has finally caught up.</description></item><item><title>It's All Just AWS Under the Hood</title><link>https://blog.rickwaterman.com/posts/its-all-just-aws-under-the-hood/</link><pubDate>Tue, 11 Mar 2025 00:00:00 +0000</pubDate><guid>https://blog.rickwaterman.com/posts/its-all-just-aws-under-the-hood/</guid><description>Vercel, Netlify, Supabase, Heroku, Render, PlanetScale: open their region docs and you find AWS region codes. The platforms are thin layers over primitives you can learn directly. Deep AWS specialization — with real fluency in CDK and Terraform — is not narrowing. It is the thing that lets you use any of them, and leave any of them.</description></item><item><title>If You Are Not Part of the Implementation, You Are Part of the Problem</title><link>https://blog.rickwaterman.com/posts/if-you-are-not-part-of-the-implementation/</link><pubDate>Tue, 14 May 2024 00:00:00 +0000</pubDate><guid>https://blog.rickwaterman.com/posts/if-you-are-not-part-of-the-implementation/</guid><description>An architect who does not ship code has no feedback loop, and an architecture with no feedback loop is a guess with a diagram. Own a real piece of the build — the hard module, the infrastructure as code, the review queue — or accept that the team will route around you.</description></item><item><title>Boring Managed Services Win</title><link>https://blog.rickwaterman.com/posts/boring-managed-services-win/</link><pubDate>Mon, 04 Dec 2023 00:00:00 +0000</pubDate><guid>https://blog.rickwaterman.com/posts/boring-managed-services-win/</guid><description>Every queue, scheduler, or database you run yourself spends an innovation token on something your customers will never notice. Managed AWS services are boring in the best sense: their failure modes are documented, their metrics ship by default, and the toil they remove is the toil nobody measures.</description></item><item><title>About</title><link>https://blog.rickwaterman.com/about/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://blog.rickwaterman.com/about/</guid><description/></item></channel></rss>