<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Revisit Your Design Ideas</title>
	<atom:link href="http://www.juliesoft.com/2008/03/revisit-your-design-ideas/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.juliesoft.com/2008/03/revisit-your-design-ideas/</link>
	<description>solve niche problems, make users happy</description>
	<lastBuildDate>Tue, 29 Jun 2010 18:49:43 -0400</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: jonchase</title>
		<link>http://www.juliesoft.com/2008/03/revisit-your-design-ideas/comment-page-1/#comment-101</link>
		<dc:creator>jonchase</dc:creator>
		<pubDate>Tue, 25 Mar 2008 13:08:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.juliesoft.com/2008/03/24/revisit-your-design-ideas/#comment-101</guid>
		<description>Patrick - 

You&#039;re right - it&#039;s always helpful to have someone else point out the other 20% that I&#039;m always going to miss!

I don&#039;t know why I never thought of munging the CC# data myself on the server side - it&#039;s not too hard to get rid of whitespace, after all:).  I also like the idea of figuring out their CC type for them - maybe I&#039;ll save that for 2.0.  

Your comment exemplifies the point of this post perfectly - even if it looks ok (ever after a revision!), it&#039;s important not to take for granted what could still be improved.</description>
		<content:encoded><![CDATA[<p>Patrick &#8211; </p>
<p>You&#8217;re right &#8211; it&#8217;s always helpful to have someone else point out the other 20% that I&#8217;m always going to miss!</p>
<p>I don&#8217;t know why I never thought of munging the CC# data myself on the server side &#8211; it&#8217;s not too hard to get rid of whitespace, after all:).  I also like the idea of figuring out their CC type for them &#8211; maybe I&#8217;ll save that for 2.0.  </p>
<p>Your comment exemplifies the point of this post perfectly &#8211; even if it looks ok (ever after a revision!), it&#8217;s important not to take for granted what could still be improved.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick McKenzie</title>
		<link>http://www.juliesoft.com/2008/03/revisit-your-design-ideas/comment-page-1/#comment-100</link>
		<dc:creator>Patrick McKenzie</dc:creator>
		<pubDate>Tue, 25 Mar 2008 06:50:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.juliesoft.com/2008/03/24/revisit-your-design-ideas/#comment-100</guid>
		<description>Here&#039;s a freebie for you: you see that portion where you have to tell people what a credit card number looks like?  Why, exactly?  

gsub(/[^0-9]/,&quot;&quot;,creditCardNumber) 

There -- you have now eliminated another class of errors which can frustrate the user.  If you want to be particularly helpful, you can validate the number in semi-realtime (via AJAX or whatever).  Also, is there any need to have folks tell you the card type?  Why don&#039;t you tell *THEM* the card type (which is predictable on the basis of the number):

Card Number: [input box]
Card Type: AJAXified read-only data (or, alternatively, AJAXified combo box)

Similarly, you can catch most of the typos before submission with :

http://en.wikipedia.org/wiki/Luhn_algorithm</description>
		<content:encoded><![CDATA[<p>Here&#8217;s a freebie for you: you see that portion where you have to tell people what a credit card number looks like?  Why, exactly?  </p>
<p>gsub(/[^0-9]/,&#8221;",creditCardNumber) </p>
<p>There &#8212; you have now eliminated another class of errors which can frustrate the user.  If you want to be particularly helpful, you can validate the number in semi-realtime (via AJAX or whatever).  Also, is there any need to have folks tell you the card type?  Why don&#8217;t you tell *THEM* the card type (which is predictable on the basis of the number):</p>
<p>Card Number: [input box]<br />
Card Type: AJAXified read-only data (or, alternatively, AJAXified combo box)</p>
<p>Similarly, you can catch most of the typos before submission with :</p>
<p><a href="http://en.wikipedia.org/wiki/Luhn_algorithm" rel="nofollow">http://en.wikipedia.org/wiki/Luhn_algorithm</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->