tag:blogger.com,1999:blog-3636450771110845075.post3283893168973569853..comments2008-05-27T13:12:28.051-04:00Don Wallacehttp://www.blogger.com/profile/06143899184466551166noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-3636450771110845075.post-53917498804213241572008-05-24T21:31:00.000-04:002008-05-24T21:31:00.000-04:00Wow Don,<BR/><BR/>What a great article. I'm going to have to read it a few more times just to make sure it's all sunk in. <BR/><BR/>It's just amazing how many company web sites I've visited that left me with NO IDEA what the company does!Starr Hornechatspring.comnoreply@blogger.comtag:blogger.com,1999:blog-3636450771110845075.post-79411944496086357732008-05-23T23:17:00.000-04:002008-05-23T23:17:00.000-04:00Thanks, Don. A Nice summary and a message to few developers get. One of the hardest things for them to do is actually write how their customer speaks, too. I think a lot of us actually do speak the way we write and that's a problem that's not exclusive to this industry (academia faces the same issue). So in some respects we need to also change how we speak ourselves in order to change how we write conversationally - beyond just avoiding "industry buzz words".Scott Kanehttp://www.davidscottkane.comnoreply@blogger.com