<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Macro Principles - Latest Comments in General</title><link>http://macroprinciples.disqus.com/</link><description></description><language>en</language><lastBuildDate>Mon, 02 Jun 2008 08:59:04 -0000</lastBuildDate><item><title>Re: Dopplr and Tripit: next-gen strategies ? Part 2</title><link>http://www.macroprinciples.com/2008/02/dopplr-and-tripit-next-gen-strategies-part-2/#comment-570943</link><description>Glad you liked it :-) We're striving to find a means to make this a&lt;br&gt;reality...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jnestour</dc:creator><pubDate>Mon, 02 Jun 2008 08:59:04 -0000</pubDate></item><item><title>Re: Innovators in corporate IT = the new VCs ?</title><link>http://www.macroprinciples.com/2008/05/innovators-in-corporate-it-the-new-vcs/#comment-560463</link><description>Yes. I would agree. We at BrightIdea have seen similarities between VCs and Innovation Officers at corporations. A lot of our customers are using BrightIdea to collect ideas, rank them, and allow users to collaborate on the ideas eventually turning them into reality. The job of the Innovation Officer is to facilitate ideation and innovation throughout that process. As a technology vendor, we cannot succeed without that human element.&lt;br&gt;&lt;br&gt;Paul&lt;br&gt;&lt;a href="mailto:ptran@brightidea.com"&gt;ptran@brightidea.com&lt;/a&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Paul Tran</dc:creator><pubDate>Fri, 30 May 2008 22:25:32 -0000</pubDate></item><item><title>Re: Dopplr and Tripit: next-gen strategies ? Part 2</title><link>http://www.macroprinciples.com/2008/02/dopplr-and-tripit-next-gen-strategies-part-2/#comment-556518</link><description>+1 on that!.&lt;br&gt;A recommendation engine based on, say, years of experience, segment/division of work within the company, other shared interests would be a killer feature.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">abhilash</dc:creator><pubDate>Fri, 30 May 2008 13:32:29 -0000</pubDate></item><item><title>Re: Protected: API GCMIT</title><link>http://www.macroprinciples.com/2008/04/api-gcmit/#comment-331665</link><description>Test comment: this is not supposed to show up on the community page...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jnestour</dc:creator><pubDate>Sun, 13 Apr 2008 20:35:49 -0000</pubDate></item><item><title>Re: Returns to cooperation</title><link>http://www.macroprinciples.com/2008/02/returns-to-cooperation/#comment-331632</link><description>Test comment for Disqus, nothing to read here :-)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jnestour</dc:creator><pubDate>Sun, 13 Apr 2008 20:26:00 -0000</pubDate></item><item><title>Re: TripIt/Dopplr: case in point</title><link>http://www.macroprinciples.com/2008/02/tripitdopplr-case-in-point/#comment-1558393</link><description>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;br&gt;&lt;br&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.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Claude Baudoin</dc:creator><pubDate>Sun, 17 Feb 2008 17:43:49 -0000</pubDate></item></channel></rss>