<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (bgporter)</title>
    <link>https://pinboard.in/u:bgporter/public/</link>
    <description>recent bookmarks from bgporter</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="http://blog.backblaze.com/2008/12/15/10-rules-for-how-to-write-cross-platform-code/"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="http://blog.backblaze.com/2008/12/15/10-rules-for-how-to-write-cross-platform-code/">
    <title>Brian’s 10 Rules for how to write cross-platform code | Backblaze Blog</title>
    <dc:date>2010-10-22T14:16:44+00:00</dc:date>
    <link>http://blog.backblaze.com/2008/12/15/10-rules-for-how-to-write-cross-platform-code/</link>
    <dc:creator>bgporter</dc:creator><description><![CDATA[However, I run into other developers or software managers who mistakenly think cross platform code is difficult, or might double or triple the development schedules.  This misconception is based on their bad experiences with badly run porting efforts.   So this article is to quickly outline the 10 simple rules I live by to achieve efficient cross platform code development.
]]></description>
<dc:subject>development cross-platform rules</dc:subject>
<dc:identifier>https://pinboard.in/u:bgporter/b:5757a079704b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:bgporter/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:bgporter/t:cross-platform"/>
	<rdf:li rdf:resource="https://pinboard.in/u:bgporter/t:rules"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>