<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Decision-Making on Chris Wagner</title><link>/tags/decision-making/</link><description>Recent content in Decision-Making on Chris Wagner</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>cw@wagner.org.za (Chrisando Wagner)</managingEditor><webMaster>cw@wagner.org.za (Chrisando Wagner)</webMaster><copyright>© 2026 Chrisando Wagner</copyright><lastBuildDate>Mon, 03 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="/tags/decision-making/index.xml" rel="self" type="application/rss+xml"/><item><title>How I Actually Make Trade-off Calls — Not Just What I Build</title><link>/posts/principal-architecture-tradeoffs/</link><pubDate>Mon, 03 Aug 2026 00:00:00 +0000</pubDate><author>cw@wagner.org.za (Chrisando Wagner)</author><guid>/posts/principal-architecture-tradeoffs/</guid><description>&lt;p&gt;If you&amp;rsquo;ve already read the build logs — the k3s cluster, the storage classes, the failover drill — you know &lt;em&gt;what&lt;/em&gt; I build. This post is about the part that doesn&amp;rsquo;t show up in a &lt;code&gt;terraform apply&lt;/code&gt; output: how I actually decide something, in the moment a plan stops matching reality, and what I do about it afterward.&lt;/p&gt;
&lt;p&gt;That&amp;rsquo;s a different question than &amp;ldquo;what technology did you pick,&amp;rdquo; and it&amp;rsquo;s the one I think actually separates senior from principal-level work. Anyone competent can execute a plan that goes to schedule. What I&amp;rsquo;m going to walk through is a plan that didn&amp;rsquo;t, twenty minutes into a homelab rebuild, and the small, unglamorous decision that followed it — because that decision is a better sample of how I&amp;rsquo;ll behave on your platform than any tool list is.&lt;/p&gt;</description></item></channel></rss>