<story><title>How We Make Trello</title><url>http://blog.fogcreek.com/how-we-make-trello/</url></story><parent_chain></parent_chain><comment><author>edwinnathaniel</author><text>I&amp;#x27;m more interested to know the actual technical details of the build and testing process than the &amp;quot;Task-List&amp;quot; software development based approach because that can be done by any software project management tools (even JIRA).&lt;p&gt;What&amp;#x27;s missing in this article is the whole Continuous Delivery technical aspect of it.&lt;p&gt;What do you guys use to build the NodeJS app?&lt;p&gt;What do you guys use to test the NodeJS app?&lt;p&gt;What do you guys use to check the code coverage of the NodeJS app?&lt;p&gt;What do you guys use to test the front-end?&lt;p&gt;What is the automated testing strategy?&lt;p&gt;How do you store artifacts of builds, schema migration (if using RDBMS) or handle different model versions, how do you rollback (what&amp;#x27;s the rollback strategy)?</text></comment>
<story><title>How We Make Trello</title><url>http://blog.fogcreek.com/how-we-make-trello/</url></story><parent_chain></parent_chain><comment><author>badman_ting</author><text>It&amp;#x27;s almost comical how nobody at my company would ever take a project this seriously. Good for them, Trello is awesome.</text></comment>