<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>devops on Further Heitz</title>
    <link>/tags/devops/</link>
    <description>Recent content in devops on Further Heitz</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>Kelly Heitz</copyright>
    <lastBuildDate>Thu, 07 Mar 2024 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="/tags/devops/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Speed and Safety</title>
      <link>/post/speed_and_safety/</link>
      <pubDate>Thu, 07 Mar 2024 00:00:00 +0000</pubDate>
      
      <guid>/post/speed_and_safety/</guid>
      <description>&amp;ldquo;You have to go slow to go fast.&amp;quot;
and
Speed is safety&amp;rdquo;
Both of these phrases are oft-quoted in software. Each have individually been well-explained by better writers and engineers than me, but I think the combination can get confusing when we talk about innovation and building new software systems.
The best metaphor I have for this is downhill skiing (I did a lot of ski racing in high school).</description>
    </item>
    
  </channel>
</rss>