<?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 Amichai Hemli on Medium]]></title>
        <description><![CDATA[Stories by Amichai Hemli on Medium]]></description>
        <link>https://medium.com/@amichai.hemli?source=rss-f4663d8bb069------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*d1TGPRU2FJo_zFq2.jpg</url>
            <title>Stories by Amichai Hemli on Medium</title>
            <link>https://medium.com/@amichai.hemli?source=rss-f4663d8bb069------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 09:15:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@amichai.hemli/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[How CI/CD took my Developer-Customer’s Relationship to the Next Level?]]></title>
            <link>https://medium.com/att-israel/how-ci-cd-took-my-developer-customers-relationship-to-the-next-level-666b5983abd0?source=rss-f4663d8bb069------2</link>
            <guid isPermaLink="false">https://medium.com/p/666b5983abd0</guid>
            <category><![CDATA[feature-toggles]]></category>
            <category><![CDATA[release-management]]></category>
            <category><![CDATA[trust]]></category>
            <category><![CDATA[cicd]]></category>
            <category><![CDATA[code]]></category>
            <dc:creator><![CDATA[Amichai Hemli]]></dc:creator>
            <pubDate>Thu, 05 Nov 2020 11:06:32 GMT</pubDate>
            <atom:updated>2020-11-05T11:06:32.114Z</atom:updated>
            <content:encoded><![CDATA[<h4>Delivering code is almost like bringing your own bag to the airport: You should have packed it by yourself and you should be able to vouch for its contents. But in code craftsmanship we don’t use X-Ray scanners, we use CI/CD. Based on a true story.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YONI6h9sky60zI2S" /><figcaption>Photo by <a href="https://unsplash.com/@rikku72?utm_source=medium&amp;utm_medium=referral">Maria Cappelli</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Did You Pack This Yourself?</h3><p>While crafting code and delivering it, a relationship is established. It’s a relationship between a customer and a developer that is founded on a single pillar: Trust.</p><p>When the customer asks you “<em>Did you pack this yourself?</em>” and your answer is “<em>Sure I did!</em>”, that’s when mutual trust is vital. If you look a bit deeper and read between the lines, you understand what the customer is really asking you:</p><p>Question #1: Can you list the contents of this package? Or do your Release Notes represent the accurate list of features and bug fixes?</p><p>Question #2: Can you ensure me it won’t blow up once I open (also deploy) it? or Have you verified the regressions and certified the new features?</p><p>The one process you should follow to establish this kind of trust is:</p><blockquote><strong>C</strong>ontinuous <strong>I</strong>ntegration <strong>C</strong>ontinuous <strong>D</strong>elivery</blockquote><p>If you have a well-formed CI/CD implementation in your tool-belt, where you <strong>frequently</strong> build/package/test your code, then you can answer the questions listed above with confidence: YES, you can trust me.</p><h3>A True Story.</h3><p>In May 2017 a new dev team was forged, and our mission was to take ownership of a live legacy system. As a team leader, it was clear to me that I would have to do things differently than my predecessor.<br>While handling the on-going support and bug-fixes (there were plenty) we started to make a small revolution in the code we inherited.<br>For every new feature, we took the “test-first” approach. We embedded the automated test into the CI/CD’s pipeline and invested a lot in redesigning our CI/CD process.</p><p>Making a long story short, starting with a big zero coverage percentage and an unstable or unusable CI/CD process, we got into a position where each commit got a full cycle of verification immediately, from 0% to more than 90% scenario coverage including Unit tests, API/UI tests, E2E tests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/987/1*aK6X875OCrueidvj5FKPKw.png" /><figcaption>Test first. The only way to know when done is really done</figcaption></figure><p>For each CI/CD cycle, we built our confidence based on more than 4000 automatic test cases:</p><ul><li>Covering the code changes</li><li>Verifying that we didn’t break any regression flow</li><li>Certifying the new features</li><li>Monitoring our static-code-analysis status</li></ul><p>Our customer was finally happy and satisfied with the product.</p><p>In this blog, I will try to share my perspective on what it takes to get there, and why you should get there as well.</p><h3>No More Out-of-stock</h3><p>A fast yet reliable CI/CD process will let you <em>always deliver</em>. As nobody wants to wait, you don’t want your customer to wait. Ever.</p><p><strong>Continuous Integration</strong> is the art of packaging.<br>This process will let you verify that you are packaging the correct items(also features). A phase in which you verify the quality of your artifacts, you document the package’s contents and prepare it for shipment.<br>Don’t be afraid of investing your dev resources in the <em>DevOps</em> tasks, writing your own pipelines, using your preferred tools, and don’t forget to create the capability of monitoring the success or failures.</p><p><strong>Continuous Delivery</strong> is the best practice to maintain your skill and ability to deliver your product. This part of the CI/CD should verify that each future deployment of your product will be smooth/seamless/transparent (zero downtime if possible).<br>For each cycle of the CI/CD, you want to know that your package will reach its destination safely and soundly. <br>If there are obstacles/limitations on the way to your customers such as production or environment challenges, then you should tackle them in advance so that you can code your way out of troubled waters.<br>Now that you know you are on the high road, you just need to wrap your package and ship away.</p><p>This will enable you to always deliver, and your customer will thank you for being so responsive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MSeFgFkgdrEymgaT3pIb-A.png" /><figcaption>Monitor your CI/CD.</figcaption></figure><p>Oh, one more thing. When continuously integrating and packaging, you will also get a higher level of confidence in your recent code changes — especially for the integration (usually pain-) points you have with other components and developers.</p><h3>Box on Your Doorstep</h3><blockquote>On delivery day, you will receive a notification in the morning with a 4-hour delivery window for when the delivery driver will arrive at your home. Right before the driver arrives, you will receive an “Arriving Now” notification and can optionally watch the delivery happen live.[<a href="https://www.amazon.com/gp/help/customer/display.html?nodeId=202104360">amazon.com</a>]</blockquote><p>This is how the customer should experience each release of your product. Take the customer’s perspective: You open the door and there it is - a shiny and new release, just waiting for you to unbox it. Can you feel it?</p><p>Once the CI/CD pipelines are installed, it’s time to utilize them. Even if you don’t deliver every build, try to deliver frequently. This means do not let the customer <strong>wait</strong> but rather to <strong>anticipate</strong> your next release.<br>Implement new features: slice them, spice them a bit with a few, just a few bug-fixes or security updates. Make sure the package is not-too-heavy as we want to keep things light&amp;agile so it will ease the shipment (by reducing the complexity and risks upon deployments).</p><p>Getting the new release will be the best part of the day for your customer. <br>Just like getting a gift.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Jnl0i7C-EkEJUAyb" /><figcaption>Photo by <a href="https://unsplash.com/@kadh?utm_source=medium&amp;utm_medium=referral">Kira Auf der Heide</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Each package should come with its contents’ description, which is your Release Notes. This is where you should specify what’s new: new features, improvements, security patches, or simply bug fixes. Don’t leave anything out that may surprise your customer.</p><h3>Unboxing</h3><p>Each release of a product will get one chance to make a first impression. Those very first minutes, when a customer uses a new product, will reflect on the customer experience of the product and overall satisfaction.</p><p>For a modified/new user-experience, try to collect as much feedback as you can. You can conduct a demo, or just implement a first-time tutorial to emphasize what was changed. Adding a “Did-you-like-this?” button on the new form, for example, may let you know what your customer thinks of a feature, etc.</p><p>Use any sort of <a href="https://martinfowler.com/bliki/FeatureToggle.html">Feature Toggling</a> mechanism to make sure that your customer will get the flavor as expected. Also, don’t forget to document the toggles and introduce this capability to your customer. This will enable doing some fine-tuning while striving to nail the exact taste your customer was looking for.<br>Sometimes the new feature is not exactly as expected. In such cases, using feature-toggles will enable turning OFF a new feature, giving the customer an immediate resolution.</p><p>Keep in mind: It is critical to have direct communication with the customer as you need the feedback. You <strong>want the feedback</strong>. This is the only way to know if your customer is satisfied and if you are meeting the product expectations, e.g. if your customer can <strong>trust</strong> you.<br>Thus, even if the product is not yet “perfect”, but because the customer and developer are on the same page, there is an understanding: <strong>we</strong> will make this product better, together.</p><h3>Enjoy Your Flight</h3><p>Let’s recap. Trust is vital for your customer-developer relationship. Therefore, you will need to build a true CI/CD process that will work for you (both).<br>It is not about the tools you choose but rather the way you use them.</p><p>So next time, do make sure you pack your own bag.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=666b5983abd0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/att-israel/how-ci-cd-took-my-developer-customers-relationship-to-the-next-level-666b5983abd0">How CI/CD took my Developer-Customer’s Relationship to the Next Level?</a> was originally published in <a href="https://medium.com/att-israel">AT&amp;T Israel Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>