<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
<channel>
<title>architected_info</title>
<link>http://www.beyeblogs.com/architected_info/</link>
<description>How people, practices, and information are transformed into relationships and understanding.</description>
<language>en</language>
<copyright>Copyright 2007</copyright>
<lastBuildDate>Mon, 12 Mar 2007 12:00:00 -0700</lastBuildDate>
<generator>http://www.movabletype.org/?v=3.33</generator>
<docs>http://blogs.law.harvard.edu/tech/rss</docs> 


<item>
<title> A Very Useful Engine</title>
<description><![CDATA[<p>A while back, <a href="http://www.architected.info/blog/how-to-build-a-system">I wrote</a> about how useful it would be to be able to combine collaborative information and structured data. While Wikis and other collaborative information sources are great, I would argue that they aren't truly useful (yet).</p>

<p>Recently, ran across an organization that is turning <a href="http://www.wikipedia.org">Wikipedia</a> entries into downloadable datasets</a> that are available today. Very, very, very cool.</p>

<p>To learn more about <a href="http://www.architected.info/blog/a-very-useful-engine">this very useful engine</a> and more, take a look at <a href="http://www.architected.info">architected.info</a>.</p>]]></description>
<link>http://www.beyeblogs.com/architected_info/archive/2007/03/a_very_useful_e.php</link>
<guid>http://www.beyeblogs.com/architected_info/archive/2007/03/a_very_useful_e.php</guid>
<category></category>
<pubDate>Mon, 12 Mar 2007 12:00:00 -0700</pubDate>
</item>

<item>
<title>EC2, Licensing, and Competitive Advantage</title>
<description><![CDATA[<p>I have been working with <a href="http://aws.amazon.com/">Amazon Web Services</a> (and <a href="http://aws.amazon.com/ec2">EC2</a>) a lot lately, and have made some observations that really fly in the face of conventional wisdom.</p>

<p>I work in <a href="http://www.architected.info/blog/category/transformation/etl/">ETL</a>, which means I need to get a hold of big iron to crunch on big data.   Machines are expensive, licenses are expensive, storage and networks are cheap.  This is very different from  Amazon's compute farm approach, which changes the economics of the game, especially with respect to software licensing ...</p>  

<p>To learn more about <a href="http://www.architected.info/blog/ec2-licensing-and-competitive-advantage">EC2, licensing, and competitive advantage</a> and more, take a look at <a href="http://www.architected.info">architected.info</a>.</p>
]]></description>
<link>http://www.beyeblogs.com/architected_info/archive/2006/12/ec2_licensing_a_1.php</link>
<guid>http://www.beyeblogs.com/architected_info/archive/2006/12/ec2_licensing_a_1.php</guid>
<category></category>
<pubDate>Fri, 08 Dec 2006 12:30:00 -0700</pubDate>
</item>

<item>
<title>The Tyranny of the Average</title>
<description><![CDATA[<p><a href="http://blogs.business2.com/design/">Seen and Not Seen</a> has an interesting post about "<a href="http://blogs.business2.com/design/2006/11/little_people_b.html#more">the tyranny of the average</a>" in the design world.  This graphic tells the gist of the story very clearly:</p>
<p align="center"><img src="http://blogs.business2.com/design/images/heightcurve_2.gif" /></p>
<p>This has got me thinking about a lot of things we do in the data world, especially with respect to business intelligence.</p>

<p>To learn more about <a href="http://www.architected.info/blog/the-tyranny-of-the-average">the the tyranny of the average</a> and more, take a look at <a href="http://www.architected.info">architected.info</a>.</p>
]]></description>
<link>http://www.beyeblogs.com/architected_info/archive/2006/11/the_tyranny_of.php</link>
<guid>http://www.beyeblogs.com/architected_info/archive/2006/11/the_tyranny_of.php</guid>
<category></category>
<pubDate>Thu, 16 Nov 2006 15:45:00 -0700</pubDate>
</item>

<item>
<title>Millenial Culture Wars</title>
<description><![CDATA[<p><strong>Youth cannot know how age thinks and feels.  But old men are guilty if they forget what it was to be young.<br />
</strong></p>
<p>-- <a href="http://www.quotationspage.com/quotes/J._K._Rowling/">J.K. Rowling</a></p>

<p>One of the massive changes every organization is going to have to deal with in the coming years is the <a href="http://www.generationsatwork.com/articles/millenials.htm">arrival of the millenials in the workplace</a>.  These are folks who have been raised on the Web, IM, and SMS.  They are <a href="http://technologysource.org/article/digital_natives_digital_immigrants/">digital natives</a>, who think nothing about taking two disparate systems and tying them together with AJAX or whatever is at hand. This is going to be a scary time for a lot of IT organizations, especially ones who are led by <a href="http://technologysource.org/article/digital_natives_digital_immigrants/">digital immigrants</a>. It will be the changing of the guard, the face-off between two cultures who are both large, ego-driven, and don't want to be ignored.</p>
<p>In my time in the industry, I have seen (and heard recounted) the history of a number of cultural conflicts:</p>
<ul>
	<li>Mainframes vs. Midframes</li>
	<li>Midframes vs. PC's.</li>
	<li>Copybooks vs. Databases</li>
	<li>Databases vs. Spreadsheets</li>
	<li>Memos vs. Email</li>
</ul>
<p>In each of these cases, the "old timers" resented the "young turks" who had no respect for how things ought to run.  At the same time, the turks resented the fact that they had to work so hard to do somethng that was so obviously needed.  In retrospect, it wasn't an issue of right or wrong, it was a question of new vs. established.</p>

<p>To learn more about <a href="http://www.architected.info/blog/millenial-culture-wars">the culture wars</a> and more, take a look at <a href="http://www.architected.info">architected.info</a><br />
</p>]]></description>
<link>http://www.beyeblogs.com/architected_info/archive/2006/08/millenial_cultu.php</link>
<guid>http://www.beyeblogs.com/architected_info/archive/2006/08/millenial_cultu.php</guid>
<category></category>
<pubDate>Sun, 27 Aug 2006 21:45:00 -0700</pubDate>
</item>

<item>
<title>The Millenial Culture Wars</title>
<description><![CDATA[<p><strong>Youth cannot know how age thinks and feels.  But old men are guilty if they forget what it was to be young.<br />
</strong></p>
<p>-- <a href="http://www.quotationspage.com/quotes/J._K._Rowling/">J.K. Rowling</a></p>

<p>One of the massive changes every organization is going to have to deal with in the coming years is the <a href="http://www.generationsatwork.com/articles/millenials.htm">arrival of the millenials in the workplace</a>.  These are folks who have been raised on the Web, IM, and SMS.  They are <a href="http://technologysource.org/article/digital_natives_digital_immigrants/">digital natives</a>, who think nothing about taking two disparate systems and tying them together with AJAX or whatever is at hand. This is going to be a scary time for a lot of IT organizations, especially ones who are led by <a href="http://technologysource.org/article/digital_natives_digital_immigrants/">digital immigrants</a>. It will be the changing of the guard, the face-off between two cultures who are both large, ego-driven, and don't want to be ignored.</p>
<p>In my time in the industry, I have seen (and heard recounted) the history of a number of cultural conflicts:</p>
<ul>
	<li>Mainframes vs. Midframes</li>
	<li>Midframes vs. PC's.</li>
	<li>Copybooks vs. Databases</li>
	<li>Databases vs. Spreadsheets</li>
	<li>Memos vs. Email</li>
</ul>
<p>In each of these cases, the "old timers" resented the "young turks" who had no respect for how things ought to run.  At the same time, the turks resented the fact that they had to work so hard to do somethng that was so obviously needed.  In retrospect, it wasn't an issue of right or wrong, it was a question of new vs. established.</p>

<p>To learn more about <a href="http://www.architected.info/blog/millenial-culture-wars">the culture wars</a> and more, take a look at <a href="http://www.architected.info">architected.info</a><br />
</p>]]></description>
<link>http://www.beyeblogs.com/architected_info/archive/2006/08/the_millenial_c.php</link>
<guid>http://www.beyeblogs.com/architected_info/archive/2006/08/the_millenial_c.php</guid>
<category></category>
<pubDate>Sun, 27 Aug 2006 21:30:00 -0700</pubDate>
</item>

<item>
<title>Enterprise Web 2.0, Linux, and Ecclesiastes</title>
<description><![CDATA[<p>Lately I have been pondering the impact of things like <a href="http://www.architected.info/blog/think-locally-act-locally">SOA</a> and<br /><a href="http://www.architected.info/blog/an-interesting-mash-up">mashups</a> in the enterprise context, blending in the <a href="http://radar.oreilly.com/archives/2006/08/round_2_dial_tone.html">web dialtone</a> discussion that is happening on the <a href="http://radar.oreilly.com/">O'Reilly Radar</a>.</p></p>

<p>This has some interesting applications, especially with<a href="http://www.architected.info/blog/category/transformation/db/">data</a> and <a href="http://www.architected.info/blog/category/transformation/etl/">ETL</a> ...</p>

<p>You can read about <a href="http://www.architected.info/blog/enterprise-web-20-linux-and-ecclesiastes">enterprise web 2.0</a> and more at <a href="http://www.architected.info">architected.info</a>.<br />
</p>]]></description>
<link>http://www.beyeblogs.com/architected_info/archive/2006/08/enterprise_web.php</link>
<guid>http://www.beyeblogs.com/architected_info/archive/2006/08/enterprise_web.php</guid>
<category></category>
<pubDate>Sun, 20 Aug 2006 18:30:00 -0700</pubDate>
</item>

<item>
<title>8 Truths About Standardization (Especially for Data and ETL)</title>
<description><![CDATA[<p>The <a href="http://today.reuters.com/News/CrisesArticle.aspx?storyId=L16224965">ongoing debate</a> about the planetary status of <a href="http://www.nineplanets.org/pluto.html">Pluto</a> is a really great example of how the standards-making process really works.   Like most debates, everyone involved is supposed to be rational, thinking adults.  The most rational, thinking people on earth: <a href="http://en.wikipedia.org/wiki/Scientists">scientists</a>.</p>

<p>This planetary debate is highly charged, personal, emotional, contradictory at times, and ended with a solution that defies logic and mollifies more than it satisfies.  Of course, this reminds me of the times I have been sitting in a room trying to decide on standard ways to do or classify things.  For the most part, this has been as a technologist (around <a href="http://www.architected.info/blog/category/transformation/db/">data</a>,  <a href="http://www.architected.info/blog/category/transformation/etl/">ETL</a> and <a href="http://www.architected.info/blog/category/practices/architecture/">architecture</a>), but also as a member of a business and as a leader in a non-profit organization ...</p>

<p>You can read about <a href="http://www.architected.info/blog/8-truths-about-standardization-especially-for-data-and-etl">the 8 truths</a> and more at <a href="http://www.architected.info">architected.info</a></p>]]></description>
<link>http://www.beyeblogs.com/architected_info/archive/2006/08/8_truths_about.php</link>
<guid>http://www.beyeblogs.com/architected_info/archive/2006/08/8_truths_about.php</guid>
<category></category>
<pubDate>Sun, 20 Aug 2006 13:30:00 -0700</pubDate>
</item>

<item>
<title>WWHD (What Would A Hacker Do)?</title>
<description><![CDATA[<p>Slashdot had an interesting thread on creative responses to security threats. The problem was that people were having others try to piggy-back over their private wireless network. </p>

<p>The solutions, ranged from scary to annoying to hilarious. Instead of taking the enterprise route (find a vendor, spend some money, integrate the system) it is interesting to see what a web hacker would do in the same situation ...</p>

<p>You can read about <a href="http://www.architected.info/blog/wwhd-what-would-a-hacker-do">hackers</a> and more at <a href="http://www.architected.info">architected.info</a></p>]]></description>
<link>http://www.beyeblogs.com/architected_info/archive/2006/08/wwhd_what_would.php</link>
<guid>http://www.beyeblogs.com/architected_info/archive/2006/08/wwhd_what_would.php</guid>
<category></category>
<pubDate>Tue, 15 Aug 2006 08:00:00 -0700</pubDate>
</item>

<item>
<title>Versatility and Value</title>
<description><![CDATA[<p>Industry rag <a href="http://www.computerworld.com/">Computerworld</a> has <a href="http://10.10.10.123/action/article.do?command=viewArticleBasic&articleId=112360&pageNumber=1">a great article</a> about job skills and the marketplace.  It predicts that:</p>

<blockquote><p>[In] 2010 ... IT departments will be populated with "versatilists" -- those with a technology background who also know the business sector inside and out, can architect and carry out IT plans that will add business value, and can cultivate relationships ...</p></blockquote>

<p>An interesting idea, but is it right?</p>

<p>You can read more about <a href="http://www.architected.info/blog/the-value-of-versatility">versatilists</a> and more at <a href="http://www.architected.info">architected.info</a></p>]]></description>
<link>http://www.beyeblogs.com/architected_info/archive/2006/08/versatility_and.php</link>
<guid>http://www.beyeblogs.com/architected_info/archive/2006/08/versatility_and.php</guid>
<category></category>
<pubDate>Sun, 13 Aug 2006 20:45:00 -0700</pubDate>
</item>

<item>
<title> Why Requirements are Difficult</title>
<description><![CDATA[<p>Having problems dealing with requirements from your customers? It could be worse … imagine if the placement of a single comma cost you $2.13 million!  This story is a great reminder why creating, maintaing, and following requirements is so difficult in technology projects ... </p>

<p>You can find about <a href="http://www.architected.info/blog/why-requirements-are-difficult">this</a> and more at <a href="http://architected.info">architected.info</a>.<br />
</p>]]></description>
<link>http://www.beyeblogs.com/architected_info/archive/2006/08/_why_requiremen.php</link>
<guid>http://www.beyeblogs.com/architected_info/archive/2006/08/_why_requiremen.php</guid>
<category></category>
<pubDate>Sat, 12 Aug 2006 16:45:00 -0700</pubDate>
</item>

<item>
<title>Bad Information Quality Can Be Devastating</title>
<description><![CDATA[<p>A New Jersey NBC affiliate reported on a shocking turn of events where a deceased infant was accidentally cremated, because:</p>

<blockquote>one of the babies being registered inconsistently at the morgue and in the hospital’s admissions database.</blockquote>

<p>And the real travesty is that this isn’t the worst part of the story ...</p>

<p>You can find about <a href="http://www.architected.info/blog/bad-information-quality-can-be-devastating">this</a> and more at <a href="http://architected.info">architected.info</a>.<br />
</p>]]></description>
<link>http://www.beyeblogs.com/architected_info/archive/2006/08/bad_information.php</link>
<guid>http://www.beyeblogs.com/architected_info/archive/2006/08/bad_information.php</guid>
<category></category>
<pubDate>Wed, 09 Aug 2006 21:30:00 -0700</pubDate>
</item>

<item>
<title>Poor Information Quality Hits Home</title>
<description><![CDATA[<p>Due to a data processing error, the City of <a href="http://www.cityofmuncie.com/">Muncie</a>, Indiana incorrectly assessed property taxes on several large non-profit institutions.  The inflated total was then used for budgeting, causing a huge shortfall.  </p>

<p>Of course, the people most impacted were the <a href="http://www.firstresponder.org/">first responders</a>.</p>

<p>You can find about <a href="http://www.architected.info/blog/poor-information-quality-hits-home">this</a> and more at <a href="http://architected.info">architected.info</a>.<br />
</p>]]></description>
<link>http://www.beyeblogs.com/architected_info/archive/2006/08/poor_informatio.php</link>
<guid>http://www.beyeblogs.com/architected_info/archive/2006/08/poor_informatio.php</guid>
<category></category>
<pubDate>Tue, 08 Aug 2006 06:30:00 -0700</pubDate>
</item>


</channel>
</rss>