<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Continuous-Deployment on Shafiq Alibhai</title>
    <link>https://www.shafiq.in/zh/tags/continuous-deployment/</link>
    <description>Recent content in Continuous-Deployment on Shafiq Alibhai</description>
    <generator>Hugo</generator>
    <language>zh-CN</language>
    <copyright>© 2009-2026 All rights reserved.</copyright>
    <lastBuildDate>Mon, 02 Jan 2012 17:31:13 +0000</lastBuildDate>
    <atom:link href="https://www.shafiq.in/zh/tags/continuous-deployment/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Navigating the Obstacles of Continuous Delivery</title>
      <link>https://www.shafiq.in/zh/blog/navigating-the-obstacles-of-continuous-delivery/</link>
      <pubDate>Mon, 02 Jan 2012 17:31:13 +0000</pubDate>
      <guid>https://www.shafiq.in/zh/blog/navigating-the-obstacles-of-continuous-delivery/</guid>
      <description>&lt;p&gt;Mastering the art of Continuous Delivery is about more than just pushing code onto a server. It&amp;rsquo;s a delicate balance of managing your technology and the people who interact with it. One major stumbling block? The tiny differences between machines that happen when someone decides to make ad-hoc changes. These may seem trivial, but they can cause massive headaches when it comes to debugging and troubleshooting.&lt;/p&gt;&#xA;&lt;p&gt;The endgame here is clear: Create a system so streamlined that there&amp;rsquo;s no need for anyone to manually log in to make changes. Achieving this means fewer bugs, faster deployments, and ultimately, a happier team.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
