<?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 JoeSindel.com</title><link>https://joesindel.com/posts/</link><description>Recent content in Posts on JoeSindel.com</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 10 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://joesindel.com/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>One-to-Many Beacon Nodes: Rethinking PoS Validator Topology</title><link>https://joesindel.com/posts/ethereum-beacon-node-topology/</link><pubDate>Sun, 10 May 2026 00:00:00 +0000</pubDate><guid>https://joesindel.com/posts/ethereum-beacon-node-topology/</guid><description>&lt;p>A proof-of-stake validator is not a monolith. It&amp;rsquo;s three processes coordinating tightly: a &lt;strong>validator client&lt;/strong> signing attestations and proposing blocks, a &lt;strong>beacon node&lt;/strong> participating in consensus, and an &lt;strong>execution client&lt;/strong> running EVM state. The simplest deployment binds them 1:1:1 — one validator paired with one beacon, one beacon paired with one execution client. That topology is fine when you&amp;rsquo;re running 32 ETH worth of stake on a home setup. It is not fine when you&amp;rsquo;re operating at the scale of a top-tier staking provider.&lt;/p></description></item><item><title>What Major Incident Command Actually Buys You</title><link>https://joesindel.com/posts/major-incident-command-playbook/</link><pubDate>Sun, 10 May 2026 00:00:00 +0000</pubDate><guid>https://joesindel.com/posts/major-incident-command-playbook/</guid><description>&lt;p>A SEV at company scale isn&amp;rsquo;t a bigger version of an outage on a small team. It&amp;rsquo;s a different problem. Once you have dozens of services on the page, multiple product surfaces affected, regulators watching, executives asking questions, and customer comms running in parallel with engineering response — the thing that breaks first is coordination, not engineering capability.&lt;/p>
&lt;p>This post is about what the IMAG / Incident Command System framework actually buys you in that environment, where I&amp;rsquo;ve seen it get misapplied, and the part most teams skip: making the post-mortem loop close.&lt;/p></description></item><item><title>Building a Private AI Server with NVIDIA Jetson AGX Thor</title><link>https://joesindel.com/posts/thor-ai-home-server/</link><pubDate>Sat, 25 Apr 2026 00:00:00 +0000</pubDate><guid>https://joesindel.com/posts/thor-ai-home-server/</guid><description>&lt;p>A few days ago I got my hands on an NVIDIA Jetson AGX Thor developer kit. 128GB of unified memory, a Blackwell GPU, and enough raw compute to run serious language models locally. This post covers the full build: three inference backends, voice chat from my phone over cellular, video-based object detection, a complete monitoring pipeline, and a custom dashboard. Everything survives a reboot, nothing touches the cloud.&lt;/p>
&lt;hr>
&lt;h2 id="the-hardware">The Hardware&lt;/h2>
&lt;p>The Jetson AGX Thor is not a consumer product. It&amp;rsquo;s a developer kit built for robotics and edge AI workloads. The specs that matter for LLM inference:&lt;/p></description></item></channel></rss>