<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Eric Johnson on Medium]]></title>
        <description><![CDATA[Stories by Eric Johnson on Medium]]></description>
        <link>https://medium.com/@thatericjohnson?source=rss-29d4465c2beb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*KQvOjJ4p11Oxky623AwHTw.jpeg</url>
            <title>Stories by Eric Johnson on Medium</title>
            <link>https://medium.com/@thatericjohnson?source=rss-29d4465c2beb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 21:52:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@thatericjohnson/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Docker build on Mac M1]]></title>
            <link>https://medium.com/@thatericjohnson/docker-build-on-mac-m1-b76963201a24?source=rss-29d4465c2beb------2</link>
            <guid isPermaLink="false">https://medium.com/p/b76963201a24</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[mac]]></category>
            <dc:creator><![CDATA[Eric Johnson]]></dc:creator>
            <pubDate>Tue, 11 Apr 2023 23:08:34 GMT</pubDate>
            <atom:updated>2023-04-11T23:08:34.343Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GPqy-YoNdJK0VOd2DM9OUQ.jpeg" /><figcaption><a href="https://www.apple.com/newsroom/2021/04/imac-features-all-new-design-in-vibrant-colors-m1-chip-and-45k-retina-display/">Mac Website</a></figcaption></figure><p>A docker container is supposed to work everywhere and eliminate the need to worry about dependencies, right? I was frustrated when a Docker image built on my Mac M1 did not work on my Linux machine. Well, it turns out you need to do a little more if you have a Mac with the new M1 chip.</p><p>The M1 uses arm64 architecture instead of the amd64 architecture used on most machines. Any image you build on a Mac M1 and run on another machine will give you the following error message.</p><blockquote>WARNING: The requested image’s platform (linux/arm64/v8) does not match the detected host platform (linux/amd64/v3) and no specific platform was requested</blockquote><p>If you run a docker ps you will find there are no containers running. If you run the following command, you will see the following error.</p><pre>Docker logs <br>exec /usr/local/bin/python: exec format error</pre><p>To resolve this, on a Mac M1 always build images with the `platform` switch.</p><pre>docker build \ <br>-t image_name:1.0 \ <br> - platform linux/amd64 \ <br>.</pre><p>This will allow an image built on the Mac M1 (with arm64) to work on a Linux machine (typically with amd64). You can still run this amd64 image on a Mac M1 even though it gives you the following warning message.</p><blockquote>WARNING: The requested image’s platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested</blockquote><p>You can build a <a href="https://docs.docker.com/build/building/multi-platform/">multi-platform image</a> to create a docker image for all the architectures you expect to need and avoid any errors, but it is much more complicated.</p><p>Thanks for reading! See <a href="https://thatericjohnson.tech/digital-garden/dev-ops-commands/docker-build-on-mac-m1/">my Digital Garden</a> for this and related articles. Follow me on Mastodon at @thatericjohnson@seattlematrix.org.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b76963201a24" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dive Deep to Do Great Work]]></title>
            <link>https://medium.com/@thatericjohnson/dive-deep-to-do-great-work-fc6d4ebf8623?source=rss-29d4465c2beb------2</link>
            <guid isPermaLink="false">https://medium.com/p/fc6d4ebf8623</guid>
            <category><![CDATA[growth-mindset]]></category>
            <category><![CDATA[competitive-advantage]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[organization]]></category>
            <category><![CDATA[efficiency]]></category>
            <dc:creator><![CDATA[Eric Johnson]]></dc:creator>
            <pubDate>Fri, 09 Sep 2022 23:33:49 GMT</pubDate>
            <atom:updated>2022-09-09T23:33:49.406Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2jTRx0RPbKN1pii3" /><figcaption>Photo by <a href="https://unsplash.com/@cristianpalmer?utm_source=medium&amp;utm_medium=referral">Cristian Palmer</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Do you wonder how some people produce great work when they don’t seem to have much time? Do you want to achieve better results in less time? Do you want to master difficult concepts more quickly? Then you need to read, “Deep Work: Rules for Focussed Success in a Distracted World”, by Cal Newport. Here is a summary of the key ideas in the book that will make you better at what you do and make work more fulfilling.</p><p><a href="https://www.calnewport.com/books/deep-work/">Cal Newport</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IpUC5c2aNezOaxEAfHirSA.jpeg" /></figure><h3>High Quality Work = Time x Focus</h3><p>High quality work on a complicated task is not just pushing hard to put the hours in. To learn hard things quickly, you must focus intently without distraction. We struggle to make progress on a complicated task if our thought process is interrupted by meetings or emails. We need un-interrupted time to learn a new tool or craft new code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TLOcU_ns8XEkqfGb5uCcqQ.jpeg" /></figure><p>People are less productive when they are constantly moving from one task to another instead of focusing on one thing at a time. We need to stop thinking about one task in order to fully transition our attention and perform well on another. Yet, results indicate it is difficult for people to transition their attention away from an unfinished task and their subsequent task performance suffers.</p><p>This carryover from one task to another is called “attention residue” — where you’re still thinking of a previous task as you start another one. Even if you finish your task completely, you still have some attention residue swirling around your head as you embark on your next task.</p><blockquote>Focusing on a single, intense task for a long period of time to reach peak productivity. You don’t get attention-residue issues, which means your output is stronger, cleaner, and just plain better from a lack of distractions.</blockquote><h3>Busyness as a Proxy for Productivity</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XM7e47VoeGFZJJZdvYPXEw.jpeg" /></figure><p>Without clear feedback to connect behaviors to business impact, we tend toward behaviors that are easiest in the moment. In technology work, there is no clear measurement of productivity. There is no metric for widgets created per day. This is what Cal Newport calls, “The Principle of Least Resistance.”</p><p>If you send emails at all hours, schedule and attend meetings constantly, weigh in on instant message systems right away, these behaviors make you seem busy in a public manner. And if busyness indicates productivity, then you appear to be doing a good job.</p><blockquote>Without clear feedback about productivity, we tend toward doing lots of stuff in a visible manner.</blockquote><p>Why does a culture of connectivity persist? It’s easier. If you can get an answer to a question immediately, this makes your life easier — at least in the moment. If you couldn’t count on this quick response time you’d instead have to do more advance planning for your work, be more organized, and be prepared to put things aside for a while and turn your attention elsewhere while waiting for what you requested. This makes day-to-day work harder (even if it produced more satisfaction and better outcome in the long term).</p><blockquote>If email were to move to the periphery of your workday, you’d be required to deploy a more thoughtful approach on what to work on and for how long. But it’s simply easier to chime in on the latest cc’d email thread.</blockquote><h3>Better Measures and Habits for Productivity</h3><p>So what should we do when we don’t have clear feedback or metrics to quantify our productivity? How do we avoid short email response expectations? Here are some ideas.</p><p><strong>Measures</strong>. Add up deep work hours that contribute to completion of complicated tasks. Mark on a paper the number of hours you have worked on a project. I want to improve my Spanish, so I mark the number of times per month that I completed some lessons in <a href="https://mangolanguages.com/">Mango Languages</a> to see how close I was to my goal of 4 sessions per month. I want to improve my coding skills, so I mark on a paper calendar if I spent time on it that day to see how close I was to learning coding every day of the month. Then I keep those papers to see how well I did to feel good about meeting my goals or help me refocus to achieve my goals.</p><p><strong>Communication Habits.</strong> Here are some expectations you can give to your team on how quickly you will respond. If necessary to get started, setup an automatic email reply that people should expect an email response to take 24 hours. Here are better expectations of how quickly you should respond to various communication methods.</p><ul><li><strong>Email response</strong>: 24 hours</li><li><strong>Chat/text response</strong>: 4 hours</li><li><strong>Call</strong>: 2 hr, and reply with text when you will call back</li></ul><h3>Benefits of an Unconnected Day</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7GRHPcgxf7kH3s9D1EFKew.jpeg" /></figure><p>We feel like we cannot afford to block off time to concentrate on a complicated task. But we take sick days and we sleep, so we do block off time for some things. We all prioritize our time. In technology work, tasks will fill up every minute we allow for them. But not all tasks are created equal, some provide higher value than others.</p><blockquote>Some office workers spend 20 hours a week outside business hours monitoring email — believing it important to answer any email within an hour of its arrival.</blockquote><p>Is this behavior necessary in for a fast-paced business? Does it really help your work to be constantly connected. Study had one group take one way of the workweek completely off — no connectivity to anyone inside or outside the company. No loss of clients and employees did not lose their jobs. Instead, the employees found more enjoyment in their work, better communication among themselves, more learning, and better product delivered.</p><h3>Better for You, Better for your Company</h3><p>You may be burned out and tired from all the hours you put in at work. You just want some time to learn new things so you can progress in your career. But you feel that your results will suffer if you take time for professional development or to work on that killer idea that might get you promoted. But you can have a better balance and better results. Stop being drawn into the path of least resistance, block out time for that complicated work, and watch your prospects rise.</p><p>Follow me on <a href="https://twitter.com/thatericjohnson">Twitter</a> or <a href="https://www.linkedin.com/in/thatericjohnson/">LinkedIn</a> to engage with me on these and other topics related to DevOps, Python Coding, Work Productivity, Wireless Communications, Private RAN Networks, and Space Systems.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc6d4ebf8623" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Take the Red Pill and Push Errors to the Left]]></title>
            <link>https://medium.com/@thatericjohnson/take-the-red-pill-and-push-errors-to-the-left-eae00737b628?source=rss-29d4465c2beb------2</link>
            <guid isPermaLink="false">https://medium.com/p/eae00737b628</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[lean]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Eric Johnson]]></dc:creator>
            <pubDate>Tue, 02 Aug 2022 17:07:24 GMT</pubDate>
            <atom:updated>2022-08-03T00:24:56.468Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Fgmy2Oy2aiGbTRjt" /><figcaption>Photo by <a href="https://unsplash.com/@lanirudhreddy?utm_source=medium&amp;utm_medium=referral">ANIRUDH</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>How many times has the software development team said an enhancement was done but there were still many errors found in the Quality Assurance (QA) testing? How many times did the new code break existing functionality? This can be a frustrating cycle that will burnout engineers and cause them to leave. There is a solution that will create a better working environment to preserve your best engineers and also enhance performance in the long run, but it takes leadership commitment to temporarily slow down software delivery (or hire additional help) to build it. If your deadlines are so urgent that you feel that you need to keep throwing bodies at the problem, then take the blue pill and stop reading. If you want to open your eyes to a whole new world of possibility, <a href="https://en.wikipedia.org/wiki/Red_pill_and_blue_pill">take the red pill</a> and see where it takes you.</p><blockquote>“This is your last chance. After this, there is no turning back. You take the <em>blue</em> pill — the story ends, you wake up in your bed and believe whatever you want to believe. You take the <em>red</em> pill — you stay in Wonderland, and I show you how deep the rabbit hole goes. Remember: all I’m offering is the truth. Nothing more.” Morpheus</blockquote><p><em>Note: Much of the following is adapted from the following training on Pluralsight.</em></p><p><a href="https://www.pluralsight.com/courses/devops-foundations-core-concepts-fundamentals">DevOps Foundations: Core Concepts and Fundamentals</a></p><h3>Push Errors to the Left with a Poka-Yoke</h3><p>Poka what? What kind of rabbit hole is this? Do not fear, my friend … remember you took the red pill. A <a href="https://www.isixsigma.com/dictionary/poka-yoke/">Poka-Yoke</a> is a Japanese term used in Lean Management that refers to anything that helps with Error Avoidance. Have you ever had a problem with a tool, and someone told you, “Ya, everyone makes that mistake. You just need to do it this way.” All of those people took the blue pill, a world where you need to ask about “the right way” to use a tool, and that is just the way it is. We call it “user error”. Now you may think, “What’s the big deal? I learned how to do it, and now it works every time.” Ah, but what if you and the many other users never had to waste time learning the right way? Some examples of tools that prevent errors are a multiple choice drop down menu or a GFCI electrical outlet breaks the circuit if there is an overload.</p><p><a href="https://smile.amazon.com/Design-Everyday-Things-Revised-Expanded-ebook/dp/B00E257T6C">The Design of Everyday Things</a>, by Donald A. Norman, has many examples of tool designs that intuitively lead you to operate them correctly, and tool designs that lead you to make the wrong choice. The book cover has a fun bad design example.</p><p><a href="https://www.amazon.com/Design-Everyday-Things-Revised-Expanded-ebook/dp/B00E257T6C">The Design of Everyday Things: Revised and Expanded Edition</a></p><p>For example, the design of a door should indicate how it works without any need for a sign that says “Push” or “Pull”. You may laugh at the following Far Side cartoon, but how many times have you pulled on a door handle only to realize you were supposed to push it? The architect should have put a door plate on the “push” side, and then you would have made the correct decision the first time. It many such cases the design is at fault, not the users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/546/1*Ttyws9Eyz-5ksPAwtuLa6g.png" /><figcaption>The Far Side, by Gary Larson</figcaption></figure><p>When we stay in the Matrix we have someone submit a form and then tell them what errors they made on the form. When we live in the Real World we have an error check during data input. Some examples of error avoidance in software development:</p><ul><li><strong>Least Privilege</strong>: User should have exactly the permissions needed. Prevent malicious behavior or error. What you cannot do, you can’t do it mistakenly or maliciously.</li><li><strong>Version Control</strong>: Prevent committing code without an approved pull request.</li><li><strong>Quality and Testing</strong>: Write tests that must pass before new code can be committed. This prevents defects now and forever.</li></ul><h3>Avoid Errors by Eliminating Waste</h3><p>Remove non-value added steps to avoid errors and perform better. Attack waste in the software development life cycle (SDLC):</p><ul><li><strong>Partially Done Work</strong>. “It’s 90% done” actually means half of the work remains. Engineers are only accounting for the logic to create the code, but it is only complete after testing. This is caused by siloed goals: Every department has a unique measure of success. The software engineering (SWE) team goal is to “finish” code by the deadline, and the validation team goal is to quickly implement tests and push issues back to the SWE team. Instead, there should be a team goal to deploy code more quickly with good performance and less change failure rate.</li></ul><blockquote>“If you aim at speed, you may get speed, but you’ll get waste. If you aim at the elimination of waste, you’ll eliminate waste and get speed.” Chris Behrens</blockquote><ul><li><strong>Extra Features</strong>. A feature produced at the wrong time. A feature just in case, but may never be used. A part on a shelf taking time and money. The SWE created it because it would take more effort later. Instead make it possible later: make it a deferred commitment, make the product more agile.</li></ul><blockquote>The number one mistake of a star engineer is optimizing a thing that shouldn’t exist.” Elon Musk</blockquote><ul><li><strong>Relearning</strong>. Acquisition of previous knowledge. You learned it before but need a refresher. You created it before, but you need to remember how the code works. Create and store knowledge that is easy to understand and access. Make the code easier to comprehend even without comments, but still add comments as appropriate.</li><li><strong>Handoffs. </strong>Knowledge transfer to a new engineer. Some engineer turnover is inevitable, so cutting corners on documentation will create waste later. Be deliberate about cross-training, rotate responsibilities among the team.</li><li><strong>Task Switching</strong>. People are not good multitaskers. If two tasks take one hour, and only switch once in the middle of the first task, then the first task will take 40% longer. That is 40% waste. Here are some great books on Work Productivity. Look for future articles from me on this topic.</li></ul><ul><li><a href="https://www.amazon.com/Deep-Work-Focused-Success-Distracted/dp/1455586692">Deep Work: Rules for Focused Success in a Distracted World</a></li><li><a href="https://www.amazon.com/Great-Work-Hidden-Habits-Performers/dp/1476765820">Great at Work: The Hidden Habits of Top Performers</a></li></ul><ul><li><strong>Delays</strong>. This is a waste that cascades from the wastes above. The project is delayed by authority concentrated on the wrong level, siloed communication, and commitment that is not deferred (i.e “Extra Features”).</li><li><strong>Defects</strong>. This is another waste that cascades from other wastes above. Task switch from new work, re-learn old work to fix defects, and then switch back to new task. You are assuming the developer is available anytime to fix defects. Defects are a sign you are not managing the other wastes.</li></ul><h3>Reduce Time and Steps with Automated Testing</h3><p>Sometimes we think it will waste time to thoroughly test our code.</p><blockquote>“Perfect is the enemy of good enough.” Engineering Adage</blockquote><p>And yet we know there is a risk that insufficient software testing may result in a bug that will cause rework. But we got away with it before, and we hope we can get away with it again. Then we can deliver more instead of confirm what we already “know”: the code works properly. But here is where we begin to digest the red pill: we can have sufficient testing without any additional work. How is this possible? Follow me further down the rabbit hole.</p><p>Build a system where the code review catches the bugs. Write the test first and then write the code: it will inform how to write the code. No code will be error free. There is a debate about writing code first or tests first. It could waste time to write tests: during coding you may change your approach and the tests are no longer applicable so you need to re-write them. But you could also waste time coding: if you write the tests later, you may realize there are corner cases that you did not consider that require significant changes to the code. Your choice depends on the situation. You may have a failure of imagination: you may not think of a scenario so you cannot build the associated test case. You cannot anticipate all bugs, but you can learn from the past.</p><p>You may eliminate steps in the process because of automation. For example, you may remove some approval stages if there is sufficient confidence in the automated testing or if it is always approved anyway.</p><blockquote>“The best part is no part. The best process is no process. It weighs nothing. Costs nothing. Can’t go wrong.” Elon Musk</blockquote><p>Some leaders may complain that the software release cycles already take too long and adding automatic regression testing would add development time. Yes, it would take more time at first, but automating regression testing would speed up testing later. The SWE manager may be focussed on optimizing software development time. But the mistake is that optimizing the parts will optimize the whole. Google’s best practice is for <a href="https://sre.google/sre-book/introduction/">Site Reliability Engineers (SREs) to spend 50% of the time automating the development</a>.</p><h3>Take the Red Pill and Live in the Real World</h3><p>Sometimes we fail to weigh the impact on the customer or tester when they catch a bug. It damages the relationship, reduces trust, shifts the burden of work to others, passes the buck. Nobody likes to be dumped on. Quality issues are deprioritized to ship on time. We incorrectly think the best approach is deliver quickly and “hope for the best”. But when we push bugs to the left the overall cost of the bugs are less, the performance is better, and your best engineers will stay. Take the red pill.</p><p>What are examples where you found your group making good steps toward pushing errors to the left? What waste do you see in your SDLC? What resistance did you have to automate?</p><p>Follow me on Twitter at @therealericjohnson and on LinkedIn at <a href="https://www.linkedin.com/in/thatericjohnson/">https://www.linkedin.com/in/thatericjohnson/</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eae00737b628" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How do you know if a company is making progress on their DevOps journey?]]></title>
            <link>https://medium.com/@thatericjohnson/how-do-you-know-if-a-company-is-making-progress-on-their-devops-journey-3e0817b3873a?source=rss-29d4465c2beb------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e0817b3873a</guid>
            <category><![CDATA[state-of-devops]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[devops-practice]]></category>
            <category><![CDATA[site-reliability-engineer]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Eric Johnson]]></dc:creator>
            <pubDate>Tue, 19 Jul 2022 01:08:44 GMT</pubDate>
            <atom:updated>2022-07-19T01:08:44.125Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A road leading back through a green valley into the bright sun." src="https://cdn-images-1.medium.com/max/1024/0*YDuOIHhM_LnkC0yz" /><figcaption>Photo by <a href="https://unsplash.com/@thematthoward?utm_source=medium&amp;utm_medium=referral">Matt Howard</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Google’s “<a href="https://cloud.google.com/blog/products/devops-sre/announcing-dora-2021-accelerate-state-of-devops-report"><em>Accelerate the State of DevOps 2021</em></a>” report shows that 26% of survey respondents are in the “Elite” category of DevOps adoption and Puppet’s “<a href="https://puppet.com/resources/report/2021-state-of-devops-report#top"><em>State of DevOps Report 2021</em></a>” shows that 18% of respondents are “highly evolved” in DevOps. Both reports show more and more companies reaching this status every year. Engineers have higher job satisfaction with more automation and companies have better performance. You may be lucky enough to be in one of those elite companies, but others may be looking to work for one of them. What can ask during your interviews to know if a company is making progress on their DevOps journey?</p><h3>How do you define an “Elite” DevOps company?</h3><p>Many companies say they value automation, but they show it by tracking and improving DevOps metrics. Adoption of DevOps is incremental and happens at stages. We can’t expect everything to be automated immediately. However they should be able to show progress on the following key DevOps metrics. See a summary below and more details in the table below. (See a similar table on p. 10 of the Puppet’s <em>State of DevOps Report 2021</em>.)</p><ul><li><strong>Deployment frequency</strong>. Elite companies: multiple per day. Seriously. Elite performers deploy code 973 times more frequently than low performers. Wow, and I thought monthly releases were so much faster than bi-annual releases.</li><li><strong>Lead time</strong> <strong>from change to production</strong>. Elite companies: less than an hour. Elite performers heave lead times 6,570 times faster than low performers.</li><li><strong>Time to restore service</strong>. Elite companies: less than an hour.</li><li><strong>Change failure rate</strong>. Elite companies: less than 15%.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g02Cm8AUIkrnZdsmMsEnRA.jpeg" /><figcaption><a href="https://cloud.google.com/blog/products/devops-sre/announcing-dora-2021-accelerate-state-of-devops-report">Accelerate State of DevOps 2021</a>, pg. 9</figcaption></figure><p>More and more companies are achieving Elite status every year. See the chart below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7kFmNqkHYs3aEiYCCiynog.jpeg" /><figcaption><a href="https://cloud.google.com/blog/products/devops-sre/announcing-dora-2021-accelerate-state-of-devops-report">Accelerate State of DevOps 2021</a>, pg. 11</figcaption></figure><p>Similar trends according to the Puppet report. But it says that far too many companies are stuck in the middle of their DevOps journey.</p><blockquote>67% of mid-evolution companies say their team has automated most repetitive tasks, but 58% say there are multiple handoffs among teams to deploy products and services.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/942/1*gVb1hKQO4cVjn4wLtSwmEg.jpeg" /></figure><h3>Does it matter if a company uses DevOps?</h3><p>Here is what DevOps can deliver (from <em>Accelerate the State of DevOps 2021</em>):</p><ul><li><strong>Beat competitors with faster value to customers</strong> with 973x more frequent code deployments (p. 13).</li><li><strong>Less pain to customers</strong> making them more likely to stay with 3x lower change failure rate (p. 13). They are 3.7 times more likely to meet their reliability targets because of continuous integration (CI) that incorporates automated testing (p. 26- 27).</li><li><strong>Impact the bottom line</strong> by being 1.6x more likely to meet or exceed organizational goals when integrating security best practices (p. 24).</li></ul><p>Engineers have higher job satisfaction with more automation.</p><blockquote>89% are more satisfied with their job and 84% are more satisfied with their company as a result of using automation in the workplace.</blockquote><p><a href="https://www.zdnet.com/article/automation-leads-to-lower-employee-stress/">Employee satisfaction increases as a result of automation in the workplace</a></p><p>It takes a commitment to focus resources on automation for improved performance later. The Puppet State of DevOps Report 2021 found that companies with high DevOps adoption have a lot of support from their leadership.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q4Iu41tFbQPrNTUc5XqjQA.jpeg" /><figcaption><a href="https://puppet.com/resources/report/2021-state-of-devops-report#top">Puppet State of DevOps Report</a>, p. 11</figcaption></figure><h3>How do you find a company destined for “elite” status?</h3><p>Ok, so now you may be getting excited: there are really companies like this out there because DevOps makes good business sense. But how can you find a company like this to work for? <strong>Ask questions during the interview. </strong>What is their software development process? What Continuous Integration (CI) best practices are implemented? Do they use the pull request in Git to automatically run a static analysis tool? Do they use a code coverage tool to determine how many lines of code are tested in their automated tests? Do software engineers (SWE) write the unit test first and then write the code? Do SWE add unit tests and component tests to the automated process before they ask SDET (Software Development Engineering in Test) teams to implement End-to-End (E2E) tests or manual tests?</p><p>Find out more about the culture. Is there a shared commitment to excellence, not passing the buck, so DevOps engineers don’t have to hound SWE to fix a problem? Do engineers trust in the tests enough so they can trust the automated deployments? Is there sufficient test coverage so engineers can trust the code? (from <a href="https://www.pluralsight.com/courses/devops-big-picture-2021"><em>DevOps: The Big Picture</em></a><em>, by Richard Seroter on Pluralsight.</em>)</p><p>Determine if the automations create a process or pattern that will not be dropped under pressure. Many manual checks or steps are dropped when schedule pressure hits. But with a robust and well-built automation, the team will still use version control, and the build will still use unit tests to prevent pushing defects to production. Ask if the team is oriented toward overall outcome (less bugs found in testing, more test coverage by SWE), not individual team outcome that are often at odds (Ex: SWE done with code faster, SDET small issue queue). (<a href="https://www.pluralsight.com/courses/devops-foundations-core-concepts-fundamentals"><em>DevOps Foundations: Core Concepts and Fundamentals</em></a><em>, by Chris Behrens on Pluralsight</em>).</p><h3>What did you find?</h3><p>Now you know there are companies out there who can push new code within an hour instead of accumulate enhancements for 6 months before they release them. And now you know how to find them. What kind of answers do you hear from employers? Do they even track any of the key DevOps KPIs or can they quantify recent improvements? Do they struggle to make progress on the journey or do DevOps Engineers spend more than 50% of their time creating/improving automations? I’d love to hear the stories of what you find out there, so please reply in the responses below.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e0817b3873a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>