<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:media="http://search.yahoo.com/mrss/">
<channel>
<title>Thoughts on in the net</title>
<link>https://terrty.net/tags/thoughts/</link>
<description>Recent content in Thoughts on in the net</description>
<generator>Hugo</generator>
<language>en</language>
<managingEditor>paskal.07@gmail.com (Dmitry Verkhoturov)</managingEditor>
<webMaster>paskal.07@gmail.com (Dmitry Verkhoturov)</webMaster>
<copyright>Dmitry Verkhoturov</copyright>
<lastBuildDate>Fri, 29 Dec 2023 22:44:11 +0000</lastBuildDate>
<atom:link href="https://terrty.net/tags/thoughts/index.xml" rel="self" type="application/rss+xml"/>
<item>
<title>Site Reliability Engineering vs DevOps</title>
<link>https://terrty.net/2020/sre-vs-devops/</link>
<media:rating scheme="urn:simple">nonadult</media:rating>
<pubDate>Thu, 06 Feb 2020 06:15:00 +0000</pubDate><author>paskal.07@gmail.com (Dmitry Verkhoturov)</author>
<guid>https://terrty.net/2020/sre-vs-devops/</guid>
<description>&lt;p&gt;Recently on many occasions, I&amp;rsquo;ve had to explain the difference between SRE and DevOps practitioners and thought it might be helpful to write it down.&lt;/p&gt;
&lt;p&gt;DevOps are making developers happy by increasing development velocity.&lt;/p&gt;
&lt;p&gt;Site Reliability Engineers are making business happy by providing meaningful and comprehensible visibility into technical systems&amp;rsquo; health. The key is the ability to communicate risk in the same terms to both business and technical stakeholders.&lt;/p&gt;</description>
<enclosure url="https://terrty.net/thumbnail.jpg" length="438598" type="image/jpg"/>
</item>
</channel>
</rss>