<?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 Bitsy on Medium]]></title>
        <description><![CDATA[Stories by Bitsy on Medium]]></description>
        <link>https://medium.com/@dearbitsy?source=rss-501f71eb8eea------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*QQmCBdbEtsYGXuki8hFtew.png</url>
            <title>Stories by Bitsy on Medium</title>
            <link>https://medium.com/@dearbitsy?source=rss-501f71eb8eea------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 17:08:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dearbitsy/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[SAFe Cracked]]></title>
            <link>https://medium.com/dear-bitsy/safe-cracked-a6a4c6eaf296?source=rss-501f71eb8eea------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6a4c6eaf296</guid>
            <category><![CDATA[safeagile]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[scaled-agile]]></category>
            <category><![CDATA[continuous-delivery]]></category>
            <dc:creator><![CDATA[Bitsy]]></dc:creator>
            <pubDate>Sun, 21 Feb 2021 21:18:18 GMT</pubDate>
            <atom:updated>2023-03-29T15:38:26.686Z</atom:updated>
            <content:encoded><![CDATA[<p>Dear Bitsy,</p><p><em>My company adopted a SAFe Agile software development approach for a system that was originally written before some of my team members were in grade school. It’s a pretty fragile piece of software, and whenever we change anything it breaks something else in a completely unexpected way. We’ve been chatting about how easy it would be to re-create most of what the system does with modern open source software and public cloud services, but have no idea how to get this idea into the whole SAFe process.</em></p><p><em>Can you help?</em></p><p><em>SAFe Cracked</em></p><p>Dear SAFe Cracked,</p><p>Congratulations on seeing opportunities for improvement! Agile software delivery includes ceremonies like retrospectives and activities that encourage continuous improvement. SAFe is one of multiple ‘scaled agile’ frameworks marketed to larger organizations or corporations that often have older, unpredictable systems and organizational sprawl. SAFe does indeed keep some organizations safe from unpredictable software, and unpredictable stakeholders.</p><p>SAFe is a perfectly good approach for systems that have shared dependencies on traditional infrastructure such as physical servers and databases, and systems that have poor unit and contract test coverage. These characteristics make systems brittle and hard to change because the impacts of change are not predictable. Longer-term planning and careful analysis of every change can be important for these systems because every change event can bring service interruption due to the lack of assurance that automated test coverage provides. Why, dear old Bitsy remembers this type of careful planning from her mainframe programming years, when unexpected results from changes to systems were also very costly. SAFe, like <a href="https://en.wikipedia.org/wiki/Waterfall_model">Waterfall</a>, is a perfectly good approach to software delivery when dealing with older systems having poor test coverage and complex shared dependencies.</p><p>For organizations taking their first steps toward agile delivery, the longer planning cycles and formality of SAFe can also help nudge stakeholders away from ‘tapping your favorite engineer on the shoulder’ and introducing new or poorly-defined features having last-minute deadlines. Unfortunately, SAFe is still very much needed in many large organizations, not to measure engineering velocity but to keep them safe from unpredictable legacy systems and stakeholders. But, <a href="https://medium.com/serious-scrum/scrum-has-hit-the-glass-ceiling-3610bb978b1d">SAFe adoption sometimes hits a ceiling</a> and may not necessarily provide an approach you and your friends could take to quickly re-imagine and deliver a system, as though you were in a garage next door.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*F3Dl8iyk1vLwWL93.jpg" /><figcaption><a href="https://www.flickr.com/photos/15131913@N00/288491653">“Safe”</a> by <a href="https://www.flickr.com/photos/15131913@N00">rpongsaj</a> is licensed under <a href="https://creativecommons.org/licenses/by/2.0/?ref=ccsearch&amp;atype=rich">CC BY 2.0</a></figcaption></figure><p>When software can be deployed in smaller pieces, with decoupled dependencies and robust automated test coverage, it is much easier to make changes and promote changes to production in small batches. Automated tests will tell you when any given change creates a negative impact on the system. Modern software can be built for continuous integration and continuous delivery, which requires good test coverage and the kind of tooling most commonly associated with ‘cloud-native’ technology. The focus shifts from long-range planning to continuously grooming and prioritizing well-defined Features and Stories that deliver independent value and do not have complex dependencies on physical servers or shared infrastructure. With this type of software development, you can pursue lighter-weight processes such as Lean or LESS which normally require less organizational overhead and emphasize placing bets or creating hypotheses such as:</p><blockquote>We might be able to recreate most of this very quickly, like entrepreneurs trying to disrupt our own business.</blockquote><p>You’re exactly right! Today’s technology stands on the shoulders of giants, and the vast sea of open source software that is readily available to rapidly compose innovative solutions. In fact, <a href="https://www.linuxfoundation.org/blog/blog/a-summary-of-census-ii-open-source-software-application-libraries-the-world-depends-on">most modern applications consist of seventy to ninety percent open source software</a>. ‘Build vs Buy’ is dead, and ‘Compose (from OSS) vs Buy’ can be a great way to innovate, differentiate, and maximize value.</p><p>But, large organizations often have a lot of organizational overhead, and questioning the amount of middle management involved in software delivery can be a very un-SAFe thing to do. To test the water, try to find out about your organization’s plans for public cloud adoption, which often brings opportunities to re-think existing software delivery processes. If you find there are people looking into public cloud adoption and Continuous Integration/Continuous Delivery, hitch your wagon to those efforts. Your knowledge of the existing system will be valuable when it comes time to free it from processes that make it brittle and unpredictable. If the existing system can not be predictably changed, or can not scale resiliently to meet the needs of your business, a software engineering process like SAFe may be addressing the symptom but not the root cause of your pains.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/100/0*MF4Wdj1w1M9WP78Z.png" /></figure><p>Best,<br>Bitsy</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6a4c6eaf296" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dear-bitsy/safe-cracked-a6a4c6eaf296">SAFe Cracked</a> was originally published in <a href="https://medium.com/dear-bitsy">Dear Bitsy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Branched out]]></title>
            <link>https://medium.com/dear-bitsy/branched-out-85c98c31db20?source=rss-501f71eb8eea------2</link>
            <guid isPermaLink="false">https://medium.com/p/85c98c31db20</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[branching-strategy]]></category>
            <category><![CDATA[continuous-delivery]]></category>
            <dc:creator><![CDATA[Bitsy]]></dc:creator>
            <pubDate>Sat, 02 Jan 2021 16:39:14 GMT</pubDate>
            <atom:updated>2021-01-02T16:39:14.385Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Dear Bitsy,</em></p><p><em>I’m a software engineer at a large company that has been infiltrated by agile consultants. They’ve spent the past three weeks arguing about branching strategies and I’m wondering where this is going.</em></p><p><em>Can you help?</em></p><p><em>Branched out</em></p><p>Dear Branched out,</p><p>Goodness, consultants spending their time arguing sounds expensive. My favorite way to bring endless arguments to closure is to time box the debate and establish the following rule:</p><blockquote>If you have opinions, bring code.</blockquote><p>Debating branching strategies is an odd use of billable time; <a href="https://trunkbaseddevelopment.com/game-changers/">volumes have been written on the topic</a> since the first mainframes roamed the earth. Today, I’d expect most agile consultants to promote <a href="https://trunkbaseddevelopment.com/">Trunk Based Development</a> and work with you on a way to arrive there from where you are today. That may or may not involve a large number of billable consulting hours. Establishing the goal of Trunk Based Development can take as little as five minutes; it may take much longer depending on the amount of engineering overhead involved in the decision. Organizations with a great deal of engineering overhead create distance between developers; that distance introduces additional time to arrive at decisions and start writing code that delivers value.</p><p><a href="https://trunkbaseddevelopment.com/5-min-overview/">Trunk Based Development</a></p><p>Moving towards Trunk Based Development goes hand in hand with the pursuit of <a href="https://trunkbaseddevelopment.com/continuous-integration/">Continuous Integration</a>, which requires good test coverage and engineering team discipline.</p><p>If your organization is responsible for a large amount of <a href="https://jeremiahflaga.github.io/memorabilia/books/quotes-from-working-effectively-with-legacy-code/">‘older’ code</a>, that code may not have the test coverage needed to enable these practices. When test coverage does not provide reliable protection from changes, organizations sometimes embrace branching strategies and additional engineering overhead to control change. In the worst scenarios, branching strategies lead to more elaborate controls intended to protect an organization from the impact of code changes, leading to longer release cycles and larger change batch sizes, leading to increased risk of change failure. On the other hand, moving an existing codebase with low test coverage towards Trunk Based Development and Continuous Integration isn’t easy.</p><p>For new code, do your best to start on the right foot — beginning with good test coverage and a goal of Trunk Based Development; this involves writing code and learning what works best for you and your team. For existing code that lacks good test coverage, there is a wealth of advice <a href="https://understandlegacycode.com/blog/key-points-of-working-effectively-with-legacy-code/">from those who have wrestled with older code</a>. Note that nowhere in this advice do we see endless debates on branching strategy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FwsXYEoRLAtaU1ua.jpg" /><figcaption><a href="https://www.flickr.com/photos/76186924@N00/37495355">“Snow Branches”</a> by <a href="https://www.flickr.com/photos/76186924@N00">glennharper</a> is licensed under <a href="https://creativecommons.org/licenses/by/2.0/?ref=ccsearch&amp;atype=rich">CC BY 2.0</a></figcaption></figure><p>Personally, my first and favorite branching strategy came along with a bubbly woman named Beverly. When I punched the batch job to compile and link my code, I waited an hour or so, walked downstairs to the raised floor output window, and asked the operator for the listing. Clean compiles were the norm since waiting hours to have a compiler find errors in my code was a drag. I’d take my clean, green bar, fan-fold listing to Beverly. After desk-checking the results, Beverly filed my contribution and discarded the oldest listing, keeping the three most recent clean listings in the filing cabinet. If I needed to review older versions of the code I could call the operator to request microfiche. There were no branches.</p><p>Now that our build times and delivery cadence are a bit quicker, why would we want to introduce additional wait time and risk from merging branches? For older code, why not pursue a test coverage strategy that will move you closer to continuous integration? Consider taking one of your agile consultants for lunch sometime to have a friendly discussion; have them pick up the tab. If the discussions don’t lead to writing code, with tests, it may be time to shop around for different consultants.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/100/0*MF4Wdj1w1M9WP78Z.png" /></figure><p>Best,<br>Bitsy</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85c98c31db20" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dear-bitsy/branched-out-85c98c31db20">Branched out</a> was originally published in <a href="https://medium.com/dear-bitsy">Dear Bitsy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cloud Immigrant]]></title>
            <link>https://medium.com/dear-bitsy/cloud-immigrant-6c033db16f24?source=rss-501f71eb8eea------2</link>
            <guid isPermaLink="false">https://medium.com/p/6c033db16f24</guid>
            <category><![CDATA[cloud-native]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[modernization]]></category>
            <category><![CDATA[private-equity]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Bitsy]]></dc:creator>
            <pubDate>Wed, 30 Dec 2020 14:13:09 GMT</pubDate>
            <atom:updated>2021-01-20T11:46:13.332Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<p><em>Dear Bitsy,</em></p><p><em>I’m an IT manager at a company that has been acquired by a private equity outfit. Our executives say that we need a digital transformation to become ‘cloud-native’. We’re a pretty traditional organization and I’m getting a lot of questions from my team about what all this means.</em></p><p><em>Can you help?</em></p><p><em>Cloud Immigrant</em></p><p>Dear Cloud Immigrant,</p><p>Congratulations on your new owners! Private equity types are normally motivated to sell your company within a few years at a higher price than they’ve paid. To spark the interest of potential buyers, they spruce up the place.</p><p>Your upcoming digital transformation is a remodeling job. Try binge-watching “<a href="https://www.youtube.com/watch?v=roiEHDIyfbc">Flip This House</a>” with your team to get the conversation going. Is your team responsible for the charming kitchen nook that becomes a selling point, or the rotting floorboards that sag when more than four people are in the room? Do your systems keep you up at night or take up your weekends?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2vmclbJBiAGGQWoT.jpg" /><figcaption><a href="https://www.flickr.com/photos/48894138@N05/6135394223">“Old house, Selwyn, Canterbury, New Zealand”</a> by <a href="https://www.flickr.com/photos/48894138@N05">brian nz</a> via <a href="https://creativecommons.org/licenses/by-sa/2.0/?ref=ccsearch&amp;atype=rich">CC BY-SA 2.0</a></figcaption></figure><p>Clinging to that old hardware and CapEx budget won’t drive up your resale value. Arguing that your current systems are too complex and your processes too highly customized won’t matter once the transformation consultants arrive. There are three twenty-somethings in a garage down the street who are building a ‘disruptor’ for your industry. It will probably ship this afternoon, full of glitches that will provide enough data about your customers in a week to make a marketing team happy for a year.</p><p>Change can be hard, but you may need to remind your team that a career in technology comes with perpetual change. When you stop learning, your career in technology is over. Your team’s advantage is their knowledge of existing systems and processes; how many of those existing systems and processes give you joy? Digital transformation is a Marie Kando moment. For software, systems, and processes that no longer give you joy, this is your chance to appreciate what they’ve taught you and let them go.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MbhFlFcd_dA9Hpoc.jpg" /><figcaption><a href="https://www.flickr.com/photos/22178197@N00/8715851521">“Clouds”</a> by <a href="https://www.flickr.com/photos/22178197@N00">Kamil Porembiński</a> via <a href="https://creativecommons.org/licenses/by-sa/2.0/?ref=ccsearch&amp;atype=rich">CC BY-SA 2.0</a></figcaption></figure><p>Start a study group with your team and tackle free cloud certification training from <a href="https://docs.microsoft.com/en-us/learn/certifications/azure-fundamentals">Microsoft</a>, <a href="https://www.coursera.org/learn/gcp-fundamentals?">Google</a>, or <a href="https://www.aws.training/Details/eLearning?id=60697">AWS</a>. Have some fun; it might just remind you of why you originally got into technology. If you run into people who resist or harp on the reasons you will fail, just <a href="https://www.youtube.com/watch?v=RoUa4dIcO50">turn up some tunes</a> and keep learning. Learn, evolve, or be relegated to the dustbin of legacy.</p><p>When your company is eventually sold to a new owner, you’ll either like the new landlords and want to stick around, or you’ll be able to use your new and marketable skills to find another home at a better salary. Surely I’d still be keypunching GOTO statements on punchcards if it weren’t so.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/100/1*_UiChI2YcKZ32_Fy1P4-8g.png" /></figure><p>Best,<br>Bitsy</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6c033db16f24" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dear-bitsy/cloud-immigrant-6c033db16f24">Cloud Immigrant</a> was originally published in <a href="https://medium.com/dear-bitsy">Dear Bitsy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>