<?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/"
  >

  <channel rdf:about="http://www.artima.com/weblogs/feeds/bloggers/andydent.rss">
    <title>Andy Dent's Weblog</title>
    <link>http://www.artima.com/weblogs/index.jsp?blogger=andydent</link>
    <description>
Artima Weblogs is a community of bloggers posting on a wide range of topics of interest to software developers.
    </description>
    <image rdf:resource="http://www.artima.com/images/artima88x33.gif"/>
    <items>
      <rdf:Seq>
        <rdf:li resource="http://www.artima.com/weblogs/viewpost.jsp?thread=268226" />
        <rdf:li resource="http://www.artima.com/weblogs/viewpost.jsp?thread=240826" />
        <rdf:li resource="http://www.artima.com/weblogs/viewpost.jsp?thread=240319" />
        <rdf:li resource="http://www.artima.com/weblogs/viewpost.jsp?thread=240268" />
        <rdf:li resource="http://www.artima.com/weblogs/viewpost.jsp?thread=239828" />
        <rdf:li resource="http://www.artima.com/weblogs/viewpost.jsp?thread=220174" />
        <rdf:li resource="http://www.artima.com/weblogs/viewpost.jsp?thread=218195" />
        <rdf:li resource="http://www.artima.com/weblogs/viewpost.jsp?thread=208868" />
        <rdf:li resource="http://www.artima.com/weblogs/viewpost.jsp?thread=189510" />
        <rdf:li resource="http://www.artima.com/weblogs/viewpost.jsp?thread=189208" />
        <rdf:li resource="http://www.artima.com/weblogs/viewpost.jsp?thread=187239" />
        <rdf:li resource="http://www.artima.com/weblogs/viewpost.jsp?thread=180637" />
        <rdf:li resource="http://www.artima.com/weblogs/viewpost.jsp?thread=174969" />
        <rdf:li resource="http://www.artima.com/weblogs/viewpost.jsp?thread=167444" />
        <rdf:li resource="http://www.artima.com/weblogs/viewpost.jsp?thread=167050" />
      </rdf:Seq>
    </items>
  </channel>

  <image rdf:about="http://www.artima.com/images/artima88x33.gif">
    <title>Artima.com</title>
    <url>http://www.artima.com/images/artima88x33.gif</url>
    <link>http://www.artima.com/</link>
  </image>

  <item rdf:about="http://www.artima.com/weblogs/viewpost.jsp?thread=268226">
    <title>Why Learn New Languages? Being Outlived by C++</title>
    <link>http://www.artima.com/weblogs/viewpost.jsp?thread=268226</link>
    <description>
Can a focus on C++ get me through the next twenty-odd years? Is it time to stop chasing bright, shiny new languages and consolidate as a guru? A few thoughts on &amp;quot;legacy languages&amp;quot; and the later stages of a coding career.
    </description>
  </item>

  <item rdf:about="http://www.artima.com/weblogs/viewpost.jsp?thread=240826">
    <title>The Adventures of a Pythonista in Rubyland/2 - No Comprehension</title>
    <link>http://www.artima.com/weblogs/viewpost.jsp?thread=240826</link>
    <description>
Trying to do some simple file processing and strip blank lines, Andy stumbles through the &amp;quot;Ruby is supposed to feel natural&amp;quot; approach and just tries things. The conclusion - Python list comprehensions are still more flexible and powerful than any Ruby feature and inject is possibly the most misleadingly named function I've ever encountered.
    </description>
  </item>

  <item rdf:about="http://www.artima.com/weblogs/viewpost.jsp?thread=240319">
    <title>The Adventures of a Pythonista in Rubyland/1</title>
    <link>http://www.artima.com/weblogs/viewpost.jsp?thread=240319</link>
    <description>
Inspired by the Adventures of a Pythonista in Schemeland series and being engaged in my own learning experience, here's the start of a series by a language geek with about 18 years of OO development experience, trying to get to the heart of Ruby.
    </description>
  </item>

  <item rdf:about="http://www.artima.com/weblogs/viewpost.jsp?thread=240268">
    <title>Unit Testing Frameworks - When to Abandon or Migrate?</title>
    <link>http://www.artima.com/weblogs/viewpost.jsp?thread=240268</link>
    <description>
A large body of unit tests as a regression test system is important to many organizations. What do you do when your framework of choice dies or is neglected? When is it time to move on and how do you budget for abandoning or rewriting tests? Have you ever thought about being caught by this situation?
    </description>
  </item>

  <item rdf:about="http://www.artima.com/weblogs/viewpost.jsp?thread=239828">
    <title>Estimate Archaeology - Unearthing Effort from a Repository</title>
    <link>http://www.artima.com/weblogs/viewpost.jsp?thread=239828</link>
    <description>
An attempt to answer the question - given 1 million lines of code in the repository (i.e. SVN), is there some rule of thumb as to the number of developers we have to keep on staff just to maintain those 1 million lines of code?
    </description>
  </item>

  <item rdf:about="http://www.artima.com/weblogs/viewpost.jsp?thread=220174">
    <title>Ruby vs Python for Code Generation and Flippin' Templates</title>
    <link>http://www.artima.com/weblogs/viewpost.jsp?thread=220174</link>
    <description>
Ruby is the cool new kid of on the block and has some significant cred in code-generation circles. Python has whitespace sensitivities that make it a poorer fit for templating solutions. This sounds like a no-brainer decision but is the real argument about which language the market wants to see used?
    </description>
  </item>

  <item rdf:about="http://www.artima.com/weblogs/viewpost.jsp?thread=218195">
    <title>The Why Diarize Song</title>
    <link>http://www.artima.com/weblogs/viewpost.jsp?thread=218195</link>
    <description>
A shower song to remind me why it's useful to write down alternatives and reasoning.
    </description>
  </item>

  <item rdf:about="http://www.artima.com/weblogs/viewpost.jsp?thread=208868">
    <title>Open-book Interviews with Googling as a Skill</title>
    <link>http://www.artima.com/weblogs/viewpost.jsp?thread=208868</link>
    <description>
Would you hire a programmer who insisted on working things out or using APIs solely from memory? If we expect people to be able to quickly research things on the web as part of the programming, why not include that in interviews? Is search efficiency a skill that should be on your resume?
    </description>
  </item>

  <item rdf:about="http://www.artima.com/weblogs/viewpost.jsp?thread=189510">
    <title>Issues, ThoughtChunks, Variations and Requirements Traceability</title>
    <link>http://www.artima.com/weblogs/viewpost.jsp?thread=189510</link>
    <description>
Everything I'm doing seems to be about small chunks of thought. These chunks need tracking, comparing, versions controlling and melding into presentations of varying narrative richness.

The interesting projects and interested parties include software engineers, publishers and academics but there's no killer app in sight?
    </description>
  </item>

  <item rdf:about="http://www.artima.com/weblogs/viewpost.jsp?thread=189208">
    <title>ROAring Confusion over Finding Services</title>
    <link>http://www.artima.com/weblogs/viewpost.jsp?thread=189208</link>
    <description>
In which Andy suffers an extreme bout of cynical disbelief in the merits of Resource Oriented Architecture and &amp;quot;solving&amp;quot; the discovery problem by giving up and just having a description as part of a &amp;quot;Resource&amp;quot;.
    </description>
  </item>

  <item rdf:about="http://www.artima.com/weblogs/viewpost.jsp?thread=187239">
    <title>Roadmaps vs Architectures</title>
    <link>http://www.artima.com/weblogs/viewpost.jsp?thread=187239</link>
    <description>
How do you develop a Roadmap for a broad-ranging community, encompassing several service-oriented architectures? Here are some ideas.
    </description>
  </item>

  <item rdf:about="http://www.artima.com/weblogs/viewpost.jsp?thread=180637">
    <title>Resigning as a Guru - Low-effort Documentation</title>
    <link>http://www.artima.com/weblogs/viewpost.jsp?thread=180637</link>
    <description>
How do you transfer knowledge about a system in an optimal way, without forever being the 'guy who knows'? What practices will help you exit gracefully? Or, even if you aren't leaving this area of the project, how do you lessen the documentation burden?
    </description>
  </item>

  <item rdf:about="http://www.artima.com/weblogs/viewpost.jsp?thread=174969">
    <title>User Experience - Decrease Stress, Increase Joy</title>
    <link>http://www.artima.com/weblogs/viewpost.jsp?thread=174969</link>
    <description>
There are two kinds of software experience you want for your end users - Invisibility and Smile on My Face.
    </description>
  </item>

  <item rdf:about="http://www.artima.com/weblogs/viewpost.jsp?thread=167444">
    <title>Closed-Source Cocoa - Arrogance, Empowerment or Commercial Necessity?</title>
    <link>http://www.artima.com/weblogs/viewpost.jsp?thread=167444</link>
    <description>
OO frameworks, especially in the C++ world, have usually shipped with source. This is often highly educational and sometimes a life-saver. Until, Apple didn't ship the Cocoa source.
    </description>
  </item>

  <item rdf:about="http://www.artima.com/weblogs/viewpost.jsp?thread=167050">
    <title>CEDSimply - Reading List for Language Designers?</title>
    <link>http://www.artima.com/weblogs/viewpost.jsp?thread=167050</link>
    <description>
Given a solid OO education and C++ background but having missed some of the traditional CS language theory, what is a minimum required reading list, especially when designing a non-traditional language?
    </description>
  </item>

</rdf:RDF>
