<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Latest Comments for kastner</title><link>http://disqus.com/by/kastner/</link><description></description><atom:link href="http://disqus.com/kastner/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Mon, 28 Dec 2009 14:48:12 -0000</lastBuildDate><item><title>Re: Continuous deployment for mission-critical applications</title><link>http://www.startuplessonslearned.com/2009/12/continuous-deployment-for-mission.html#comment-27404562</link><description>&lt;p&gt;That brings up an interesting question. How much of the test suite is run by a developer during TDD, and how much is run before they commit to the mainline branch that WILL be deployed in short order? Are the tests tiered?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kastner</dc:creator><pubDate>Mon, 28 Dec 2009 14:48:12 -0000</pubDate></item><item><title>Re: Continuous deployment for mission-critical applications</title><link>http://www.startuplessonslearned.com/2009/12/continuous-deployment-for-mission.html#comment-27403970</link><description>&lt;p&gt;How much to technological choices like OOP vs. Procedural code or rsync vs. packaged releases effect continuous deployment?&lt;/p&gt;&lt;p&gt;For example, I know that flickr is mostly procedural, but you tout TDD which, while not impossible to apply to procedural code bases, is usually geared towards OOP&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kastner</dc:creator><pubDate>Mon, 28 Dec 2009 14:36:54 -0000</pubDate></item></channel></rss>