<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cf="http://www.microsoft.com/schemas/rss/core/2005" xmlns:media="http://search.yahoo.com/mrss/" xmlns:ymusic="http://music.yahoo.com/rss/1.0/ymusic/" xmlns:contact="http://lucidocean.com/contact" xmlns:crss="http://lucidocean.com/crss" xmlns:sx="http://www.microsoft.com/schemas/rss/sse" xmlns:content="http://purl.org/dc/terms/" version="2.0">
  <channel>
    <dc:creator>Lucid Ocean Limited</dc:creator>
    <contact:method url="http://www.skype.com">
      <contact:uid>lucidocean</contact:uid>
      <contact:provider>skype</contact:provider>
      <contact:options>skype:lucidocean?call</contact:options>
    </contact:method>
    <crss:disclaimer url="http://www.lucidocean.com/general/disclaimer.aspx">&amp;lt;br /&amp;gt;
hello</crss:disclaimer>
    <crss:details url="http://www.lucidocean.com/">
      <crss:name>Lucid Ocean Limited</crss:name>
    </crss:details>
    <crss:feed url="http://www.lucidocean.com/getrss.aspx" />
    <crss:aggregation />
    <title>Latest News via RSS</title>
    <link>http://www.lucidocean.com/</link>
    <description>Lucid Ocean Software Development Latest News</description>
    <copyright>copyright © 2006-2007, Lucid Ocean Limited</copyright>
    <webMaster>contact@lucidocean.com</webMaster>
    <generator>WebStream - www.lucidocean.com</generator>
    <ttl>1440</ttl>
    <item>
      <dc:date>2007-11-02T09:56:58-07:00</dc:date>
      <dc:language>en-GB</dc:language>
      <content:abstract>From &lt;a href="http://www.martinfowler.com"&gt;Martin Fowler&lt;/a&gt; - post on &lt;a href="http://www.infoq.com/presentations/modifiability-fowler"&gt;Modifiability: Or is there Design in Agility?&lt;/a&gt; &lt;br /&gt;
After watching it, here are my thoughts on the matter...&lt;span id="ctl00_MainContent_ctl00_lblContent"&gt;COMMON, UNIFIED, PATTERNED and PREDICTABLE....&lt;/span&gt;</content:abstract>
      <content:created>2007-10-26T07:30:00-07:00</content:created>
      <content:modified>2007-11-02T09:56:58-07:00</content:modified>
      <media:description type="plain" />
      <media:keywords>software modifiability, software agility, agile software, malleable software, changing software, code for change, change management</media:keywords>
      <title>Modifiability</title>
      <link>http://www.lucidocean.com/Blogs/Jonathan/Modifiability_1862505d2d674da2a6510cde1dbec710.aspx</link>
      <description>From &lt;a href="http://www.martinfowler.com"&gt;Martin Fowler&lt;/a&gt; - post on &lt;a href="http://www.infoq.com/presentations/modifiability-fowler"&gt;Modifiability: Or is there Design in Agility?&lt;/a&gt; &lt;br /&gt;
After watching it, here are my thoughts on the matter...&lt;span id="ctl00_MainContent_ctl00_lblContent"&gt;COMMON, UNIFIED, PATTERNED and PREDICTABLE....&lt;/span&gt;</description>
      <author>contact@lucidocean.com</author>
      <pubDate>2007-10-26T08:54:05-07:00</pubDate>
    </item>
    <item>
      <dc:date>2007-11-02T09:41:26-07:00</dc:date>
      <dc:language>en-GB</dc:language>
      <content:abstract>I would like to propose a new way of thinking about the ubiquitous software &lt;strong&gt;&amp;ldquo;contract&amp;rdquo;&lt;/strong&gt;. &lt;br /&gt;
You and I to a lesser or greater extent design and/or implement interfaces in most software activities. We create them knowingly and some times as an affect of or in consequence of writing within an environment. For example, you can use C#, to create some object, which is now &amp;ldquo;contracted&amp;rdquo; to System.Object and then you extend that interface with more members, un</content:abstract>
      <content:created>2007-11-02T09:24:00-07:00</content:created>
      <content:modified>2007-11-02T09:41:26-07:00</content:modified>
      <media:description type="plain" />
      <media:keywords />
      <title>ShapeShifting Interfaces</title>
      <link>http://www.lucidocean.com/Blogs/Jonathan/ShapeShifting_Interfaces_3228746a246e4ffda25a9843df2804cb.aspx</link>
      <description>I would like to propose a new way of thinking about the ubiquitous software &lt;strong&gt;&amp;ldquo;contract&amp;rdquo;&lt;/strong&gt;. &lt;br /&gt;
You and I to a lesser or greater extent design and/or implement interfaces in most software activities. We create them knowingly and some times as an affect of or in consequence of writing within an environment. For example, you can use C#, to create some object, which is now &amp;ldquo;contracted&amp;rdquo; to System.Object and then you extend that interface with more members, un</description>
      <author>contact@lucidocean.com</author>
      <pubDate>2007-11-02T09:36:08-07:00</pubDate>
    </item>
    <item>
      <dc:date>2007-10-26T11:48:29-07:00</dc:date>
      <dc:language>en-GB</dc:language>
      <content:abstract>The CAM according to the CAM book (specifications), the &amp;quot;Content Model describes the components used to build a learning experience from learning resources&amp;quot;. It then further explai...</content:abstract>
      <content:created>2007-10-11T12:54:00-07:00</content:created>
      <content:modified>2007-10-26T11:48:29-07:00</content:modified>
      <media:description type="plain" />
      <media:keywords>CAM, SCORM, ADL, XML, e-learning, learning schemas</media:keywords>
      <title>CAM Overview</title>
      <link>http://www.lucidocean.com/ClearContent/CAM_Overview_ec2f7feee230467eaf25b7951aecd2d3.aspx</link>
      <description>The CAM according to the CAM book (specifications), the &amp;quot;Content Model describes the components used to build a learning experience from learning resources&amp;quot;. It then further explai...</description>
      <author>contact@lucidocean.com</author>
      <pubDate>2007-10-11T12:53:52-07:00</pubDate>
    </item>
    <item>
      <dc:date>2007-10-26T07:12:51-07:00</dc:date>
      <dc:language>en-GB</dc:language>
      <content:abstract>A class that works with a collection of leaf classes, that each point to it's parent. In effect a composite in reverse. Keep all the leaf objects in a collection and build the heirarchy from the bottom up.</content:abstract>
      <content:created>2007-10-11T13:16:00-07:00</content:created>
      <content:modified>2007-10-26T07:12:51-07:00</content:modified>
      <media:description type="plain" />
      <media:keywords />
      <title>Reverse Composite Pattern</title>
      <link>http://www.lucidocean.com/Software_Patterns/Design_Patterns/Reverse_Composite_Pattern_592c03a58cad4cf2b7a60142c8788b3c.aspx</link>
      <description>A class that works with a collection of leaf classes, that each point to it's parent. In effect a composite in reverse. Keep all the leaf objects in a collection and build the heirarchy from the bottom up.</description>
      <author>contact@lucidocean.com</author>
      <pubDate>2007-10-11T13:34:11-07:00</pubDate>
    </item>
    <item>
      <dc:date>2007-10-25T11:10:26-07:00</dc:date>
      <dc:language>en-GB</dc:language>
      <content:abstract>Frameworks offer architecture and a means for reuse that can offer agility  in our modern world. If you are developing a piece of code, thinking of it as a  Framework, instils a way of thinking that promotes reuse, extensibility and  agility. But first we have to understand what it is and then how useful it can  be....</content:abstract>
      <content:created>2007-10-11T13:28:00-07:00</content:created>
      <content:modified>2007-10-25T11:10:26-07:00</content:modified>
      <media:description type="plain" />
      <media:keywords />
      <title>A Framework is a Class</title>
      <link>http://www.lucidocean.com/Software_Patterns/Frameworks/A_Framework_is_a_Class_8dcddca8563040b6a3ba94c1b659fad4.aspx</link>
      <description>Frameworks offer architecture and a means for reuse that can offer agility  in our modern world. If you are developing a piece of code, thinking of it as a  Framework, instils a way of thinking that promotes reuse, extensibility and  agility. But first we have to understand what it is and then how useful it can  be....</description>
      <author>contact@lucidocean.com</author>
      <pubDate>2007-10-25T11:05:24-07:00</pubDate>
    </item>
    <item>
      <dc:date>2007-10-25T07:26:35-07:00</dc:date>
      <dc:language>en-GB</dc:language>
      <content:abstract>There is really no excuse to not use Transactions in your code. MSDTC makes it easier than ever. To use it in your .NET project, simply.....</content:abstract>
      <content:created>2007-10-25T06:30:00-07:00</content:created>
      <content:modified>2007-10-25T07:26:35-07:00</content:modified>
      <media:description type="plain" />
      <media:keywords />
      <title>UseTransactions</title>
      <link>http://www.lucidocean.com/Blogs/Jonathan/UseTransactions_56723343848c417ab3dd0a1b35dd7869.aspx</link>
      <description>There is really no excuse to not use Transactions in your code. MSDTC makes it easier than ever. To use it in your .NET project, simply.....</description>
      <author>contact@lucidocean.com</author>
      <pubDate>2007-10-25T07:24:06-07:00</pubDate>
    </item>
    <item>
      <dc:date>2007-10-22T16:47:37-07:00</dc:date>
      <dc:language>en-GB</dc:language>
      <content:abstract>An in-progress Pattern Language for Designing Software Frameworks.</content:abstract>
      <content:created>2007-10-11T13:12:00-07:00</content:created>
      <content:modified>2007-10-22T16:47:37-07:00</content:modified>
      <media:description type="plain" />
      <media:keywords />
      <title>D4 Software Framework</title>
      <link>http://www.lucidocean.com/Software_Patterns/Frameworks/D4_Software_Framework_2756673d4b7c4cfe967f7d74cd5bfa8a.aspx</link>
      <description>An in-progress Pattern Language for Designing Software Frameworks.</description>
      <author>contact@lucidocean.com</author>
      <pubDate>2007-10-11T13:11:51-07:00</pubDate>
    </item>
    <item>
      <dc:date>2007-10-22T08:22:38-07:00</dc:date>
      <dc:language>en-GB</dc:language>
      <content:abstract>also named - SplitCreate, SplitReader, SplitUpdate, SplitDelete</content:abstract>
      <content:created>2007-10-22T07:37:00-07:00</content:created>
      <content:modified>2007-10-22T08:22:38-07:00</content:modified>
      <media:description type="plain" />
      <media:keywords />
      <title>PhazedCRUD</title>
      <link>http://www.lucidocean.com/Software_Patterns/Design_Patterns/PhazedCRUD_856b9d4a096c407eb7d2a151ffbf7fbf.aspx</link>
      <description>also named - SplitCreate, SplitReader, SplitUpdate, SplitDelete</description>
      <author>contact@lucidocean.com</author>
      <pubDate>2007-10-22T07:37:55-07:00</pubDate>
    </item>
    <item>
      <dc:date>2007-10-22T07:41:13-07:00</dc:date>
      <dc:language>en-GB</dc:language>
      <content:abstract>You need to populate an object in two phazes which could be dependant on a condition or constraint..</content:abstract>
      <content:created>2007-10-09T14:23:00-07:00</content:created>
      <content:modified>2007-10-22T07:41:13-07:00</content:modified>
      <media:description type="plain" />
      <media:keywords>Design Patterns, GOF, Data patterns, software design</media:keywords>
      <title>SplitPopulator</title>
      <link>http://www.lucidocean.com/Software_Patterns/Design_Patterns/SplitPopulator_fa9b930235e94d4f99ae01adb0cfecac.aspx</link>
      <description>You need to populate an object in two phazes which could be dependant on a condition or constraint..</description>
      <author>contact@lucidocean.com</author>
      <pubDate>2007-10-09T14:41:43-07:00</pubDate>
    </item>
    <item>
      <dc:date>2007-10-21T10:56:32-07:00</dc:date>
      <dc:language>en-GB</dc:language>
      <content:abstract>This document outlines principles of good design for software. Since the topic is extremely wide, I focus in on the principles and abstractions of the topic. It is not an epiphany, but a collection of thoughts from my experience within design put into wor...</content:abstract>
      <content:created>2007-04-13T14:25:31-07:00</content:created>
      <content:modified>2007-10-21T10:56:32-07:00</content:modified>
      <media:description type="plain" />
      <media:keywords />
      <title>Immerse into good design principles</title>
      <link>http://www.lucidocean.com/Software_Patterns/Frameworks/Immerse_into_good_design_principles_cdcde346867b4888bcbdd3015354.aspx</link>
      <description>This document outlines principles of good design for software. Since the topic is extremely wide, I focus in on the principles and abstractions of the topic. It is not an epiphany, but a collection of thoughts from my experience within design put into wor...</description>
      <author>contact@lucidocean.com</author>
      <pubDate>2007-03-20T13:39:38-07:00</pubDate>
    </item>
  </channel>
</rss>