<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://mikerozlog.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Latest News from Mike Rozlog</title>
 <link>http://mikerozlog.sys-con.com/</link>
 <description>Latest News from Mike Rozlog</description>
 <language>en</language>
 <copyright>Copyright 2009 Ulitzer.com</copyright>
 <generator>Ulitzer.com</generator>
 <lastBuildDate>Wed, 09 Dec 2009 04:46:27 EST</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>360</ttl>
<item>
 <title>Standardized Tooling: Building Bridges, Not Walls</title>
 <link>http://mikerozlog.sys-con.com/node/941430</link>
 <description>Some walls are necessary. We use brick-and-mortar walls to support buildings and firewalls to protect our computers from attack. But not all walls are good. Consider the Berlin Wall, a wall of segregation. It divided a country and its citizens, but has subsequently been brought down by people working together because upon re-evaluation the Wall did more harm than good.&lt;p&gt;&lt;a href=&quot;http://mikerozlog.sys-con.com/node/941430&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Wed, 29 Apr 2009 15:45:00 EDT</pubDate>
 <guid isPermaLink="true">http://mikerozlog.sys-con.com/node/941430</guid>
 <comments>http://mikerozlog.sys-con.com/node/941430#feedback</comments>
</item>
<item>
 <title>Software Archeology: What Is It and Why Should Java Developers Care?</title>
 <link>http://mikerozlog.sys-con.com/node/487614</link>
 <description>The term Software Archeology has been used in various forms since early 2001. The concept of Software Archeology is an approach or methodology that helps individual team members or entire teams to understand exactly what they have in the code they&#039;re going to be working on. The approach is also very useful when deconstructing an existing piece of software to find patterns of design and development that could be &#039;harvested&#039; in future developments.&lt;p&gt;&lt;a href=&quot;http://mikerozlog.sys-con.com/node/487614&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Mon, 28 Jan 2008 11:00:00 EST</pubDate>
 <guid isPermaLink="true">http://mikerozlog.sys-con.com/node/487614</guid>
 <comments>http://mikerozlog.sys-con.com/node/487614#feedback</comments>
</item>
<item>
 <title>Disaster Recovery Plans Be Prepared</title>
 <link>http://mikerozlog.sys-con.com/node/159572</link>
 <description>It would seem only logical that after 9/11, one of the most horrific days in American history, corporations large and small would be ready for unforeseen catastrophic events. However, by one recent estimate, less than 38% have put a complete disaster recovery plan in place - the policies, processes, procedures, and architecture to deal with unforeseen events. In the wake of Hurricanes Katrina and Rita, IT managers are again forced to reassess how well prepared they and their organizations are to manage through and recover from natural or man-made disasters.&lt;p&gt;&lt;a href=&quot;http://mikerozlog.sys-con.com/node/159572&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Mon, 26 Dec 2005 10:15:00 EST</pubDate>
 <guid isPermaLink="true">http://mikerozlog.sys-con.com/node/159572</guid>
 <comments>http://mikerozlog.sys-con.com/node/159572#feedback</comments>
</item>
</channel>
</rss>
