<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel rdf:about="http://blogmarks.net/api/marks/link/3112208">
<title>Public marks on http://blog.objectmentor.com/articles/2009/02/26/10-papers-every-programmer-should-read-at-least-twice</title>
<description>Public marks on http://blog.objectmentor.com/articles/2009/02/26/10-papers-every-programmer-should-read-at-least-twice</description>
<link>http://blogmarks.net/marks/link/3112208</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/ghis/mark/1058236923"/>
<rdf:li resource="http://blogmarks.net/api/user/ronpish/mark/1058223880"/>
<rdf:li resource="http://blogmarks.net/api/user/greut/mark/1058223734"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/ghis/mark/1058236923">
<title>10 Papers Every Programmer Should Read (At Least Twice)</title>
<link>http://blog.objectmentor.com/articles/2009/02/26/10-papers-every-programmer-should-read-at-least-twice</link>
<description></description>
<dc:date>2009-03-11T02:17:50Z</dc:date>
<dc:author>ghis</dc:author>
<dc:subject>programming</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://blog.objectmentor.com/articles/2009/02/26/10-papers-every-programmer-should-read-at-least-twice"><img border="0" src="http://blogmarks.net/screenshots/2009/03/11/707804ae12fb6ab1e63d4dc5634ed2d8.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://blog.objectmentor.com/articles/2009/02/26/10-papers-every-programmer-should-read-at-least-twice">10 Papers Every Programmer Should Read (At Least Twice)</a></h4>
 
by <a href="http://blogmarks.net/user/ghis">ghis</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/3112208">2 other(s)</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/programming">programming</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058236923">Copy</a> | 
<a href="http://blogmarks.net/link/3112208">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/ronpish/mark/1058223880">
<title>10 Papers Every Programmer Should Read (At Least Twice)</title>
<link>http://blog.objectmentor.com/articles/2009/02/26/10-papers-every-programmer-should-read-at-least-twice</link>
<description></description>
<dc:date>2009-02-27T10:08:57Z</dc:date>
<dc:author>ronpish</dc:author>
<dc:subject>code</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://blog.objectmentor.com/articles/2009/02/26/10-papers-every-programmer-should-read-at-least-twice"><img border="0" src="http://blogmarks.net/screenshots/2009/03/11/707804ae12fb6ab1e63d4dc5634ed2d8.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://blog.objectmentor.com/articles/2009/02/26/10-papers-every-programmer-should-read-at-least-twice">10 Papers Every Programmer Should Read (At Least Twice)</a></h4>
 
by <a href="http://blogmarks.net/user/ronpish">ronpish</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/3112208">2 other(s)</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/code">code</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058223880">Copy</a> | 
<a href="http://blogmarks.net/link/3112208">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/greut/mark/1058223734">
<title>10 Papers Every Programmer Should Read (At Least Twice)</title>
<link>http://blog.objectmentor.com/articles/2009/02/26/10-papers-every-programmer-should-read-at-least-twice</link>
<description>&lt;blockquote&gt;&lt;p&gt;I realized that instead of complaining, I could help by pointing to some papers which are easily available online and which (to me at least) point to some of the most interesting ideas about software. To me, these are classic papers which contain deep &lt;q&gt;things you oughta know&lt;/q&gt; about code – the material you work with.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;added to the toread list&lt;/p&gt;</description>
<dc:date>2009-02-27T07:04:21Z</dc:date>
<dc:author>greut</dc:author>
<dc:subject>code, work, todo, paper</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://blog.objectmentor.com/articles/2009/02/26/10-papers-every-programmer-should-read-at-least-twice"><img border="0" src="http://blogmarks.net/screenshots/2009/03/11/707804ae12fb6ab1e63d4dc5634ed2d8.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://blog.objectmentor.com/articles/2009/02/26/10-papers-every-programmer-should-read-at-least-twice">10 Papers Every Programmer Should Read (At Least Twice)</a></h4>
 
by <a href="http://blogmarks.net/user/greut">greut</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/3112208">2 other(s)</a> 
<div class="description"><blockquote><p>I realized that instead of complaining, I could help by pointing to some papers which are easily available online and which (to me at least) point to some of the most interesting ideas about software. To me, these are classic papers which contain deep <q>things you oughta know</q> about code – the material you work with.</p></blockquote>
<p>added to the toread list</p></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/code">code</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/work">work</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/todo">todo</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/paper">paper</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058223734">Copy</a> | 
<a href="http://blogmarks.net/link/3112208">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>