<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Chuck Brooks For FutureWare</title>
	<atom:link href="http://futurewaredc.com/fwsweblog/index.php/feed/" rel="self" type="application/rss+xml" />
	<link>http://futurewaredc.com/fwsweblog</link>
	<description>Software That Works! For Health, Home And Office</description>
	<lastBuildDate>Sun, 25 Sep 2011 21:59:53 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>When Size Matters</title>
		<link>http://futurewaredc.com/fwsweblog/index.php/2011/07/29/software-that-works/when-size-matters/</link>
		<comments>http://futurewaredc.com/fwsweblog/index.php/2011/07/29/software-that-works/when-size-matters/#comments</comments>
		<pubDate>Sat, 30 Jul 2011 02:00:31 +0000</pubDate>
		<dc:creator>Chuck Brooks</dc:creator>
				<category><![CDATA[Software That Works]]></category>
		<category><![CDATA[cascading style sheets]]></category>
		<category><![CDATA[css]]></category>
		<category><![CDATA[google chrome]]></category>
		<category><![CDATA[snippets]]></category>
		<category><![CDATA[widgets]]></category>

		<guid isPermaLink="false">http://futurewaredc.com/fwsweblog/index.php/2011/07/29/software-that-works/when-size-matters/</guid>
		<description><![CDATA[Adding html widgets to a website is an easy way to extend services and incorporate new capabilities, but sometimes they don’t always fit well. Changing the spot sizing can be a problem, particularly with hosted sites that are template driven. Here’s a way to solve this with a little help from Google.]]></description>
		<wfw:commentRss>http://futurewaredc.com/fwsweblog/index.php/2011/07/29/software-that-works/when-size-matters/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Designed To Fail</title>
		<link>http://futurewaredc.com/fwsweblog/index.php/2011/03/22/software-that-works/designed-to-fail/</link>
		<comments>http://futurewaredc.com/fwsweblog/index.php/2011/03/22/software-that-works/designed-to-fail/#comments</comments>
		<pubDate>Tue, 22 Mar 2011 07:50:52 +0000</pubDate>
		<dc:creator>Chuck Brooks</dc:creator>
				<category><![CDATA[Software That Works]]></category>
		<category><![CDATA[bad software]]></category>
		<category><![CDATA[client processing]]></category>
		<category><![CDATA[measuring failure]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[quality control]]></category>
		<category><![CDATA[script limitations]]></category>
		<category><![CDATA[stored procedures]]></category>
		<category><![CDATA[technology investment]]></category>

		<guid isPermaLink="false">http://futurewaredc.com/fwsweblog/?p=148</guid>
		<description><![CDATA[Anyone can design a website with today’s scripting environments. Those who shouldn’t create opportunities for those who can, who invariably are called in to clean-up. There are some easy ways to avoid these hidden costs upfront, or determine the clean-up costs afterwards.]]></description>
		<wfw:commentRss>http://futurewaredc.com/fwsweblog/index.php/2011/03/22/software-that-works/designed-to-fail/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Ways To Mitigate Vexing Email Problems</title>
		<link>http://futurewaredc.com/fwsweblog/index.php/2011/03/01/software-that-works/ways-to-mitigate-vexing-email-problems/</link>
		<comments>http://futurewaredc.com/fwsweblog/index.php/2011/03/01/software-that-works/ways-to-mitigate-vexing-email-problems/#comments</comments>
		<pubDate>Tue, 01 Mar 2011 07:50:13 +0000</pubDate>
		<dc:creator>Chuck Brooks</dc:creator>
				<category><![CDATA[Software That Works]]></category>
		<category><![CDATA[email quicksand]]></category>
		<category><![CDATA[managing email]]></category>
		<category><![CDATA[public block lists]]></category>
		<category><![CDATA[small company email]]></category>
		<category><![CDATA[spam]]></category>

		<guid isPermaLink="false">http://futurewaredc.com/fwsweblog/?p=147</guid>
		<description><![CDATA[Email on the internet is a public resource available to everyone and can be abused by anyone. Increasingly we depend on what turns out to be a fragile communications system that in many ways is pure Rube Goldberg in design and operation. Here are some ways, organized as questions and answers, that small companies managing their own email systems can avoid most of the quicksand.]]></description>
		<wfw:commentRss>http://futurewaredc.com/fwsweblog/index.php/2011/03/01/software-that-works/ways-to-mitigate-vexing-email-problems/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Another PHP Memory Allocation Problem</title>
		<link>http://futurewaredc.com/fwsweblog/index.php/2011/01/31/software-that-works/another-php-memory-allocation-problem/</link>
		<comments>http://futurewaredc.com/fwsweblog/index.php/2011/01/31/software-that-works/another-php-memory-allocation-problem/#comments</comments>
		<pubDate>Mon, 31 Jan 2011 07:50:26 +0000</pubDate>
		<dc:creator>Chuck Brooks</dc:creator>
				<category><![CDATA[Software That Works]]></category>
		<category><![CDATA[mysql]]></category>
		<category><![CDATA[open source software]]></category>
		<category><![CDATA[php memory problems]]></category>

		<guid isPermaLink="false">http://futurewaredc.com/fwsweblog/?p=146</guid>
		<description><![CDATA[Memory allocation problems in PHP have many causes, but the error reporting (such as it is) leaves much to be desired in finding a solution. Here’s one fatal memory error cause, and the fix, that is a MySQL 5.3 Community edition ‘feature’ that is particularly vexing. It also happens in version 5.2, but don’t know if if happens with 5.4.]]></description>
		<wfw:commentRss>http://futurewaredc.com/fwsweblog/index.php/2011/01/31/software-that-works/another-php-memory-allocation-problem/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Would You Buy A Used Car From This Man?</title>
		<link>http://futurewaredc.com/fwsweblog/index.php/2011/01/28/potpourri/would-you-buy-a-used-car-from-this-man/</link>
		<comments>http://futurewaredc.com/fwsweblog/index.php/2011/01/28/potpourri/would-you-buy-a-used-car-from-this-man/#comments</comments>
		<pubDate>Fri, 28 Jan 2011 07:50:52 +0000</pubDate>
		<dc:creator>Chuck Brooks</dc:creator>
				<category><![CDATA[Potpourri]]></category>
		<category><![CDATA[Software That Works]]></category>
		<category><![CDATA[first impressions]]></category>
		<category><![CDATA[losing sales]]></category>
		<category><![CDATA[marketing]]></category>
		<category><![CDATA[social media]]></category>

		<guid isPermaLink="false">http://futurewaredc.com/fwsweblog/index.php/2011/01/28/potpourri/would-you-buy-a-used-car-from-this-man/</guid>
		<description><![CDATA[Trite but still true, there’s no second chance to make a first impression. Odd that those peddling social network expertise seemingly ignore this and, perhaps, much else besides.]]></description>
		<wfw:commentRss>http://futurewaredc.com/fwsweblog/index.php/2011/01/28/potpourri/would-you-buy-a-used-car-from-this-man/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Signing Your Work</title>
		<link>http://futurewaredc.com/fwsweblog/index.php/2010/12/30/software-that-works/signing-your-work/</link>
		<comments>http://futurewaredc.com/fwsweblog/index.php/2010/12/30/software-that-works/signing-your-work/#comments</comments>
		<pubDate>Thu, 30 Dec 2010 07:50:23 +0000</pubDate>
		<dc:creator>Chuck Brooks</dc:creator>
				<category><![CDATA[Software That Works]]></category>
		<category><![CDATA[graphical design]]></category>
		<category><![CDATA[program skins]]></category>
		<category><![CDATA[software aesthetics]]></category>

		<guid isPermaLink="false">http://futurewaredc.com/fwsweblog/?p=144</guid>
		<description><![CDATA[Paintings and sculptures can be identified by workmanship details, which sometimes are better authentications than a signature. Software can be similarly identified, and for the same reasons.]]></description>
		<wfw:commentRss>http://futurewaredc.com/fwsweblog/index.php/2010/12/30/software-that-works/signing-your-work/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Simplifying Help With A Floating Window</title>
		<link>http://futurewaredc.com/fwsweblog/index.php/2010/11/30/software-that-works/simplifying-help-with-a-floating-window/</link>
		<comments>http://futurewaredc.com/fwsweblog/index.php/2010/11/30/software-that-works/simplifying-help-with-a-floating-window/#comments</comments>
		<pubDate>Tue, 30 Nov 2010 07:50:58 +0000</pubDate>
		<dc:creator>Chuck Brooks</dc:creator>
				<category><![CDATA[Software That Works]]></category>
		<category><![CDATA[jquery]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[popup windows]]></category>
		<category><![CDATA[yui]]></category>

		<guid isPermaLink="false">http://futurewaredc.com/fwsweblog/?p=143</guid>
		<description><![CDATA[Software frameworks earn their keep by reducing development effort, but sometimes managing a simple click through their Byzantine paths complicate simple things. Here’s what we did when all we wanted was to get a little help without losing our place in the workflow.
]]></description>
		<wfw:commentRss>http://futurewaredc.com/fwsweblog/index.php/2010/11/30/software-that-works/simplifying-help-with-a-floating-window/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Sloppy Software From Beginning To End</title>
		<link>http://futurewaredc.com/fwsweblog/index.php/2010/09/28/software-that-works/sloppy-software-from-beginning-to-end/</link>
		<comments>http://futurewaredc.com/fwsweblog/index.php/2010/09/28/software-that-works/sloppy-software-from-beginning-to-end/#comments</comments>
		<pubDate>Tue, 28 Sep 2010 07:50:35 +0000</pubDate>
		<dc:creator>Chuck Brooks</dc:creator>
				<category><![CDATA[Software That Works]]></category>
		<category><![CDATA[incomplete uninstalls]]></category>
		<category><![CDATA[shareware]]></category>
		<category><![CDATA[sloppy software]]></category>
		<category><![CDATA[software development tools]]></category>
		<category><![CDATA[software investment]]></category>
		<category><![CDATA[try before you buy]]></category>

		<guid isPermaLink="false">http://futurewaredc.com/fwsweblog/?p=142</guid>
		<description><![CDATA[While judging a book by its cover may not always be a good thing, judging software by its installation process can be a good indicator of overall product quality. The uninstall process can be a confirmation of the decision to do so.]]></description>
		<wfw:commentRss>http://futurewaredc.com/fwsweblog/index.php/2010/09/28/software-that-works/sloppy-software-from-beginning-to-end/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Flash CS5 For Designers Book Review</title>
		<link>http://futurewaredc.com/fwsweblog/index.php/2010/09/15/software-that-works/flash-cs5-for-designers-book-review/</link>
		<comments>http://futurewaredc.com/fwsweblog/index.php/2010/09/15/software-that-works/flash-cs5-for-designers-book-review/#comments</comments>
		<pubDate>Wed, 15 Sep 2010 07:50:05 +0000</pubDate>
		<dc:creator>Chuck Brooks</dc:creator>
				<category><![CDATA[Software That Works]]></category>
		<category><![CDATA[animation]]></category>
		<category><![CDATA[CS5]]></category>
		<category><![CDATA[Flash]]></category>
		<category><![CDATA[graphics]]></category>
		<category><![CDATA[video]]></category>

		<guid isPermaLink="false">http://futurewaredc.com/fwsweblog/?p=141</guid>
		<description><![CDATA[The latest version of Flash, part of Adobe’s CS5, has many changes, new features and extended capabilities that increase productivity and improve workflow. This not only adds some complexity, and can cause confusion on where familiar tool settings and controls are now, but in some cases are not accurately described in the official Adobe documentation. This book, by authors with international experience and expertise with Flash, addresses these issues with well written explanations and detailed exercises and training aids.]]></description>
		<wfw:commentRss>http://futurewaredc.com/fwsweblog/index.php/2010/09/15/software-that-works/flash-cs5-for-designers-book-review/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Blogs As Bait And Comment Containment</title>
		<link>http://futurewaredc.com/fwsweblog/index.php/2010/09/07/software-that-works/blogs-as-bait-and-comment-containment/</link>
		<comments>http://futurewaredc.com/fwsweblog/index.php/2010/09/07/software-that-works/blogs-as-bait-and-comment-containment/#comments</comments>
		<pubDate>Tue, 07 Sep 2010 07:50:30 +0000</pubDate>
		<dc:creator>Chuck Brooks</dc:creator>
				<category><![CDATA[Software That Works]]></category>
		<category><![CDATA[blog comments]]></category>
		<category><![CDATA[blog spidering]]></category>
		<category><![CDATA[captcha]]></category>
		<category><![CDATA[spam]]></category>

		<guid isPermaLink="false">http://futurewaredc.com/fwsweblog/?p=140</guid>
		<description><![CDATA[Like email spam, hijacked email addresses and money transfers from Nigeria, the inevitability of automated blog comment submittals have become more than nuisances. Here’s a few ways to control these pests without making things too difficult to legitimate readers’ comments.]]></description>
		<wfw:commentRss>http://futurewaredc.com/fwsweblog/index.php/2010/09/07/software-that-works/blogs-as-bait-and-comment-containment/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

