<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Development on a shoestring - Latest Comments in Agile and SQL links</title><link>http://slaven.disqus.com/</link><description></description><language>en</language><lastBuildDate>Sun, 04 Feb 2007 18:23:57 -0000</lastBuildDate><item><title>Re: Agile and SQL links</title><link>http://blog.slaven.net.au/archives/2007/02/04/agile-and-sql-links/#comment-1279551</link><description>60+ servers? Wow, I would hate to be your DBA!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Glenn Slaven</dc:creator><pubDate>Sun, 04 Feb 2007 18:23:57 -0000</pubDate></item><item><title>Re: Agile and SQL links</title><link>http://blog.slaven.net.au/archives/2007/02/04/agile-and-sql-links/#comment-1279550</link><description>It is much easier to rename a column when all you got is one production site, a testing site and a few development sites. In our case, changing a column would require&lt;br&gt;&lt;br&gt;- Change a column in the table definition file&lt;br&gt;- Write an upgrade script and test it against trunk + 2 branches&lt;br&gt;- Rebuild the 2 release branches&lt;br&gt;- Test the new builds &lt;br&gt;- Get permission from clients who need the change about upgrading&lt;br&gt;- Push out the change across 60+ servers in the evenings&lt;br&gt;- Send the patches + upgrade instructions to clients who are not hosted with us&lt;br&gt;- Wait for the support calls in the morning when clients found some incompatibility :)&lt;br&gt;&lt;br&gt;Around a week of work, and we are already trying to be as agile as possible :(&lt;br&gt;&lt;br&gt;Moreover, I found when the development only involves micro-iterations, people are less likely to work on re-factoring and re-architecturing the code, which are usually necessary when you are looking at 5+ years into the project...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott</dc:creator><pubDate>Sun, 04 Feb 2007 17:56:47 -0000</pubDate></item></channel></rss>