<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Best-Practices on Shafiq Alibhai</title>
    <link>https://www.shafiq.in/zh/tags/best-practices/</link>
    <description>Recent content in Best-Practices on Shafiq Alibhai</description>
    <generator>Hugo</generator>
    <language>zh-CN</language>
    <copyright>© 2009-2026 All rights reserved.</copyright>
    <lastBuildDate>Wed, 26 Sep 2018 11:55:38 +0000</lastBuildDate>
    <atom:link href="https://www.shafiq.in/zh/tags/best-practices/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Cart Before the Horse - A DevOps Conundrum</title>
      <link>https://www.shafiq.in/zh/blog/the-cart-before-the-horse-a-devops-conundrum/</link>
      <pubDate>Wed, 26 Sep 2018 11:55:38 +0000</pubDate>
      <guid>https://www.shafiq.in/zh/blog/the-cart-before-the-horse-a-devops-conundrum/</guid>
      <description>&lt;p&gt;We&amp;rsquo;ve all heard the age-old saying: putting the cart before the horse. Unfortunately, in the world of DevOps, this is happening far more often than it should, and it&amp;rsquo;s time we talk about it.&lt;/p&gt;&#xA;&lt;p&gt;The crux of the issue is that, too often, the focus isn&amp;rsquo;t on solving actual problems; it&amp;rsquo;s on utilizing shiny new technologies. Picture this: A developer stumbles upon a cutting-edge piece of technology. They&amp;rsquo;re immediately enamored by its features, its capabilities, the way it&amp;rsquo;s touted as the &amp;rsquo;next big thing.&amp;rsquo; So, they start finding ways to incorporate it into their work, regardless of whether it&amp;rsquo;s actually the best fit for the problems at hand.&lt;/p&gt;</description>
    </item>
    <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>
    <item>
      <title>Best Practices for Crafting an Efficient Build Script</title>
      <link>https://www.shafiq.in/zh/blog/best-practices-for-crafting-an-efficient-build-script/</link>
      <pubDate>Mon, 09 May 2011 18:31:40 +0000</pubDate>
      <guid>https://www.shafiq.in/zh/blog/best-practices-for-crafting-an-efficient-build-script/</guid>
      <description>&lt;h2 id=&#34;disablehljs-false&#34;&gt;disableHLJS: false&lt;a class=&#34;anchor&#34; href=&#34;#disablehljs-false&#34;&gt;#&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;When it comes to software development, a robust and efficient build script can be a game-changer. Whether you&amp;rsquo;re working on a Java project or any other type of application, the right build script can streamline the whole process and make life a whole lot easier for developers. Here&amp;rsquo;s a rundown of some best practices to keep in mind when you&amp;rsquo;re writing your build script:&lt;/p&gt;&#xA;&lt;h3 id=&#34;platform-independence&#34;&gt;Platform Independence&lt;a class=&#34;anchor&#34; href=&#34;#platform-independence&#34;&gt;#&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;p&gt;Choose a programming language that is compatible across multiple platforms, especially if you&amp;rsquo;re working on a Java project. This flexibility will save you from a lot of headaches down the line when dealing with different operating systems.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
