<?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>Newops on Brave New Geek</title><link>https://bravenewgeek.com/tag/newops/</link><description>Recent content in Newops on Brave New Geek</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 07 Dec 2020 11:23:20 -0500</lastBuildDate><atom:link href="https://bravenewgeek.com/tag/newops/index.xml" rel="self" type="application/rss+xml"/><item><title>Scaling DevOps and the Revival of Operations</title><link>https://bravenewgeek.com/scaling-devops-and-the-revival-of-operations/</link><pubDate>Wed, 18 Apr 2018 10:07:42 -0500</pubDate><guid>https://bravenewgeek.com/scaling-devops-and-the-revival-of-operations/</guid><description>&lt;p&gt;Operations is going through a renaissance right now. With the move to cloud, the increasing amount of automation, and the increasing &lt;em&gt;importance&lt;/em&gt; of automation, Ops as we know it is reinventing itself out of necessity. Infrastructure is becoming more and more sophisticated—and commoditized—and practices are just now starting to grow up around that. So while some worry about robots taking our jobs, the reality is more about how automation will help augment us to build better software and focus on higher-value things. It’s not so much about the &lt;em&gt;distant&lt;/em&gt; future—whatever that may hold—so much as it is about the next five to ten years, what Operations looks like in that timeframe, and why I think it has to retool.&lt;/p&gt;</description></item><item><title>The Future of Ops</title><link>https://bravenewgeek.com/the-future-of-ops/</link><pubDate>Wed, 03 May 2017 20:12:57 -0500</pubDate><guid>https://bravenewgeek.com/the-future-of-ops/</guid><description>&lt;p&gt;Traditional Operations isn’t going away, it’s just retooling. The move from on-premise to cloud means Ops, in the classical sense, is largely being outsourced to cloud providers. This is the buzzword-compliant &lt;em&gt;NoOps movement&lt;/em&gt;, of which many call the “successor” to DevOps, though that word has become &lt;a href="https://medium.com/@cindysridharan/what-is-devops-5b0181fdb953"&gt;pretty diluted&lt;/a&gt; these days. What this leaves is a thin but crucial slice between Amazon and the products built by development teams, encompassing infrastructure automation, deployment automation, configuration management, log management, and monitoring and instrumentation.&lt;/p&gt;</description></item></channel></rss>