<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Core Edges - Latest Comments in TripIt/Dopplr: case in point</title><link>http://macroprinciples.disqus.com/</link><description></description><atom:link href="https://macroprinciples.disqus.com/tripitdopplr_case_in_point/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Tue, 25 Aug 2009 22:37:03 -0000</lastBuildDate><item><title>Re: TripIt/Dopplr: case in point</title><link>http://coreedges.com/blog/2008/02/16/tripitdopplr-case-in-point/#comment-15395628</link><description>&lt;p&gt;Thinking about this a few weeks ago, when I posted a trip to "Boston" because I thought that if I said "Cambridge" it might not reveal some coincidences -- but then I thought it might also have the opposite effect.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Club Penguin Cheats</dc:creator><pubDate>Tue, 25 Aug 2009 22:37:03 -0000</pubDate></item><item><title>Re: TripIt/Dopplr: case in point</title><link>http://coreedges.com/blog/2008/02/16/tripitdopplr-case-in-point/#comment-1558393</link><description>&lt;p&gt;Woohoo... thanks for posting this.  I was just thinking about this a few weeks ago, when I posted a trip to "Boston" because I thought that if I said "Cambridge" it might not reveal some coincidences -- but then I thought it might also have the opposite effect.&lt;/p&gt;&lt;p&gt;As you well know, Julien, we have a cluster of locations around Houston where our colleagues often travel, and the same thing around Paris -- although of course we might naturally enter "Houston" instead of "Sugar Land" and "Paris" instead of "Clamart" already.  Nonetheless, I am glad that the Dopplr guys are so responsive to emerging requirements.  This is "agile development" -- a good lesson for our own software groups to learn, methinks.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Claude Baudoin</dc:creator><pubDate>Sun, 17 Feb 2008 12:43:49 -0000</pubDate></item></channel></rss>