<?xml version="1.0" encoding="utf-8"?>
			
			<rss version="2.0">
			<channel>
			<title>Hal Helms On Web Development - Product</title>
			<link>http://www.halhelms.com/blog/index.cfm</link>
			<description>Hal Helms talks about web development.</description>
			<language>en-us</language>
			<pubDate>Wed, 08 Sep 2010 20:14:08 -0400</pubDate>
			<lastBuildDate>Fri, 09 Apr 2010 08:08:00 -0400</lastBuildDate>
			<generator>BlogCFC</generator>
			<docs>http://blogs.law.harvard.edu/tech/rss</docs>
			<managingEditor>hal@halhelms.com</managingEditor>
			<webMaster>hal@halhelms.com</webMaster>
			
			
			
			
			
			<item>
				<title>Adobe v. Apple Misses an Important Point</title>
				<link>http://www.halhelms.com/blog/index.cfm/2010/4/9/Adobe-v-Apple-Misses-an-Important-Point</link>
				<description>
				
				Well, the internet is roiling with accusations, conspiracy theories, cross-complaints -- you name it -- regarding Apple&apos;s much ballyhooed smackdown on Adobe&apos;s Flash. I found this comment to be particularly telling:

&quot;The iPad is an anti-technology device targeting consumers who are too lazy/stupid to use or want a keyboard or mouse or stylus. Why should a website focusing on tech-savvy people modify their code to play along with the silly-ass marketing scheme Apple plays making its airhead users _think_ they&apos;re some kind of pioneers?&quot;

Let&apos;s stipulate that Apple is not too fond of Adobe. Why? Who knows. And it was particularly cold-blooded of them to let Adobe develop their Flash-to-iPhone technology, dropping this bombshell only a few days before the release of CS5. Let&apos;s stipulate, in fact, that Apple is bristling with its own power -- and is using it with shocking disregard for what other members of the tech community think.

But we techies miss an important point that Apple does not: computers are too damned hard for normal people to use. In the tradeoff between power and ease-of-use, techies will always choose power. Apple really does seem intent on making a computer &quot;for the rest of us&quot; -- and that means that power must/will be sacrificed to make the device(s) simple to use. And reliable. And having a decent battery life.

Does Apple&apos;s decision to cut Flash off at the knees make sense? It depends on whose interests you&apos;re thinking of. Is it good for you and me who crave all the power we can get? No. But is it good for the vast numbers of people who just want a computer that works and are frustrated by the unintended side effects of power run amok? Reluctantly, I have to say yes.
				
				</description>
						
				
				<category>Product</category>				
				
				<category>General</category>				
				
				<pubDate>Fri, 09 Apr 2010 08:08:00 -0400</pubDate>
				<guid>http://www.halhelms.com/blog/index.cfm/2010/4/9/Adobe-v-Apple-Misses-an-Important-Point</guid>
				
			</item>
			
		 	
			
			
			<item>
				<title>Project Serenity</title>
				<link>http://www.halhelms.com/blog/index.cfm/2009/6/30/Project-Serenity</link>
				<description>
				
				Every cool project needs a cool code name. The open source ColdFusion ecommerce project now has one: Project Serenity.
				 [More]
				</description>
						
				
				<category>Product</category>				
				
				<category>ColdFusion</category>				
				
				<category>Software Development</category>				
				
				<category>Code</category>				
				
				<pubDate>Tue, 30 Jun 2009 11:32:00 -0400</pubDate>
				<guid>http://www.halhelms.com/blog/index.cfm/2009/6/30/Project-Serenity</guid>
				
			</item>
			
		 	
			
			
			<item>
				<title>Tweets for the Week Ending 06.26.09</title>
				<link>http://www.halhelms.com/blog/index.cfm/2009/6/29/Tweets-for-the-Week-Ending-062609</link>
				<description>
				
				I&apos;ve been on twitter for a while now. Typically, I&apos;ll post 4-5 tweets a day that are technical in nature. Lots of people don&apos;t follow Twitter religiously, so each Monday, I&apos;ll post on my tweets for the last week.
				 [More]
				</description>
						
				
				<category>jQuery</category>				
				
				<category>Product</category>				
				
				<category>Prototype</category>				
				
				<category>Software Development</category>				
				
				<category>General</category>				
				
				<pubDate>Mon, 29 Jun 2009 11:09:00 -0400</pubDate>
				<guid>http://www.halhelms.com/blog/index.cfm/2009/6/29/Tweets-for-the-Week-Ending-062609</guid>
				
			</item>
			
		 	
			
			
			<item>
				<title>XMind: Free Mindmapping Tool</title>
				<link>http://www.halhelms.com/blog/index.cfm/2009/3/5/XMind-Free-Mindmapping-Tool</link>
				<description>
				
				I&apos;ve used, I think, all of the mindmapping tools available. Recently, I discovered XMind, another entry in the field. After working with it, I&apos;m very impressed. It&apos;s interface is intuitive, it&apos;s fast, it looks good and it prints well. It comes in both a free and a paid version. I&apos;m using the free version and find it the best I&apos;ve worked with. 

Worth checking out at xmind.net.
				
				</description>
						
				
				<category>Product</category>				
				
				<pubDate>Thu, 05 Mar 2009 08:09:00 -0400</pubDate>
				<guid>http://www.halhelms.com/blog/index.cfm/2009/3/5/XMind-Free-Mindmapping-Tool</guid>
				
			</item>
			
		 	
			
			
			<item>
				<title>jQuery Ate My Homework</title>
				<link>http://www.halhelms.com/blog/index.cfm/2009/2/2/jQuery-Ate-My-Homework</link>
				<description>
				
				Well, I had my January newsletter almost wrapped. The centerpiece was an article on event delegation. That&apos;s a technique used to get around the limitation that an element added to the DOM does not &quot;inherit&quot; events that may have been bound to other, similar elements. 

An example: if I bind all images&apos; &quot;mouseover&quot; function so that a tooltip appears, and then add another image element dynamically to the DOM, that new image won&apos;t have the desired mouseover behavior.
				 [More]
				</description>
						
				
				<category>Product</category>				
				
				<category>Javascript</category>				
				
				<pubDate>Mon, 02 Feb 2009 10:44:00 -0400</pubDate>
				<guid>http://www.halhelms.com/blog/index.cfm/2009/2/2/jQuery-Ate-My-Homework</guid>
				
			</item>
			
		 	
			
			
			<item>
				<title>Book Review: Outliers</title>
				<link>http://www.halhelms.com/blog/index.cfm/2008/11/27/Book-Review-Outliers</link>
				<description>
				
				&lt;img src=&quot;http://208.112.31.201/blog/images//outliers.jpg&quot;&gt;
Malcolm Gladwell, author of &lt;i&gt;Tipping Point&lt;/i&gt; and &lt;i&gt;Blink&lt;/i&gt; has a new book: &lt;i&gt;Outliers: The Story of Success&quot; &lt;/i&gt;. Gladwell is a wonderful writer, drawing the reader in and making connections that are non-obvious but often profound.&lt;more /&gt;

This book breaks down the myth of the Genius that arises, &lt;i&gt;sui generis&lt;/i&gt;, from humble circumstances, propelled by the power of his (it&apos;s almost always a man) greatness.

In &lt;i&gt;Outliers&lt;/i&gt;, Gladwell argues that outliers, those &quot;data points&quot; that fall outside the expected normal distribution, can&apos;t be understood apart from familial and cultural factors that shape the person&apos;s life in unexpected ways.

Gladwell is at his best when drawing surprising connections, and this book has some great ones. I love books like this: it makes me think very differently beyond what appears obvious.

Content: 4.5

Readability: 4.5

Recommended For: People interested in going beyond the myths of rugged individualism and the inevitability of the Great Man.
				
				</description>
						
				
				<category>Product</category>				
				
				<category>General</category>				
				
				<category>Philosophy</category>				
				
				<pubDate>Thu, 27 Nov 2008 18:36:00 -0400</pubDate>
				<guid>http://www.halhelms.com/blog/index.cfm/2008/11/27/Book-Review-Outliers</guid>
				
			</item>
			
		 	
			
			
			<item>
				<title>Two Months with Axure</title>
				<link>http://www.halhelms.com/blog/index.cfm/2008/11/24/Two-Months-with-Axure</link>
				<description>
				
				About two months ago, I started working with Axure Pro RP (&lt;a href=&quot;http://www.axure.com&quot;&gt;www.axure.com&lt;/a&gt;). (Just for the record, I have no financial interest in the company.) The software allows non-programmers to create medium-fidelity prototypes. I&apos;ve written and spoken extensively on how important I consider prototyping to be, so I thought some folks would like to hear my impressions of working with the program after two months.

PROS
* Very easy and fast to create prototypes
* Very little time needed to get up to speed with the program
* Allows for fair amount of conditional logic -- especially considering that the software is meant for non-programmers
* Comes with a good selection of widgets
* &quot;Dynamic panels&quot; allow for good Ajax-like state changes of portions of the page

CONS
* Doesn&apos;t allow for user feedback via something like DevNotes (see &lt;a href=&quot;http://grokfusebox.com&quot;&gt;Jeff Peters&apos; site&lt;/a&gt; for my DevNotes program)
* Very limited ability to add customized widgets -- and that by a hack
* No fancy DHTML capabilities
* No real programmability to extend the code
* How-to materials and tutorials are not extensive

Those are the bullet points. All in all, I&apos;d say I&apos;m quite happy with Axure. It&apos;s not nearly the behemoth that iRise is (another prototyping tool) and that&apos;s both to its advantage and disadvantage. Since my ultimate goal is to offload the majority of prototype work to others, the ease of use and short learning cycle is very important. Yes, I&apos;d love it to be more capable, but, of course, that would increase the complexity.

As for the company itself, I&apos;ve found the company to be responsive to my questions and requests. There is pending litigation from iRise for patent violation. I&apos;m not a lawyer (thank you, God) so I won&apos;t offer my opinions of over-reaching lawsuits. Really, I won&apos;t.

My recommendation: Take a serious look at Axure if you&apos;re sold on the virtue of prototypes. Consider how quickly you can turn prototypes around using software like this. In my case, I typically have a new rev of the prototype within 48 hours of getting customer feedback. I think you may find Axure will change the way you build software for the better.

Axure costs $589 and the one-year subscription for updates and support costs $149.
				
				</description>
						
				
				<category>Product</category>				
				
				<category>Prototype</category>				
				
				<category>Software Development</category>				
				
				<pubDate>Mon, 24 Nov 2008 12:30:00 -0400</pubDate>
				<guid>http://www.halhelms.com/blog/index.cfm/2008/11/24/Two-Months-with-Axure</guid>
				
			</item>
			
		 	
			</channel></rss>