<?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: Rounded Corners &#8211; 171 (Sex it up)</title>
	<atom:link href="http://labnotes.org/2007/12/10/rounded-corners-171-sex-it-up/feed/" rel="self" type="application/rss+xml" />
	<link>http://labnotes.org/2007/12/10/rounded-corners-171-sex-it-up/</link>
	<description></description>
	<lastBuildDate>Sun, 15 Jan 2012 21:29:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Assaf</title>
		<link>http://labnotes.org/2007/12/10/rounded-corners-171-sex-it-up/comment-page-1/#comment-139186</link>
		<dc:creator>Assaf</dc:creator>
		<pubDate>Sun, 16 Dec 2007 21:57:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labnotes.org/2007/12/10/rounded-corners-171-sex-it-up/#comment-139186</guid>
		<description>Michael, I come from that world, and that list reads to me like effects, not causes.  The underlying cause is simple: enterprise software is not built for the people who use it.

If there was focus on people, the priorities would reflect that, so it wouldn&#039;t be a priority issue.

Legacy integration would be about &#039;making legacy easier to use&#039;, not &#039;making legacy accessible to my J2EE&#039;s ESB JCA connector&#039;.

The technology limitations would not exist, different vendors and products would raise based on their ability to deliver products that address people better.

UI doesn&#039;t grace with age, but good legacy UI is better than bad legacy UI (I still use Vim and bash), so for one legacy apps would work the better.  As it stands, many internal apps are designed like it&#039;s 1999.</description>
		<content:encoded><![CDATA[<p>Michael, I come from that world, and that list reads to me like effects, not causes.  The underlying cause is simple: enterprise software is not built for the people who use it.</p>
<p>If there was focus on people, the priorities would reflect that, so it wouldn&#8217;t be a priority issue.</p>
<p>Legacy integration would be about &#8216;making legacy easier to use&#8217;, not &#8216;making legacy accessible to my J2EE&#8217;s ESB JCA connector&#8217;.</p>
<p>The technology limitations would not exist, different vendors and products would raise based on their ability to deliver products that address people better.</p>
<p>UI doesn&#8217;t grace with age, but good legacy UI is better than bad legacy UI (I still use Vim and bash), so for one legacy apps would work the better.  As it stands, many internal apps are designed like it&#8217;s 1999.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Krigsman</title>
		<link>http://labnotes.org/2007/12/10/rounded-corners-171-sex-it-up/comment-page-1/#comment-139185</link>
		<dc:creator>Michael Krigsman</dc:creator>
		<pubDate>Sun, 16 Dec 2007 21:25:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labnotes.org/2007/12/10/rounded-corners-171-sex-it-up/#comment-139185</guid>
		<description>&quot;Rationalization for lousy engineering&quot;? Not quite. My blog postings represent an accurate statement of why enterprise software is in it&#039;s current state. Do I think that&#039;s a good thing? No. Do I understand how we got here? You bet.

Enterprise 2.0 is bringing change into enterprise software, but the issue is far more complex than simple usability or better user interfaces. In other words, the situation will improve over time, but to effectively drive change, one needs to first understand the starting point.

Michael Krigsman
Blog: http://blogs.zdnet.com/projectfailures
Twitter: http://twitter.com/mkrigsman</description>
		<content:encoded><![CDATA[<p>&#8220;Rationalization for lousy engineering&#8221;? Not quite. My blog postings represent an accurate statement of why enterprise software is in it&#8217;s current state. Do I think that&#8217;s a good thing? No. Do I understand how we got here? You bet.</p>
<p>Enterprise 2.0 is bringing change into enterprise software, but the issue is far more complex than simple usability or better user interfaces. In other words, the situation will improve over time, but to effectively drive change, one needs to first understand the starting point.</p>
<p>Michael Krigsman<br />
Blog: <a href="http://blogs.zdnet.com/projectfailures" rel="nofollow">http://blogs.zdnet.com/projectfailures</a><br />
Twitter: <a href="http://twitter.com/mkrigsman" rel="nofollow">http://twitter.com/mkrigsman</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

