<?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>Software Best-Practice on Chris McKelt - Remembering Thoughts</title><link>https://blog.smarttechventures.au/tags/software-best-practice/</link><description>Recent content in Software Best-Practice on Chris McKelt - Remembering Thoughts</description><generator>Hugo -- 0.147.2</generator><language>en</language><lastBuildDate>Mon, 21 Jul 2014 00:00:00 +0800</lastBuildDate><atom:link href="https://blog.smarttechventures.au/tags/software-best-practice/index.xml" rel="self" type="application/rss+xml"/><item><title>Software Development Best Practice (minimum)</title><link>https://blog.smarttechventures.au/articles/posts/software-development-best-practice-minimum/</link><pubDate>Mon, 21 Jul 2014 00:00:00 +0800</pubDate><guid>https://blog.smarttechventures.au/articles/posts/software-development-best-practice-minimum/</guid><description>&lt;h1 id="source-control">Source Control&lt;/h1>
&lt;p>To track versions and manage an environment from deployment to recovery, source control is essential.  Tracking changes, performing peer reviews before merging to the main master branch &amp;amp; the ability to rebuild/recover/revert to a previously known good state ensure quality throughout the process.&lt;/p>
&lt;p>Example source control : &lt;a href="https://github.com/" target="_blank">GitHub&lt;/a>&lt;/p>
&lt;h1 id="continue-integration">Continue Integration&lt;/h1>
&lt;p>Continuous Integration (CI) is a development practice that requires developers to integrate code into a shared repository several times a day. Each check-in is then verified by an automated build, allowing teams to detect problems early.&lt;/p></description></item></channel></rss>