<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.dovetailsoftware.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Suzy Bates</title><link>http://blogs.dovetailsoftware.com/blogs/sbates/default.aspx</link><description /><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.2)</generator><item><title>Some "Predictions" about the world of Development for 2008</title><link>http://blogs.dovetailsoftware.com/blogs/sbates/archive/2008/01/11/some-predictions-about-the-world-of-development-for-2008.aspx</link><pubDate>Fri, 11 Jan 2008 20:14:00 GMT</pubDate><guid isPermaLink="false">5c171a62-8cd2-4aac-8f20-46c3ac3f3269:10934</guid><dc:creator>sbates</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.dovetailsoftware.com/blogs/sbates/comments/10934.aspx</comments><wfw:commentRss>http://blogs.dovetailsoftware.com/blogs/sbates/commentrss.aspx?PostID=10934</wfw:commentRss><description>
&lt;p&gt;In this "look at the year ahead in the world of software" article, there are some interesting views on Ruby on Rails, AJAX, and the (predicted) future of the application and it's developers.&lt;/p&gt;

&lt;p&gt;It's clear the there are differing opinions about all of these subjects, but the one thing that does come out is that there isn't a clear winner for development tools and platforms at the moment.&amp;nbsp; I think it comes down to the strength of the implementation.&amp;nbsp; Clearly, the richness of the interaction will come out on top of how you got there, provided bloat and irrelevant functionality aren't build at the expense of simplicity and usability.&lt;/p&gt;

&lt;p&gt;&amp;nbsp;&lt;/p&gt;

&lt;p&gt;&lt;a href="http://webservices.sys-con.com/read/478303.htm"&gt;
Where's RIAs, AJAX, SOA and Virtualization Headed in 2008&lt;/a&gt;&lt;br&gt;
— 2007 was the undoubtedly the year of Social Networking, but what of 2008? Will '08 be the year of 'Unified Communications' or the year when CMS comes to stand for 'Community Management System' - or even 'Collaboration Management System'? Or will it be the year of a giga-merger, to beat the mere mega-mergers of 2007? As usual at the end of each year, SYS-CON has been informally polling its globe-girdling network of software developers, industry executives, commentators, investors, writers, and editors. As always, the range and depth of their answers is fascinating, throwing light not just on where the industry is going but also how it's going to get there, why, because of who, within what kind of time-scale.&amp;nbsp; Enjoy!&lt;br&gt;&lt;/p&gt;&lt;img src="http://blogs.dovetailsoftware.com/aggbug.aspx?PostID=10934" width="1" height="1"&gt;</description></item><item><title>Incremental Pain or Business Innovation?</title><link>http://blogs.dovetailsoftware.com/blogs/sbates/archive/2007/12/17/incremental-pain-or-business-innovation.aspx</link><pubDate>Mon, 17 Dec 2007 21:05:00 GMT</pubDate><guid isPermaLink="false">5c171a62-8cd2-4aac-8f20-46c3ac3f3269:10854</guid><dc:creator>sbates</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.dovetailsoftware.com/blogs/sbates/comments/10854.aspx</comments><wfw:commentRss>http://blogs.dovetailsoftware.com/blogs/sbates/commentrss.aspx?PostID=10854</wfw:commentRss><description>In this article &lt;a href="http://www.marketingprofs.com/7/engaging-customers-to-produce-real-innovation-shaeffer.asp?part=2"&gt;Five Keys to Engaging the Customer to Produce Real Innovation&lt;/a&gt; on MarketProfs it makes some interesting observations about how to take the next step in a product's evolution.&amp;nbsp; Do you just address the incremental pain they are having or is the time and effort involved to get to the source by learning their business worth it?&lt;br&gt;&lt;img src="http://blogs.dovetailsoftware.com/aggbug.aspx?PostID=10854" width="1" height="1"&gt;</description></item></channel></rss>