<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Culture on Bits, Trades &amp; Systems</title>
    <link>https://blog.turboawesome.win/tags/culture/</link>
    <description>Recent content in Culture on Bits, Trades &amp; Systems</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 05 Oct 2022 11:27:00 +0000</lastBuildDate>
    <atom:link href="https://blog.turboawesome.win/tags/culture/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Postmortems as a Learning Tool: Structure, Culture, and Follow-Through</title>
      <link>https://blog.turboawesome.win/2022/10/postmortems-as-a-learning-tool-structure-culture-and-follow-through/</link>
      <pubDate>Wed, 05 Oct 2022 11:27:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2022/10/postmortems-as-a-learning-tool-structure-culture-and-follow-through/</guid>
      <description>A postmortem that concludes with &amp;#39;be more careful&amp;#39; has failed. The structure and culture of blameless postmortems, and why follow-through is where most teams fall short.</description>
    </item>
    <item>
      <title>On-Call Culture That Doesn&#39;t Burn Out Your Team</title>
      <link>https://blog.turboawesome.win/2022/07/on-call-culture-that-doesnt-burn-out-your-team/</link>
      <pubDate>Wed, 06 Jul 2022 09:55:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2022/07/on-call-culture-that-doesnt-burn-out-your-team/</guid>
      <description>On-call is a forcing function for reliability — when engineers are paged for their own systems, the feedback loop on quality is immediate. Done badly, it burns out your team. The practices that keep it sustainable.</description>
    </item>
  </channel>
</rss>
