DISQUS

DISQUS Hello! Development on a shoestring is using DISQUS, a powerful comment system, to manage its comments. Learn more.

Community Page

  • Subscribe

  • Community

  • Top Commenters

  • Popular Threads

  • Recent Comments

    • This prestigious jewelry line is designed by the legendary Elsa Peretti, an Italian jewelry designer who first tied the Tiffany cadre in 1974. For more than 100 being, <a...

      4 days ago by classic tiffany

      in Happy Easter all

    • Dennis Wurster, I am having the same problem. I wonder if it worked well if you schedule REAL cronjob to run wp-pseudo-cron (/blog/wp-cron.php as I assume) each minute/hour? So that cron...

      6 days ago by Dennis

      in Timing is everything: scheduling in WordPress

    • What I can say is very nice and helpful as well as informative post...really help me very much more!! Thanks.. Cheers, <a href="http://sain-web.com" rel="nofollow">Buat...

      1 week ago by Traveller_Adventure

      in Showing trackbacks with Disqus

    • ่่่่่่่่่่่่่่่่่่่่่ghhhhhhhhhhhh

      1 week ago by aaaa

      in FriendFeed Comments WordPress Plugin

    • The brilliant and shining links of london with brightly colored <a href=http://www.londonoflinks.co.uk/>Links of London</a> eye-catching. Your face shape and hair style, can wear red...

      1 week ago by linksoflondon

      in Happy Easter all

Jump to original thread »
Author

Agile and SQL links

Started by Glenn Slaven · 11 months ago

Scott Bellware of CodeBetter.com has a great article on CoDe Magazine about agile development and how it improves the whole development lifecyle.  He has this to say about the old way of running a development project:
Somewhere in the lost pre-history of software development, ... Continue reading »

2 comments

  • 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

    - Change a column in the table definition file
    - Write an upgrade script and test it against trunk + 2 branches
    - Rebuild the 2 release branches
    - Test the new builds
    - Get permission from clients who need the change about upgrading
    - Push out the change across 60+ servers in the evenings
    - Send the patches + upgrade instructions to clients who are not hosted with us
    - Wait for the support calls in the morning when clients found some incompatibility :)

    Around a week of work, and we are already trying to be as agile as possible :(

    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...
  • 60+ servers? Wow, I would hate to be your DBA!

Add New Comment

Returning? Login