Warning: include_once(/home/resonantstudios/gratis/eclecti.ca/public/wordpress/wp-content/plugins/wordpress-support/wordpress-support.php): failed to open stream: Permission denied in /home/resonantstudios/gratis/eclecti.ca/public/wordpress/wp-settings.php on line 221
Warning: include_once(): Failed opening '/home/resonantstudios/gratis/eclecti.ca/public/wordpress/wp-content/plugins/wordpress-support/wordpress-support.php' for inclusion (include_path='.:/usr/local/lib/php:/usr/local/php5/lib/pear') in /home/resonantstudios/gratis/eclecti.ca/public/wordpress/wp-settings.php on line 221 M3talinks For 05/03/2011 | Eclecti.ca
Ah source control, if there’s a more essential tool which indiscriminately spans programming languages without favour, I’m yet to see it. It’s an essential component of how so many of us work; the lifeblood of many development teams, if you like. So why do we often get it so wrong? Why are some of the really core, fundamentals of version control systems often so poorly understood?
I boil it down to 10 practices – or “commandments” if you like – which often break down or are not properly understand to begin with. These are all relevant to version control products of all types and programming languages of all flavours. I’ll pick some examples from Subversion and .NET but they’re broadly applicable to other technologies.