<?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>Continuous Delivery on Body of Knowledge | João Malcata</title>
    <link>https://bok.malcata.eu/tags/continuous-delivery/</link>
    <description>Recent content in Continuous Delivery on Body of Knowledge | João Malcata</description>
    <image>
      <title>Body of Knowledge | João Malcata</title>
      <url>https://bok.malcata.eu/icon.png</url>
      <link>https://bok.malcata.eu/icon.png</link>
    </image>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Wed, 18 Jun 2025 23:00:00 +0000</lastBuildDate><atom:link href="https://bok.malcata.eu/tags/continuous-delivery/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>TBD&#43;&#43; a Code Branching Strategy for the Modern Enterprise</title>
      <link>https://bok.malcata.eu/article/tbd&#43;&#43;-branching-strategy/</link>
      <pubDate>Wed, 18 Jun 2025 23:00:00 +0000</pubDate>
      
      <guid>https://bok.malcata.eu/article/tbd&#43;&#43;-branching-strategy/</guid>
      <description>Every engineering organization faces the same fundamental question: how do we balance speed with safety in our development workflow? GitFlow promised us structure and predictability. Trunk-Based Development promised us velocity and simplicity. Yet most engineering teams I met find themselves caught in an uncomfortable middle ground...</description>
    </item>
    
    <item>
      <title>I published</title>
      <link>https://bok.malcata.eu/blog/i-published/</link>
      <pubDate>Sun, 17 May 2020 01:06:51 +0000</pubDate>
      
      <guid>https://bok.malcata.eu/blog/i-published/</guid>
      <description>&lt;p&gt;I published &lt;a href=&#34;https://medium.com/@malcata/from-zero-to-continuous-delivery-in-6-months-the-startup-way-a34794bb2b6d&#34;&gt;medium.com/@malcata/from-…&lt;/a&gt; #Entrepreneurship #startups #LessonsLearned #ContinuousDelivery&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;&lt;a href=&#34;https://twitter.com/malcata/status/1261825476726833158&#34;&gt;Original Tweet&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>from zero to Continuous Delivery in 6 months, the startup way</title>
      <link>https://bok.malcata.eu/article/cd-startup-way/</link>
      <pubDate>Tue, 17 Mar 2020 23:00:00 +0000</pubDate>
      
      <guid>https://bok.malcata.eu/article/cd-startup-way/</guid>
      <description>The journey of a startup studio developing its first product while bringing to life an MVP delivery system expected to be lean and fast. A set of lessons learned and anti-patterns collected from the trenches of building a product from scratch. Finally, the realization that in scenarios of extreme uncertainty, money and time shortage, no legacy, and few early adopters, can lead to counter-intuitive actions that will help you fly. This will either broaden your perspectives or drive you insane.</description>
    </item>
    
    <item>
      <title>A brief history of the software development process according to my experience</title>
      <link>https://bok.malcata.eu/article/my-brief-sdlc-history/</link>
      <pubDate>Tue, 21 Feb 2017 23:00:00 +0000</pubDate>
      
      <guid>https://bok.malcata.eu/article/my-brief-sdlc-history/</guid>
      <description>Over almost 20 years, I have been involved in a multitude of software development endeavors. Out of sheer luck or just time passing, together they seem to show an “evolution“ worth sharing. Even if not systematic and according to a scientific process, experience does provide insight and I hope lessons to be learned.</description>
    </item>
    
  </channel>
</rss>
