102 lines
5.3 KiB
HTML
102 lines
5.3 KiB
HTML
<p><a class="email_only" href="https://sreweekly.com/sre-weekly-issue-534/">View on sreweekly.com</a></p>
|
||
|
||
<div class="sreweekly-sponsor-message" style="border: 1px solid #b0b0b0; width: 80%;">
|
||
<h2 style="text-align: center; font-size: 80%; color: #909090;">A message from our sponsor, <a href="https://sreweekly.com/link/534">Planetscale</a>:</h2>
|
||
<p>Neki brings horizontal sharding to Postgres. It handles the hard parts of running Postgres at scale:</p>
|
||
<ul>
|
||
<li>Online schema changes</li>
|
||
<li>Version upgrades with no downtime</li>
|
||
<li>Better connection pooling</li>
|
||
<li>Resharding</li>
|
||
<li>Graceful planned and unplanned failovers</li>
|
||
</ul>
|
||
<p>→ Neki is available today. <a href="https://sreweekly.com/link/534"><u>Learn more.</u></a></p>
|
||
</div>
|
||
|
||
|
||
<div class="wp-block-group"><div class="wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow">
|
||
<div class="sreweekly-entry">
|
||
<div class="sreweekly-title"><a href="https://www.sylvainkalache.com/blog/ai-handles-incidents-engineers-lose-touch-with-their-systems" target="_blank">AI handles incidents, engineers lose touch with their systems</a></div>
|
||
<div class="sreweekly-description">
|
||
<blockquote>
|
||
<p>The better these tools become at resolving routine incidents, the less practice human responders will get. And when an ambiguous, high-severity incident comes in that automation cannot solve, responding engineers will be in trouble.</p>
|
||
</blockquote>
|
||
<p>I love the concept of <em>comprehension debt</em> described in this article.</p>
|
||
<p> <small>Sylvain Kalache</small></p>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
|
||
<div class="sreweekly-entry">
|
||
<div class="sreweekly-title"><a href="https://surfingcomplexity.blog/2026/08/18/tough-days-at-github-a-continuing-series/" target="_blank">Tough days at GitHub, a continuing series</a></div>
|
||
<div class="sreweekly-description">
|
||
<p>Another excellent write-up by my favorite writer of incident write-up write-ups. I especially like that last section.</p>
|
||
<p>Lorin also <a href="https://surfingcomplexity.blog/2026/08/19/github-autoscaling-and-the-component-substitution-fallacy/">wrote more the next day</a>.</p>
|
||
<p> <small>Lorin Hochstein</small></p>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
|
||
<div class="sreweekly-entry">
|
||
<div class="sreweekly-title"><a href="https://greatcircle.com/blog/2026/08/18/how-senior-leaders-disrupt-incidents-by-showing-up/" target="_blank">How senior leaders disrupt incidents just by showing up</a></div>
|
||
<div class="sreweekly-description">
|
||
<blockquote>
|
||
<p>A VP’s question […] lands with the weight of the org chart behind it, and everyone in the channel feels it.</p>
|
||
</blockquote>
|
||
<p>I especially liked the sections toward the end on how to mitigate a leader’s impact.</p>
|
||
<p> <small>Brent Chapman</small></p>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
|
||
<div class="sreweekly-entry">
|
||
<div class="sreweekly-title"><a href="https://bluetriangle.com/blog/empowering-retail-excellence-how-lowes-sre-team-is-driving-reliability-through-hyper-automation-and-unified-platforms" target="_blank">How Lowe’s SRE Team is Driving Reliability Through Hyper Automation and Unified Platforms</a></div>
|
||
<div class="sreweekly-description">
|
||
<p>Lowe’s has an intensive (and intense) SRE practice that provides client teams with a framework of tools to ensure reliability.</p>
|
||
<p> <small>Raghuprasanth Ravichandran, Joe Praveena A, and Pavan Palagiri</small></p>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
|
||
<div class="sreweekly-entry">
|
||
<div class="sreweekly-title"><a href="https://hackernoon.com/before-you-automate-a-decision-define-its-blast-radius" target="_blank">Before You Automate a Decision, Define Its Blast Radius</a></div>
|
||
<div class="sreweekly-description">
|
||
<p>How far will the impact of an incorrect automated decision spread? Will it get integrated into the system and influence later decisions?</p>
|
||
<p> <small>Sai Sandeep Koneti — HackerNoon</small></p>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
|
||
<div class="sreweekly-entry">
|
||
<div class="sreweekly-title"><a href="https://www.gremlin.com/blog/managing-kubernetes-node-drains-with-pod-disruption-budgets" target="_blank">Managing Kubernetes node drains with Pod Disruption Budgets</a></div>
|
||
<div class="sreweekly-description">
|
||
<p>A great primer on how pod disruption budgets work and why they’re critical for reliability.</p>
|
||
<p> <small>Andre Newman — Gremlin</small></p>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
|
||
<div class="sreweekly-entry">
|
||
<div class="sreweekly-title"><a href="https://www.checklyhq.com/blog/agentic-rewrite-nodejs-to-go" target="_blank">Rewriting a Node.js Service in Go With AI Agents</a></div>
|
||
<div class="sreweekly-description">
|
||
<p>They took a systematic approach using test-driven development. I enjoyed not only learning what went well, but where they ran into trouble.</p>
|
||
<p> <small>Edvinas Janusevicius — Checkly</small></p>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
|
||
<div class="sreweekly-entry">
|
||
<div class="sreweekly-title"><a href="https://www.uptimelabs.io/articles/supporting-new-responders" target="_blank">Supporting Your Team’s New Responders</a></div>
|
||
<div class="sreweekly-description">
|
||
<p>Great advice if you’re training early-career engineers on incident response. This advice reminds me of some of the techniques that folks used with me when I was starting out.</p>
|
||
<p> <small>Karan Nagarajagowda — Uptime Labs</small></p>
|
||
</div>
|
||
</div>
|
||
</div></div> |