<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" encoding="UTF-8" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/" xmlns:atom="http://www.w3.org/2005/Atom/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:fireside="http://fireside.fm/modules/rss/fireside">
  <channel>
    <fireside:hostname>app01</fireside:hostname>
    <fireside:genDate>Fri, 18 Sep 2026 16:56:15 +0000</fireside:genDate>
    <generator>Fireside (https://fireside.fm)</generator>
    <title>Software Defined Interviews - Episodes Tagged with “Devops”</title>
    <link>https://www.softwaredefinedinterviews.com/tags/devops</link>
    <pubDate>Wed, 02 Sep 2026 17:00:00 +0200</pubDate>
    <description>Deep discussions about technology, enterprise IT, and the like</description>
    <language>en-us</language>
    <itunes:type>episodic</itunes:type>
    <itunes:subtitle>Deep discussions about technology, enterprise IT, and the like</itunes:subtitle>
    <itunes:author>Software Defined Talk</itunes:author>
    <itunes:summary>Deep discussions about technology, enterprise IT, and the like</itunes:summary>
    <itunes:image href="https://media24.fireside.fm/file/fireside-images-2024/podcasts/images/7/752ee20c-8e7a-4ce1-8214-0a3fef88215c/cover.jpg?v=7"/>
    <itunes:explicit>yes</itunes:explicit>
    <itunes:owner>
      <itunes:name>Software Defined Talk</itunes:name>
      <itunes:email>softwaredefinedinterviews@cote.wtf</itunes:email>
    </itunes:owner>
<itunes:category text="Technology"/>
<itunes:category text="News">
  <itunes:category text="Tech News"/>
</itunes:category>
<itunes:category text="Business">
  <itunes:category text="Management"/>
</itunes:category>
<item>
  <title>Episode 126: DevOpsDays, Technical Storytelling, and Loading the Dishwasher, with Jason Yee</title>
  <link>https://www.softwaredefinedinterviews.com/126</link>
  <guid isPermaLink="false">8443b81d-88ac-4957-9971-75f56c7dab2a</guid>
  <pubDate>Wed, 02 Sep 2026 17:00:00 +0200</pubDate>
  <author>Software Defined Talk</author>
  <enclosure url="https://aphid.fireside.fm/d/1437767933/752ee20c-8e7a-4ce1-8214-0a3fef88215c/8443b81d-88ac-4957-9971-75f56c7dab2a.mp3" length="63582664" type="audio/mpeg"/>
  <itunes:episode>126</itunes:episode>
  <itunes:title>DevOpsDays, Technical Storytelling, and Loading the Dishwasher, with Jason Yee</itunes:title>
  <itunes:episodeType>full</itunes:episodeType>
  <itunes:author>Software Defined Talk</itunes:author>
  <itunes:subtitle>Jason Yee has two jobs that turn out to be the same job - Staff Technical Advocate at Datadog, and one of three global co-chairs of DevOpsDays - and both are about getting other people to talk. How the DevOpsDays machine actually runs, what sponsorship looks like now that DevOps is mature rather than hot, and why the sponsors doing well have stopped counting leads and started running workshops.</itunes:subtitle>
  <itunes:duration>1:05:03</itunes:duration>
  <itunes:explicit>yes</itunes:explicit>
  <itunes:image href="https://media24.fireside.fm/file/fireside-images-2024/podcasts/images/7/752ee20c-8e7a-4ce1-8214-0a3fef88215c/episodes/8/8443b81d-88ac-4957-9971-75f56c7dab2a/cover.jpg?v=1"/>
  <description>&lt;p&gt;Jason Yee is a Staff Technical Advocate at Datadog and one of three global co-chairs of DevOpsDays, and both jobs turn out to be mostly about getting other people to talk. Whitney and Coté ask him how the DevOpsDays machine actually works - local teams run the events, a global core team advises, and the co-chairs exist as a final escalation point - and what happens to conference sponsorship now that DevOps is mature rather than hot. His answer is that the sponsors who do well have stopped counting leads and started running workshops, on the grounds that a Lego giveaway gets you a list of people who wanted Lego.&lt;/p&gt;

&lt;p&gt;They also get into why DevOpsDays has a human streak that other tech subcultures never picked up, with Jason putting most of the "blame" on John Allspaw and safety science; Jason's Ignite talks in Amsterdam, including a DevOps children's book read aloud in his own bad Dutch; whether people drawn to systems are simply a particular kind of person, tested here by asking what everyone does when they open a badly loaded dishwasher; and Jason's actual day job, which is a technical storytelling team he thinks is the only one of its kind - talking Datadog engineers and executives into telling their own stories, then ghostwriting the session description and outline so they have something to react to instead of a blank page.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://devopsdays.org/events/2026-portland-or/welcome/" rel="nofollow noopener"&gt;DevOpsDays Portland&lt;/a&gt; is back for the first time since 2021, September 8 through 10, with Whitney giving both a workshop and a talk.&lt;/p&gt;

&lt;p&gt;Jason has no home page and would rather you did not look for him: "go touch grass, get outside, get some fresh air." If you don't like grass, and must Internet, he is on LinkedIn.&lt;/p&gt;

&lt;p&gt;Mentions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.linkedin.com/in/gitbisect/" rel="nofollow noopener"&gt;Jason Yee on LinkedIn&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;a href="https://devopsdays.org/events/2026-portland-or/" rel="nofollow noopener"&gt;DevOpsDays Portland&lt;/a&gt;, September 8-10, back for the first time since 2021.&lt;/li&gt;
&lt;li&gt;&lt;a href="https://devopsdays.org/events" rel="nofollow noopener"&gt;Every DevOpsDays, on a map&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.youtube.com/watch?v=LdOe18KhtT4" rel="nofollow noopener"&gt;John Allspaw and Paul Hammond, "10+ Deploys Per Day"&lt;/a&gt;, the Velocity 2009 talk that comes up.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Special Guest: Jason Yee. Special Guest: Jason Yee.&lt;/p&gt;
</description>
  <itunes:keywords>Jason Yee, Datadog, DevOpsDays, DevOpsDays Portland, DevOpsDays Amsterdam, global co-chair, conference organizing, conference sponsorship, sponsorship KPIs, lead generation, workshops, Ignite talks, open spaces, unconference, technical storytelling, developer advocacy, developer relations, ghostwriting, blank page problem, call for papers, speaker coaching, executive communications, product marketing, John Allspaw, blameless postmortem, safety science, resilience engineering, University of Lund, 10 deploys a day, Velocity, systems thinking, Thinking in Systems, DevOps, platform engineering, Portland, Portlandia, community conferences, volunteer organizing, code of conduct, introverts, dishwasher loading</itunes:keywords>
  <content:encoded>
    <![CDATA[<p>Jason Yee is a Staff Technical Advocate at Datadog and one of three global co-chairs of DevOpsDays, and both jobs turn out to be mostly about getting other people to talk. Whitney and Coté ask him how the DevOpsDays machine actually works - local teams run the events, a global core team advises, and the co-chairs exist as a final escalation point - and what happens to conference sponsorship now that DevOps is mature rather than hot. His answer is that the sponsors who do well have stopped counting leads and started running workshops, on the grounds that a Lego giveaway gets you a list of people who wanted Lego.</p>

<p>They also get into why DevOpsDays has a human streak that other tech subcultures never picked up, with Jason putting most of the "blame" on John Allspaw and safety science; Jason's Ignite talks in Amsterdam, including a DevOps children's book read aloud in his own bad Dutch; whether people drawn to systems are simply a particular kind of person, tested here by asking what everyone does when they open a badly loaded dishwasher; and Jason's actual day job, which is a technical storytelling team he thinks is the only one of its kind - talking Datadog engineers and executives into telling their own stories, then ghostwriting the session description and outline so they have something to react to instead of a blank page.</p>

<p><a href="https://devopsdays.org/events/2026-portland-or/welcome/" rel="nofollow noopener">DevOpsDays Portland</a> is back for the first time since 2021, September 8 through 10, with Whitney giving both a workshop and a talk.</p>

<p>Jason has no home page and would rather you did not look for him: "go touch grass, get outside, get some fresh air." If you don't like grass, and must Internet, he is on LinkedIn.</p>

<p>Mentions:</p>

<ul>
<li><a href="https://www.linkedin.com/in/gitbisect/" rel="nofollow noopener">Jason Yee on LinkedIn</a>.</li>
<li><a href="https://devopsdays.org/events/2026-portland-or/" rel="nofollow noopener">DevOpsDays Portland</a>, September 8-10, back for the first time since 2021.</li>
<li><a href="https://devopsdays.org/events" rel="nofollow noopener">Every DevOpsDays, on a map</a>.</li>
<li><a href="https://www.youtube.com/watch?v=LdOe18KhtT4" rel="nofollow noopener">John Allspaw and Paul Hammond, "10+ Deploys Per Day"</a>, the Velocity 2009 talk that comes up.</li>
</ul>

<p>Special Guest: Jason Yee.</p><p>Special Guest: Jason Yee.</p>]]>
  </content:encoded>
  <itunes:summary>
    <![CDATA[<p>Jason Yee is a Staff Technical Advocate at Datadog and one of three global co-chairs of DevOpsDays, and both jobs turn out to be mostly about getting other people to talk. Whitney and Coté ask him how the DevOpsDays machine actually works - local teams run the events, a global core team advises, and the co-chairs exist as a final escalation point - and what happens to conference sponsorship now that DevOps is mature rather than hot. His answer is that the sponsors who do well have stopped counting leads and started running workshops, on the grounds that a Lego giveaway gets you a list of people who wanted Lego.</p>

<p>They also get into why DevOpsDays has a human streak that other tech subcultures never picked up, with Jason putting most of the "blame" on John Allspaw and safety science; Jason's Ignite talks in Amsterdam, including a DevOps children's book read aloud in his own bad Dutch; whether people drawn to systems are simply a particular kind of person, tested here by asking what everyone does when they open a badly loaded dishwasher; and Jason's actual day job, which is a technical storytelling team he thinks is the only one of its kind - talking Datadog engineers and executives into telling their own stories, then ghostwriting the session description and outline so they have something to react to instead of a blank page.</p>

<p><a href="https://devopsdays.org/events/2026-portland-or/welcome/" rel="nofollow noopener">DevOpsDays Portland</a> is back for the first time since 2021, September 8 through 10, with Whitney giving both a workshop and a talk.</p>

<p>Jason has no home page and would rather you did not look for him: "go touch grass, get outside, get some fresh air." If you don't like grass, and must Internet, he is on LinkedIn.</p>

<p>Mentions:</p>

<ul>
<li><a href="https://www.linkedin.com/in/gitbisect/" rel="nofollow noopener">Jason Yee on LinkedIn</a>.</li>
<li><a href="https://devopsdays.org/events/2026-portland-or/" rel="nofollow noopener">DevOpsDays Portland</a>, September 8-10, back for the first time since 2021.</li>
<li><a href="https://devopsdays.org/events" rel="nofollow noopener">Every DevOpsDays, on a map</a>.</li>
<li><a href="https://www.youtube.com/watch?v=LdOe18KhtT4" rel="nofollow noopener">John Allspaw and Paul Hammond, "10+ Deploys Per Day"</a>, the Velocity 2009 talk that comes up.</li>
</ul>

<p>Special Guest: Jason Yee.</p><p>Special Guest: Jason Yee.</p>]]>
  </itunes:summary>
</item>
<item>
  <title>Episode 125: Running D&amp;D with AI, Determinism First, and Workflow ROI, with Michael Rishi Forrester</title>
  <link>https://www.softwaredefinedinterviews.com/125</link>
  <guid isPermaLink="false">3773701a-4bc5-418d-89fc-1f1c59419585</guid>
  <pubDate>Thu, 20 Aug 2026 09:00:00 +0200</pubDate>
  <author>Software Defined Talk</author>
  <enclosure url="https://aphid.fireside.fm/d/1437767933/752ee20c-8e7a-4ce1-8214-0a3fef88215c/3773701a-4bc5-418d-89fc-1f1c59419585.mp3" length="71641904" type="audio/mpeg"/>
  <itunes:episode>125</itunes:episode>
  <itunes:title>Running D&amp;D with AI, Determinism First, and Workflow ROI, with Michael Rishi Forrester</itunes:title>
  <itunes:episodeType>full</itunes:episodeType>
  <itunes:author>Software Defined Talk</itunes:author>
  <itunes:subtitle>Michael Rishi Forrester built his son a homebrew tabletop campaign with AI in the loop - 20 hours of work instead of 60 to 100 - and found out the hard way that the model had quietly started doing the dice math itself. That turns into an argument about why individuals get so much value out of AI while organizations get so little, and why the ROI is at the workflow level or nowhere.</itunes:subtitle>
  <itunes:duration>1:13:29</itunes:duration>
  <itunes:explicit>yes</itunes:explicit>
  <itunes:image href="https://media24.fireside.fm/file/fireside-images-2024/podcasts/images/7/752ee20c-8e7a-4ce1-8214-0a3fef88215c/episodes/3/3773701a-4bc5-418d-89fc-1f1c59419585/cover.jpg?v=1"/>
  <description>&lt;p&gt;Michael Rishi Forrester does AI workforce transformation at Accenture LearnVantage, after three years at KodeKloud and about thirty years in IT before that. Whitney and Coté talk with him about running tabletop role-playing games with AI. He built his 19-year-old son a homebrew campaign on top of Lancer, the sci-fi mech game, in about 20 hours instead of the 60 to 100 it would have taken him before - and got a website, a virtual tabletop and some Discord bots out of it. What breaks is the interesting part: there was a night when every shot did one damage, because the model had quietly stopped using the dice harness and started doing the math itself.&lt;/p&gt;

&lt;p&gt;From there it turns into an argument about where AI actually pays off at work. Michael’s position is that the ROI is at the workflow level and there is no organizational ROI to go find, that read-only work over more information than a person can hold is where it currently earns its keep, and that everything he has had success with is a bound system with a finite rule set. Whitney names the through-line: what can be deterministic should be deterministic, and if you need an LLM, scope it tightly and have it write the deterministic thing.&lt;/p&gt;

&lt;p&gt;It ends on mantis shrimp.&lt;/p&gt;

&lt;p&gt;You can watch &lt;a href="https://www.youtube.com/watch?v=HRVtMHbIAR0" rel="nofollow noopener"&gt;the video version of this episode&lt;/a&gt; as well, if you prefer that kind of thing.&lt;/p&gt;

&lt;p&gt;Mentions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;  &lt;a href="https://michaelrishiforrester.com/" rel="nofollow noopener"&gt;Michael Rishi Forrester’s home page on the World Wide Web&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;  &lt;a href="https://antiphonthegame.com/" rel="nofollow noopener"&gt;Antiphon: The Game&lt;/a&gt;, the homebrew Lancer campaign - the whole story, the missions, the board, and the sea-creature capital ships.&lt;/li&gt;
&lt;li&gt;  &lt;a href="https://www.linkedin.com/in/michaelrishiforrester/" rel="nofollow noopener"&gt;Michael on LinkedIn&lt;/a&gt;, where he posts most often.&lt;/li&gt;
&lt;li&gt;  &lt;a href="https://massifpress.com/lancer" rel="nofollow noopener"&gt;Lancer&lt;/a&gt;, the sci-fi mech game Antiphon is built on top of. Special Guest: Michael Rishi Forrester.&lt;/li&gt;
&lt;/ul&gt;
</description>
  <itunes:keywords>Michael Rishi Forrester, Accenture LearnVantage, KodeKloud, AI workforce transformation, Dungeons &amp; Dragons, Lancer, Antiphon, solo role-playing, tabletop RPG, application harness, determinism first, deterministic wrappers, MCP, Claude Code, agentic AI, hooks, LLM math, dice rolls, human in the loop, Air Force doctrine, intuition, judgment, enterprise ROI, workflow ROI, bound systems, read-only agents, context management, agent parallelism, alert fatigue, SOC 2 compliance, code review, regulated industries, layoffs, developer productivity, MIT Nanda report, Kubernetes, CI/CD, TDD, platform engineering</itunes:keywords>
  <content:encoded>
    <![CDATA[<p>Michael Rishi Forrester does AI workforce transformation at Accenture LearnVantage, after three years at KodeKloud and about thirty years in IT before that. Whitney and Coté talk with him about running tabletop role-playing games with AI. He built his 19-year-old son a homebrew campaign on top of Lancer, the sci-fi mech game, in about 20 hours instead of the 60 to 100 it would have taken him before - and got a website, a virtual tabletop and some Discord bots out of it. What breaks is the interesting part: there was a night when every shot did one damage, because the model had quietly stopped using the dice harness and started doing the math itself.</p>

<p>From there it turns into an argument about where AI actually pays off at work. Michael’s position is that the ROI is at the workflow level and there is no organizational ROI to go find, that read-only work over more information than a person can hold is where it currently earns its keep, and that everything he has had success with is a bound system with a finite rule set. Whitney names the through-line: what can be deterministic should be deterministic, and if you need an LLM, scope it tightly and have it write the deterministic thing.</p>

<p>It ends on mantis shrimp.</p>

<p>You can watch <a href="https://www.youtube.com/watch?v=HRVtMHbIAR0" rel="nofollow noopener">the video version of this episode</a> as well, if you prefer that kind of thing.</p>

<p>Mentions:</p>

<ul>
<li>  <a href="https://michaelrishiforrester.com/" rel="nofollow noopener">Michael Rishi Forrester’s home page on the World Wide Web</a>.</li>
<li>  <a href="https://antiphonthegame.com/" rel="nofollow noopener">Antiphon: The Game</a>, the homebrew Lancer campaign - the whole story, the missions, the board, and the sea-creature capital ships.</li>
<li>  <a href="https://www.linkedin.com/in/michaelrishiforrester/" rel="nofollow noopener">Michael on LinkedIn</a>, where he posts most often.</li>
<li>  <a href="https://massifpress.com/lancer" rel="nofollow noopener">Lancer</a>, the sci-fi mech game Antiphon is built on top of.</li>
</ul><p>Special Guest: Michael Rishi Forrester.</p>]]>
  </content:encoded>
  <itunes:summary>
    <![CDATA[<p>Michael Rishi Forrester does AI workforce transformation at Accenture LearnVantage, after three years at KodeKloud and about thirty years in IT before that. Whitney and Coté talk with him about running tabletop role-playing games with AI. He built his 19-year-old son a homebrew campaign on top of Lancer, the sci-fi mech game, in about 20 hours instead of the 60 to 100 it would have taken him before - and got a website, a virtual tabletop and some Discord bots out of it. What breaks is the interesting part: there was a night when every shot did one damage, because the model had quietly stopped using the dice harness and started doing the math itself.</p>

<p>From there it turns into an argument about where AI actually pays off at work. Michael’s position is that the ROI is at the workflow level and there is no organizational ROI to go find, that read-only work over more information than a person can hold is where it currently earns its keep, and that everything he has had success with is a bound system with a finite rule set. Whitney names the through-line: what can be deterministic should be deterministic, and if you need an LLM, scope it tightly and have it write the deterministic thing.</p>

<p>It ends on mantis shrimp.</p>

<p>You can watch <a href="https://www.youtube.com/watch?v=HRVtMHbIAR0" rel="nofollow noopener">the video version of this episode</a> as well, if you prefer that kind of thing.</p>

<p>Mentions:</p>

<ul>
<li>  <a href="https://michaelrishiforrester.com/" rel="nofollow noopener">Michael Rishi Forrester’s home page on the World Wide Web</a>.</li>
<li>  <a href="https://antiphonthegame.com/" rel="nofollow noopener">Antiphon: The Game</a>, the homebrew Lancer campaign - the whole story, the missions, the board, and the sea-creature capital ships.</li>
<li>  <a href="https://www.linkedin.com/in/michaelrishiforrester/" rel="nofollow noopener">Michael on LinkedIn</a>, where he posts most often.</li>
<li>  <a href="https://massifpress.com/lancer" rel="nofollow noopener">Lancer</a>, the sci-fi mech game Antiphon is built on top of.</li>
</ul><p>Special Guest: Michael Rishi Forrester.</p>]]>
  </itunes:summary>
</item>
<item>
  <title>Episode 124: The Chief Therapy Officer, Job Titles as Culture Change, and AI as Spreadsheets, with Bryan Ross</title>
  <link>https://www.softwaredefinedinterviews.com/124</link>
  <guid isPermaLink="false">a4a2167f-2cb9-4f13-af10-067073382ca9</guid>
  <pubDate>Wed, 05 Aug 2026 11:00:00 +0200</pubDate>
  <author>Software Defined Talk</author>
  <enclosure url="https://aphid.fireside.fm/d/1437767933/752ee20c-8e7a-4ce1-8214-0a3fef88215c/a4a2167f-2cb9-4f13-af10-067073382ca9.mp3" length="34023503" type="audio/mpeg"/>
  <itunes:episode>124</itunes:episode>
  <itunes:title>The Chief Therapy Officer, Job Titles as Culture Change, and AI as Spreadsheets, with Bryan Ross</itunes:title>
  <itunes:episodeType>full</itunes:episodeType>
  <itunes:author>Software Defined Talk</itunes:author>
  <itunes:subtitle></itunes:subtitle>
  <itunes:duration>1:09:48</itunes:duration>
  <itunes:explicit>yes</itunes:explicit>
  <itunes:image href="https://media24.fireside.fm/file/fireside-images-2024/podcasts/images/7/752ee20c-8e7a-4ce1-8214-0a3fef88215c/episodes/a/a4a2167f-2cb9-4f13-af10-067073382ca9/cover.jpg?v=1"/>
  <description>&lt;p&gt;Bryan Ross is a Field CTO at GitLab, a role he describes as straddling sales, customer success, and solution architecture - or, as one of his customers renamed it, chief therapy officer, which he has since turned into a Substack. Whitney and Coté talk with him about what the job actually looks like: getting catapulted into an account by the sales team, asking a lot of questions, and finding out about four minutes in that the tech problem is a human one. He makes the case that changing job titles - sysadmin, DevOps engineer, platform engineer, now context engineer - is mostly an organization trying to change its culture without knowing how, and that the real difference is mindset: keeping a box alive versus serving one team versus building a product. There’s a long stretch on metrics, including Goodhart’s law, why every metric needs a balancing one, and why he cared more about how many VMs were being decommissioned than how many were being provisioned. Also: whether anyone actually needs to ship faster (Coté’s pharmacy doesn’t), the UK Postal Service discovering that a friendly postman beat a modernized delivery fleet on customer satisfaction, and why copying Google is usually the wrong move. On AI, Bryan’s argument is that it will end up like spreadsheets - a few experts building the macros, everyone else using and lightly tinkering with what they made - and that which model you use should be a finance and data governance decision, not a developer one. Plus the hazard of a nicely formatted report: the pastel-shading trick for spreadsheets nobody will check, and why an AI scoring something 6 out of 10 gets the same unearned benefit of the doubt.&lt;/p&gt;

&lt;p&gt;Also, ordering pizza in Amsterdam.&lt;/p&gt;

&lt;p&gt;You can watch &lt;a href="https://www.youtube.com/watch?v=w184M4RtlIU" rel="nofollow noopener"&gt;the video version of this episode&lt;/a&gt; as well, if you prefer that kind of thing.&lt;/p&gt;

&lt;p&gt;Mentions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;  &lt;a href="https://bryanross.me/" rel="nofollow noopener"&gt;Bryan Ross’s home page on the World Wide Web&lt;/a&gt;, which links to everything else.&lt;/li&gt;
&lt;li&gt;  &lt;a href="https://chieftherapyofficer.co.uk/" rel="nofollow noopener"&gt;Chief Therapy Officer&lt;/a&gt;, Bryan’s Substack.&lt;/li&gt;
&lt;li&gt;  &lt;a href="https://www.linkedin.com/in/bryanross/" rel="nofollow noopener"&gt;Bryan on LinkedIn&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;  Coté's &lt;a href="https://cote.pizza/shit-people-say/" rel="nofollow noopener"&gt;list of "laws," anecdotes, and common shit people say&lt;/a&gt;. See also &lt;a href="https://hacker-laws.com/" rel="nofollow noopener"&gt;Hacker Laws&lt;/a&gt;. Special Guest: Bryan Ross.&lt;/li&gt;
&lt;/ul&gt;
</description>
  <itunes:keywords>Bryan Ross, GitLab, field CTO, chief therapy officer, platform engineering, DevOps engineer, job titles, sysadmin, context engineer, Goodhart’s law, metrics, balancing metrics, VM provisioning, decommissioning, repaving, microservices, monolith, LAMP stack, Kubernetes, golden paths, developer velocity, shipping faster, UK Postal Service, customer satisfaction, AI adoption, frontier models, model routing, FinOps for AI, agentic engineering, diffusion of innovations, Conway’s law, non-determinism, CI, coding agents, AI evaluation, tool sprawl, Jenkins, Tanzu, Substack, The New Stack</itunes:keywords>
  <content:encoded>
    <![CDATA[<p>Bryan Ross is a Field CTO at GitLab, a role he describes as straddling sales, customer success, and solution architecture - or, as one of his customers renamed it, chief therapy officer, which he has since turned into a Substack. Whitney and Coté talk with him about what the job actually looks like: getting catapulted into an account by the sales team, asking a lot of questions, and finding out about four minutes in that the tech problem is a human one. He makes the case that changing job titles - sysadmin, DevOps engineer, platform engineer, now context engineer - is mostly an organization trying to change its culture without knowing how, and that the real difference is mindset: keeping a box alive versus serving one team versus building a product. There’s a long stretch on metrics, including Goodhart’s law, why every metric needs a balancing one, and why he cared more about how many VMs were being decommissioned than how many were being provisioned. Also: whether anyone actually needs to ship faster (Coté’s pharmacy doesn’t), the UK Postal Service discovering that a friendly postman beat a modernized delivery fleet on customer satisfaction, and why copying Google is usually the wrong move. On AI, Bryan’s argument is that it will end up like spreadsheets - a few experts building the macros, everyone else using and lightly tinkering with what they made - and that which model you use should be a finance and data governance decision, not a developer one. Plus the hazard of a nicely formatted report: the pastel-shading trick for spreadsheets nobody will check, and why an AI scoring something 6 out of 10 gets the same unearned benefit of the doubt.</p>

<p>Also, ordering pizza in Amsterdam.</p>

<p>You can watch <a href="https://www.youtube.com/watch?v=w184M4RtlIU" rel="nofollow noopener">the video version of this episode</a> as well, if you prefer that kind of thing.</p>

<p>Mentions:</p>

<ul>
<li>  <a href="https://bryanross.me/" rel="nofollow noopener">Bryan Ross’s home page on the World Wide Web</a>, which links to everything else.</li>
<li>  <a href="https://chieftherapyofficer.co.uk/" rel="nofollow noopener">Chief Therapy Officer</a>, Bryan’s Substack.</li>
<li>  <a href="https://www.linkedin.com/in/bryanross/" rel="nofollow noopener">Bryan on LinkedIn</a>.</li>
<li>  Coté's <a href="https://cote.pizza/shit-people-say/" rel="nofollow noopener">list of "laws," anecdotes, and common shit people say</a>. See also <a href="https://hacker-laws.com/" rel="nofollow noopener">Hacker Laws</a>.</li>
</ul><p>Special Guest: Bryan Ross.</p>]]>
  </content:encoded>
  <itunes:summary>
    <![CDATA[<p>Bryan Ross is a Field CTO at GitLab, a role he describes as straddling sales, customer success, and solution architecture - or, as one of his customers renamed it, chief therapy officer, which he has since turned into a Substack. Whitney and Coté talk with him about what the job actually looks like: getting catapulted into an account by the sales team, asking a lot of questions, and finding out about four minutes in that the tech problem is a human one. He makes the case that changing job titles - sysadmin, DevOps engineer, platform engineer, now context engineer - is mostly an organization trying to change its culture without knowing how, and that the real difference is mindset: keeping a box alive versus serving one team versus building a product. There’s a long stretch on metrics, including Goodhart’s law, why every metric needs a balancing one, and why he cared more about how many VMs were being decommissioned than how many were being provisioned. Also: whether anyone actually needs to ship faster (Coté’s pharmacy doesn’t), the UK Postal Service discovering that a friendly postman beat a modernized delivery fleet on customer satisfaction, and why copying Google is usually the wrong move. On AI, Bryan’s argument is that it will end up like spreadsheets - a few experts building the macros, everyone else using and lightly tinkering with what they made - and that which model you use should be a finance and data governance decision, not a developer one. Plus the hazard of a nicely formatted report: the pastel-shading trick for spreadsheets nobody will check, and why an AI scoring something 6 out of 10 gets the same unearned benefit of the doubt.</p>

<p>Also, ordering pizza in Amsterdam.</p>

<p>You can watch <a href="https://www.youtube.com/watch?v=w184M4RtlIU" rel="nofollow noopener">the video version of this episode</a> as well, if you prefer that kind of thing.</p>

<p>Mentions:</p>

<ul>
<li>  <a href="https://bryanross.me/" rel="nofollow noopener">Bryan Ross’s home page on the World Wide Web</a>, which links to everything else.</li>
<li>  <a href="https://chieftherapyofficer.co.uk/" rel="nofollow noopener">Chief Therapy Officer</a>, Bryan’s Substack.</li>
<li>  <a href="https://www.linkedin.com/in/bryanross/" rel="nofollow noopener">Bryan on LinkedIn</a>.</li>
<li>  Coté's <a href="https://cote.pizza/shit-people-say/" rel="nofollow noopener">list of "laws," anecdotes, and common shit people say</a>. See also <a href="https://hacker-laws.com/" rel="nofollow noopener">Hacker Laws</a>.</li>
</ul><p>Special Guest: Bryan Ross.</p>]]>
  </itunes:summary>
</item>
<item>
  <title>Episode 123: Deming, DevOps History, AI Risk, and Critical Thinking, with John Willis</title>
  <link>https://www.softwaredefinedinterviews.com/123</link>
  <guid isPermaLink="false">8dd9a59d-ac29-4d39-a560-d39f2af295f3</guid>
  <pubDate>Sat, 06 Jun 2026 12:00:00 +0200</pubDate>
  <author>Software Defined Talk</author>
  <enclosure url="https://aphid.fireside.fm/d/1437767933/752ee20c-8e7a-4ce1-8214-0a3fef88215c/8dd9a59d-ac29-4d39-a560-d39f2af295f3.mp3" length="67286037" type="audio/mpeg"/>
  <itunes:episode>123</itunes:episode>
  <itunes:title>Deming, DevOps History, AI Risk, and Critical Thinking, with John Willis</itunes:title>
  <itunes:episodeType>full</itunes:episodeType>
  <itunes:author>Software Defined Talk</itunes:author>
  <itunes:subtitle></itunes:subtitle>
  <itunes:duration>1:09:32</itunes:duration>
  <itunes:explicit>yes</itunes:explicit>
  <itunes:image href="https://media24.fireside.fm/file/fireside-images-2024/podcasts/images/7/752ee20c-8e7a-4ce1-8214-0a3fef88215c/episodes/8/8dd9a59d-ac29-4d39-a560-d39f2af295f3/cover.jpg?v=1"/>
  <description>&lt;p&gt;W. Edwards Deming was a physicist, statistician, and quality theorist who taught post-war Japanese manufacturers what eventually became the Toyota Production System - and, decades later, DevOps. John Willis, one of the founders of the DevOps movement and the author of a book on Deming, walks Whitney and Coté through that lineage: Deming's system of profound knowledge (theory of knowledge, variation, psychology, and systems thinking), how it landed at Toyota, and how it threads through Lean software development into modern delivery practice. From there, the conversation turns to what the industry is getting wrong about AI: bragging about K-LOC and token counts instead of value, treating probabilistic systems with old deterministic notions of risk, and forgetting the social-technical lessons we already paid for. Along the way: VC moats and the buy-versus-build conversation inside large organizations, David Foster Wallace's "This is Water" and the ladder of inference, Jevons Paradox and whether AI gets us a three-day work week or a six-day one, and what CS students should be learning besides how to code. Also a brief detour into why John would want fifteen minutes with Bill Clinton.&lt;/p&gt;

&lt;p&gt;You can watch &lt;a href="https://www.youtube.com/watch?v=iIMp05f9d7Y" rel="nofollow noopener"&gt;the video version of this episode&lt;/a&gt; as well, if you prefer that kind of thing.&lt;/p&gt;

&lt;p&gt;Mentions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.linkedin.com/in/johnwillisatlanta/" rel="nofollow noopener"&gt;John on LinkedIn&lt;/a&gt; - the entry point to his author portal and writing.&lt;/li&gt;
&lt;li&gt;John's book on Deming, &lt;a href="https://itrevolution.com/product/demings-journey-to-profound-knowledge/" rel="nofollow noopener"&gt;&lt;em&gt;Deming's Journey to Profound Knowledge&lt;/em&gt;&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;John's book on AI, &lt;a href="https://www.rebelsofreason.com/" rel="nofollow noopener"&gt;&lt;em&gt;Rebels of Reason&lt;/em&gt;&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;a href="https://itrevolution.com/product/the-devops-handbook-second-edition/" rel="nofollow noopener"&gt;&lt;em&gt;The DevOps Handbook&lt;/em&gt;&lt;/a&gt;, which John co-authored with Gene Kim, Jez Humble, and Patrick Debois.&lt;/li&gt;
&lt;li&gt;Donella Meadows, &lt;a href="https://www.chelseagreen.com/product/thinking-in-systems/" rel="nofollow noopener"&gt;&lt;em&gt;Thinking in Systems&lt;/em&gt;&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Steven Spear, &lt;a href="https://www.mheducation.com/highered/product/high-velocity-edge-spear/9780071741415.html" rel="nofollow noopener"&gt;&lt;em&gt;The High-Velocity Edge&lt;/em&gt;&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Mary and Tom Poppendieck, &lt;a href="https://www.poppendieck.com/" rel="nofollow noopener"&gt;&lt;em&gt;Lean Software Development&lt;/em&gt;&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;David Foster Wallace, &lt;a href="https://fs.blog/david-foster-wallace-this-is-water/" rel="nofollow noopener"&gt;"This is Water"&lt;/a&gt; commencement speech.&lt;/li&gt;
&lt;li&gt;The 1980 NBC documentary &lt;a href="https://en.wikipedia.org/wiki/If_Japan_Can..._Why_Can%27t_We%3F" rel="nofollow noopener"&gt;&lt;em&gt;If Japan Can, Why Can't We?&lt;/em&gt;&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
</description>
  <itunes:keywords>John Willis, W. Edwards Deming, DevOps, history of DevOps, Toyota Production System, Lean software development, system of   profound knowledge, theory of knowledge, AI risk, probabilistic systems, K-LOC, Jevons Paradox, ladder of inference, David   Foster Wallace, This is Water, critical thinking, venture capital, buy versus build, DevOps Handbook, Rebels of Reason,   Gene Kim, Mary Poppendieck, Donella Meadows</itunes:keywords>
  <content:encoded>
    <![CDATA[<p>W. Edwards Deming was a physicist, statistician, and quality theorist who taught post-war Japanese manufacturers what eventually became the Toyota Production System - and, decades later, DevOps. John Willis, one of the founders of the DevOps movement and the author of a book on Deming, walks Whitney and Coté through that lineage: Deming's system of profound knowledge (theory of knowledge, variation, psychology, and systems thinking), how it landed at Toyota, and how it threads through Lean software development into modern delivery practice. From there, the conversation turns to what the industry is getting wrong about AI: bragging about K-LOC and token counts instead of value, treating probabilistic systems with old deterministic notions of risk, and forgetting the social-technical lessons we already paid for. Along the way: VC moats and the buy-versus-build conversation inside large organizations, David Foster Wallace's "This is Water" and the ladder of inference, Jevons Paradox and whether AI gets us a three-day work week or a six-day one, and what CS students should be learning besides how to code. Also a brief detour into why John would want fifteen minutes with Bill Clinton.</p>

<p>You can watch <a href="https://www.youtube.com/watch?v=iIMp05f9d7Y" rel="nofollow noopener">the video version of this episode</a> as well, if you prefer that kind of thing.</p>

<p>Mentions:</p>

<ul>
<li><a href="https://www.linkedin.com/in/johnwillisatlanta/" rel="nofollow noopener">John on LinkedIn</a> - the entry point to his author portal and writing.</li>
<li>John's book on Deming, <a href="https://itrevolution.com/product/demings-journey-to-profound-knowledge/" rel="nofollow noopener"><em>Deming's Journey to Profound Knowledge</em></a>.</li>
<li>John's book on AI, <a href="https://www.rebelsofreason.com/" rel="nofollow noopener"><em>Rebels of Reason</em></a>.</li>
<li><a href="https://itrevolution.com/product/the-devops-handbook-second-edition/" rel="nofollow noopener"><em>The DevOps Handbook</em></a>, which John co-authored with Gene Kim, Jez Humble, and Patrick Debois.</li>
<li>Donella Meadows, <a href="https://www.chelseagreen.com/product/thinking-in-systems/" rel="nofollow noopener"><em>Thinking in Systems</em></a>.</li>
<li>Steven Spear, <a href="https://www.mheducation.com/highered/product/high-velocity-edge-spear/9780071741415.html" rel="nofollow noopener"><em>The High-Velocity Edge</em></a>.</li>
<li>Mary and Tom Poppendieck, <a href="https://www.poppendieck.com/" rel="nofollow noopener"><em>Lean Software Development</em></a>.</li>
<li>David Foster Wallace, <a href="https://fs.blog/david-foster-wallace-this-is-water/" rel="nofollow noopener">"This is Water"</a> commencement speech.</li>
<li>The 1980 NBC documentary <a href="https://en.wikipedia.org/wiki/If_Japan_Can..._Why_Can%27t_We%3F" rel="nofollow noopener"><em>If Japan Can, Why Can't We?</em></a>.</li>
</ul>]]>
  </content:encoded>
  <itunes:summary>
    <![CDATA[<p>W. Edwards Deming was a physicist, statistician, and quality theorist who taught post-war Japanese manufacturers what eventually became the Toyota Production System - and, decades later, DevOps. John Willis, one of the founders of the DevOps movement and the author of a book on Deming, walks Whitney and Coté through that lineage: Deming's system of profound knowledge (theory of knowledge, variation, psychology, and systems thinking), how it landed at Toyota, and how it threads through Lean software development into modern delivery practice. From there, the conversation turns to what the industry is getting wrong about AI: bragging about K-LOC and token counts instead of value, treating probabilistic systems with old deterministic notions of risk, and forgetting the social-technical lessons we already paid for. Along the way: VC moats and the buy-versus-build conversation inside large organizations, David Foster Wallace's "This is Water" and the ladder of inference, Jevons Paradox and whether AI gets us a three-day work week or a six-day one, and what CS students should be learning besides how to code. Also a brief detour into why John would want fifteen minutes with Bill Clinton.</p>

<p>You can watch <a href="https://www.youtube.com/watch?v=iIMp05f9d7Y" rel="nofollow noopener">the video version of this episode</a> as well, if you prefer that kind of thing.</p>

<p>Mentions:</p>

<ul>
<li><a href="https://www.linkedin.com/in/johnwillisatlanta/" rel="nofollow noopener">John on LinkedIn</a> - the entry point to his author portal and writing.</li>
<li>John's book on Deming, <a href="https://itrevolution.com/product/demings-journey-to-profound-knowledge/" rel="nofollow noopener"><em>Deming's Journey to Profound Knowledge</em></a>.</li>
<li>John's book on AI, <a href="https://www.rebelsofreason.com/" rel="nofollow noopener"><em>Rebels of Reason</em></a>.</li>
<li><a href="https://itrevolution.com/product/the-devops-handbook-second-edition/" rel="nofollow noopener"><em>The DevOps Handbook</em></a>, which John co-authored with Gene Kim, Jez Humble, and Patrick Debois.</li>
<li>Donella Meadows, <a href="https://www.chelseagreen.com/product/thinking-in-systems/" rel="nofollow noopener"><em>Thinking in Systems</em></a>.</li>
<li>Steven Spear, <a href="https://www.mheducation.com/highered/product/high-velocity-edge-spear/9780071741415.html" rel="nofollow noopener"><em>The High-Velocity Edge</em></a>.</li>
<li>Mary and Tom Poppendieck, <a href="https://www.poppendieck.com/" rel="nofollow noopener"><em>Lean Software Development</em></a>.</li>
<li>David Foster Wallace, <a href="https://fs.blog/david-foster-wallace-this-is-water/" rel="nofollow noopener">"This is Water"</a> commencement speech.</li>
<li>The 1980 NBC documentary <a href="https://en.wikipedia.org/wiki/If_Japan_Can..._Why_Can%27t_We%3F" rel="nofollow noopener"><em>If Japan Can, Why Can't We?</em></a>.</li>
</ul>]]>
  </itunes:summary>
</item>
<item>
  <title>Episode 30: Patrick Debois on using serverless for a year and half, defining DevOps vs. SRE vs. design, and meatware over tools</title>
  <link>https://www.softwaredefinedinterviews.com/30</link>
  <guid isPermaLink="false">45beeb3c-86e9-4a64-9e8d-b1e882820e26</guid>
  <pubDate>Fri, 26 May 2017 17:00:00 +0200</pubDate>
  <author>Software Defined Talk</author>
  <enclosure url="https://aphid.fireside.fm/d/1437767933/752ee20c-8e7a-4ce1-8214-0a3fef88215c/45beeb3c-86e9-4a64-9e8d-b1e882820e26.mp3" length="7346305" type="audio/mp3"/>
  <itunes:episode>30</itunes:episode>
  <itunes:title>Patrick Debois on using serverless for a year and half, defining DevOps vs. SRE vs. design, and meatware over tools</itunes:title>
  <itunes:episodeType>full</itunes:episodeType>
  <itunes:author>Software Defined Talk</itunes:author>
  <itunes:subtitle>At DevOpsDays Austin, 2017, [Barton George](https://twitter.com/barton808) and [I](https://twitter.com/cote) talk with [Patrick Debois](https://twitter.com/patrickdebois).</itunes:subtitle>
  <itunes:duration>13:50</itunes:duration>
  <itunes:explicit>yes</itunes:explicit>
  <itunes:image href="https://media24.fireside.fm/file/fireside-images-2024/podcasts/images/7/752ee20c-8e7a-4ce1-8214-0a3fef88215c/episodes/4/45beeb3c-86e9-4a64-9e8d-b1e882820e26/cover.jpg?v=1"/>
  <description>&lt;p&gt;At DevOpsDays Austin, 2017, &lt;a href="https://twitter.com/barton808" rel="nofollow noopener"&gt;Barton George&lt;/a&gt; and &lt;a href="https://twitter.com/cote" rel="nofollow noopener"&gt;I&lt;/a&gt; talk with &lt;a href="https://twitter.com/patrickdebois" rel="nofollow noopener"&gt;Patrick Debois&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;See also &lt;a href="https://www.youtube.com/watch?v=NDCmQEJyh50" rel="nofollow noopener"&gt;a video of this interview&lt;/a&gt;. Special Guests: Barton George and Patrick Debois.&lt;/p&gt;
</description>
  <content:encoded>
    <![CDATA[<p>At DevOpsDays Austin, 2017, <a href="https://twitter.com/barton808" rel="nofollow noopener">Barton George</a> and <a href="https://twitter.com/cote" rel="nofollow noopener">I</a> talk with <a href="https://twitter.com/patrickdebois" rel="nofollow noopener">Patrick Debois</a>.</p>

<p>See also <a href="https://www.youtube.com/watch?v=NDCmQEJyh50" rel="nofollow noopener">a video of this interview</a>.</p><p>Special Guests: Barton George and Patrick Debois.</p>]]>
  </content:encoded>
  <itunes:summary>
    <![CDATA[<p>At DevOpsDays Austin, 2017, <a href="https://twitter.com/barton808" rel="nofollow noopener">Barton George</a> and <a href="https://twitter.com/cote" rel="nofollow noopener">I</a> talk with <a href="https://twitter.com/patrickdebois" rel="nofollow noopener">Patrick Debois</a>.</p>

<p>See also <a href="https://www.youtube.com/watch?v=NDCmQEJyh50" rel="nofollow noopener">a video of this interview</a>.</p><p>Special Guests: Barton George and Patrick Debois.</p>]]>
  </itunes:summary>
</item>
<item>
  <title>Episode 25: John Willis on DevOps, inclusion, burn-out, and biz dev</title>
  <link>https://www.softwaredefinedinterviews.com/25</link>
  <guid isPermaLink="false">2f99fb2c-c484-48c5-90ef-4a1f79042a59</guid>
  <pubDate>Thu, 11 May 2017 14:00:00 +0200</pubDate>
  <author>Software Defined Talk</author>
  <enclosure url="https://aphid.fireside.fm/d/1437767933/752ee20c-8e7a-4ce1-8214-0a3fef88215c/2f99fb2c-c484-48c5-90ef-4a1f79042a59.mp3" length="7122512" type="audio/mp3"/>
  <itunes:episode>25</itunes:episode>
  <itunes:title>John Willis on DevOps, inclusion, burn-out, and biz dev</itunes:title>
  <itunes:episodeType>full</itunes:episodeType>
  <itunes:author>Software Defined Talk</itunes:author>
  <itunes:subtitle>Barton George and I talk with John Willis at DevOpsDays Austin 2017.</itunes:subtitle>
  <itunes:duration>13:09</itunes:duration>
  <itunes:explicit>yes</itunes:explicit>
  <itunes:image href="https://media24.fireside.fm/file/fireside-images-2024/podcasts/images/7/752ee20c-8e7a-4ce1-8214-0a3fef88215c/episodes/2/2f99fb2c-c484-48c5-90ef-4a1f79042a59/cover.jpg?v=1"/>
  <description>&lt;p&gt;Special Guest: Barton George.&lt;/p&gt;
</description>
  <content:encoded>
    <![CDATA[]]>
  </content:encoded>
  <itunes:summary>
    <![CDATA[]]>
  </itunes:summary>
</item>
<item>
  <title>Episode 19: Computers are easy. Humans are Hard. With Bridget Kromhout</title>
  <link>https://www.softwaredefinedinterviews.com/19</link>
  <guid isPermaLink="false">9b6e24e9-4543-4cd4-990c-dd4e9f4a2cbb</guid>
  <pubDate>Fri, 27 Jan 2017 22:00:00 +0100</pubDate>
  <author>Software Defined Talk</author>
  <enclosure url="https://aphid.fireside.fm/d/1437767933/752ee20c-8e7a-4ce1-8214-0a3fef88215c/9b6e24e9-4543-4cd4-990c-dd4e9f4a2cbb.mp3" length="15574430" type="audio/mpeg"/>
  <itunes:episode>19</itunes:episode>
  <itunes:title>Computers are easy. Humans are Hard. With Bridget Kromhout</itunes:title>
  <itunes:episodeType>full</itunes:episodeType>
  <itunes:author>Software Defined Talk</itunes:author>
  <itunes:subtitle>We discuss all the human and process changes needed to do good things with computers.</itunes:subtitle>
  <itunes:duration>31:12</itunes:duration>
  <itunes:explicit>yes</itunes:explicit>
  <itunes:image href="https://media24.fireside.fm/file/fireside-images-2024/podcasts/images/7/752ee20c-8e7a-4ce1-8214-0a3fef88215c/episodes/9/9b6e24e9-4543-4cd4-990c-dd4e9f4a2cbb/cover.jpg?v=1"/>
  <description>&lt;p&gt;We discuss all the human and process changes needed to do good things with computers. Special Guest: Bridget Kromhout.&lt;/p&gt;
</description>
  <content:encoded>
    <![CDATA[<p>We discuss all the human and process changes needed to do good things with computers.</p><p>Special Guest: Bridget Kromhout.</p><p>Links:</p><ul><li><a title="Video recording of this episode" rel="nofollow" href="https://www.facebook.com/drunkandretired/videos/10155012857744169/">Video recording of this episode
</a> &mdash; The livestreamed recording we did.
</li></ul>]]>
  </content:encoded>
  <itunes:summary>
    <![CDATA[<p>We discuss all the human and process changes needed to do good things with computers.</p><p>Special Guest: Bridget Kromhout.</p><p>Links:</p><ul><li><a title="Video recording of this episode" rel="nofollow" href="https://www.facebook.com/drunkandretired/videos/10155012857744169/">Video recording of this episode
</a> &mdash; The livestreamed recording we did.
</li></ul>]]>
  </itunes:summary>
</item>
  </channel>
</rss>
