<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
<title>Simon St. Laurent on O&apos;Reilly Broadcast</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/" />
<link rel="self" type="application/atom+xml" href="http://broadcast.oreilly.com/atom.xml" />
<id>tag:broadcast.oreilly.com,2008-08-07://53</id>
<updated>2010-02-17T18:59:19Z</updated>

<generator uri="http://www.sixapart.com/movabletype/">Movable Type Pro 4.21-en</generator>

<entry>
<title>A Live Edition for Learning Rails</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2010/02/a-live-edition-for-learning-ra.html" />
<id>tag:broadcast.oreilly.com,2010://53.39159</id>

<published>2010-02-17T18:59:19Z</published>
<updated>2010-02-17T18:59:19Z</updated>

<summary>One of the best things about Rails is that it&apos;s under constant development.  New features appear constantly, and the upcoming 3.0 release even streamlines the architecture substantially.  This wonderful track record of incremental development gives developers an ever-better set of tools to work with, but is really difficult for those of us documenting those tools in old-fashioned ink and paper.  I&apos;m very happy to announce that O&apos;Reilly has released the Live Edition of Learning Rails, which brings the book up to date from its original November 2008 release (covering Rails 2.1.0) to last month (covering Rails 2.3.5), as well as incorporating errata. </summary>
<author>
<name>Simon St. Laurent</name>
<uri>http://simonstl.com/</uri>
</author>

<category term="beta" label="beta" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="publishing" label="publishing" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="rails" label="rails" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
One of the best things about Rails is that it&apos;s under constant development.  New features appear constantly, and the upcoming 3.0 release even streamlines the architecture substantially.  This wonderful track record of incremental development gives developers an ever-better set of tools to work with, but is really difficult for those of us documenting those tools in old-fashioned ink and paper.  I&apos;m very happy to announce that O&apos;Reilly has released the Live Edition of Learning Rails, which brings the book up to date from its original November 2008 release (covering Rails 2.1.0) to last month (covering Rails 2.3.5), as well as incorporating errata. 
</content>
</entry>

<entry>
<title>170 years of tech book publishing, demonstrated</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2010/02/170-years-of-tech-book-history.html" />
<id>tag:broadcast.oreilly.com,2010://53.39148</id>

<published>2010-02-16T13:35:33Z</published>
<updated>2010-02-16T13:35:33Z</updated>

<summary>Some of the most fascinating technical writing I&apos;ve encountered recently was written 170 years ago.  How is that possible?  And just how different was it?  The Joiner and Cabinet Maker is a recent re-issue of a long-forgotten 1839 book on an apprenticeship in woodworking.  Unlike most books of the time, it covers the first few steps into woodworking in detail, rather than providing a vague general description or covering only advanced techiques. This reprint, though, goes beyond the usual simple reproduction or even explanatory notes.  It includes notes, yes, but also a detailed introduction, a recreation of the projects in modern prose and photographs, DVD slideshows, SketchUp diagrams, and an appendix on the techniques used to print the originals.  Though it is intended as a book about woodworking, it also does a tremendous job demonstrating changes in technical writing.</summary>
<author>
<name>Simon St. Laurent</name>
<uri>http://simonstl.com/</uri>
</author>

<category term="apprentice" label="apprentice" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="audience" label="audience" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="binding" label="binding" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="diy" label="DIY" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="history" label="history" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="publishing" label="publishing" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="techbook" label="tech book" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="woodwork" label="woodwork" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
Some of the most fascinating technical writing I&apos;ve encountered recently was written 170 years ago.  How is that possible?  And just how different was it?  The Joiner and Cabinet Maker is a recent re-issue of a long-forgotten 1839 book on an apprenticeship in woodworking.  Unlike most books of the time, it covers the first few steps into woodworking in detail, rather than providing a vague general description or covering only advanced techiques. This reprint, though, goes beyond the usual simple reproduction or even explanatory notes.  It includes notes, yes, but also a detailed introduction, a recreation of the projects in modern prose and photographs, DVD slideshows, SketchUp diagrams, and an appendix on the techniques used to print the originals.  Though it is intended as a book about woodworking, it also does a tremendous job demonstrating changes in technical writing.
</content>
</entry>

<entry>
<title>The Widening HTML5 Chasm</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2010/02/the-widening-html5-chasm.html" />
<id>tag:broadcast.oreilly.com,2010://53.39139</id>

<published>2010-02-15T15:59:16Z</published>
<updated>2010-02-15T15:59:16Z</updated>

<summary>Recent claims that Adobe is blocking HTML5 are glaringly wrong, reflecting mostly the incompatibilities between the two organizations, the W3C and WHATWG, sharing the process. Ideally, I&apos;d like to see the W3C take its consensus-based process seriously, and the WHATWG agree to abide by that. Realistically, I just can&apos;t see either part of that happening. The W3C is too willing to bend; the WHATWG too unwilling.</summary>
<author>
<name>Simon St. Laurent</name>
<uri>http://simonstl.com/</uri>
</author>

<category term="adobe" label="adobe" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="flash" label="Flash" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="html5" label="html 5" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="standardization" label="standardization" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="w3c" label="w3c" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="whatwg" label="WHATWG" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
Recent claims that Adobe is blocking HTML5 are glaringly wrong, reflecting mostly the incompatibilities between the two organizations, the W3C and WHATWG, sharing the process. Ideally, I&apos;d like to see the W3C take its consensus-based process seriously, and the WHATWG agree to abide by that. Realistically, I just can&apos;t see either part of that happening. The W3C is too willing to bend; the WHATWG too unwilling.
</content>
</entry>

<entry>
<title>How dare Apple...</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2010/01/how-dare-apple.html" />
<id>tag:broadcast.oreilly.com,2010://53.39012</id>

<published>2010-01-28T23:25:36Z</published>
<updated>2010-01-28T23:25:36Z</updated>

<summary>Back in 1984, when the Macintosh 128K had just arrived, I wandered down to Chemung Electronics to take a look at this supposed upgrade from the Apple ][ world. It was okay until I asked the salesman, &quot;so how do I write programs on this thing?&quot; He laughed and said I&apos;d have to buy that separately. They&apos;d even have to special-order it. Today, I find myself reading pieces from a lot of good people (Tim Bray, Alex Payne) who share the dismay of my 13-year-old self. How could Apple release a product so exclusively oriented to consumption, rather than production?</summary>
<author>
<name>Simon St. Laurent</name>
<uri>http://simonstl.com/</uri>
</author>

<category term="creativity" label="creativity" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="ipad" label="iPad" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="mac" label="Mac" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="programming" label="programming" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
Back in 1984, when the Macintosh 128K had just arrived, I wandered down to Chemung Electronics to take a look at this supposed upgrade from the Apple ][ world. It was okay until I asked the salesman, &quot;so how do I write programs on this thing?&quot; He laughed and said I&apos;d have to buy that separately. They&apos;d even have to special-order it. Today, I find myself reading pieces from a lot of good people (Tim Bray, Alex Payne) who share the dismay of my 13-year-old self. How could Apple release a product so exclusively oriented to consumption, rather than production?
</content>
</entry>

<entry>
<title>Programming as Live Performance</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/06/programming-as-live-performanc.html" />
<id>tag:broadcast.oreilly.com,2009://53.36658</id>

<published>2009-06-03T22:08:10Z</published>
<updated>2009-06-03T22:08:10Z</updated>

<summary>As I&apos;m writing this, twenty people are watching their peers write code.  They aren&apos;t looking over anyone&apos;s shoulders, or doing peer programming - they&apos;re watching mirrors of screens at the TopCoder Open, seeing exactly how competitors work their way through algorithm problems in C++, Java, and C#.  Is this something we should be doing more of?</summary>
<author>
<name>Simon St. Laurent</name>
<uri>http://simonstl.com/</uri>
</author>

<category term="competition" label="competition" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="programming" label="programming" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="topcoder" label="topcoder" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
As I&apos;m writing this, twenty people are watching their peers write code.  They aren&apos;t looking over anyone&apos;s shoulders, or doing peer programming - they&apos;re watching mirrors of screens at the TopCoder Open, seeing exactly how competitors work their way through algorithm problems in C++, Java, and C#.  Is this something we should be doing more of?
</content>
</entry>

<entry>
<title>Writing a book by competition</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/05/writing-a-book-by-competition.html" />
<id>tag:broadcast.oreilly.com,2009://53.36275</id>

<published>2009-05-19T16:17:23Z</published>
<updated>2009-05-19T16:17:23Z</updated>

<summary>I&apos;ve worked on lots of collaborative books before.  Now, I&apos;m starting on something different: a book written by competition. We&apos;re asking TopCoder participants to create a book about how to participate in TopCoder contests, the TopCoder Cookbook.  Cookbooks are a natural fit for books with multiple authors, as each recipe can be fairly self-contained, sequence is less critical, and there&apos;s room for a wide range of subjects and levels related to a given topic. </summary>
<author>
<name>Simon St. Laurent</name>
<uri>http://simonstl.com/</uri>
</author>

<category term="competition" label="competition" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="cookbook" label="cookbook" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="topcoder" label="topcoder" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
I&apos;ve worked on lots of collaborative books before.  Now, I&apos;m starting on something different: a book written by competition. We&apos;re asking TopCoder participants to create a book about how to participate in TopCoder contests, the TopCoder Cookbook.  Cookbooks are a natural fit for books with multiple authors, as each recipe can be fairly self-contained, sequence is less critical, and there&apos;s room for a wide range of subjects and levels related to a given topic. 
</content>
</entry>

<entry>
<title>Personalizing the Learning Conversation</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/05/immediacy-and-teaching-for-diy.html" />
<id>tag:broadcast.oreilly.com,2009://53.36123</id>

<published>2009-05-05T14:25:27Z</published>
<updated>2009-05-05T14:25:27Z</updated>

<summary>Twenty years of change are shifting technology from top-down broadcast-model documentation and training to a more conversational approach that shrinks the social distance between teacher and learner, personalizing our experience.</summary>
<author>
<name>Simon St. Laurent</name>
<uri>http://simonstl.com/</uri>
</author>

<category term="book" label="book" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="exercises" label="exercises" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="mentor" label="mentor" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="publishing" label="publishing" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="rails" label="rails" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="railsconf" label="railsconf" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="screencast" label="screencast" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="teaching" label="teaching" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="tutor" label="tutor" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
Twenty years of change are shifting technology from top-down broadcast-model documentation and training to a more conversational approach that shrinks the social distance between teacher and learner, personalizing our experience.
</content>
</entry>

<entry>
<title>Dreaming of Rails as the Next Microsoft Access</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/05/dreaming-of-rails-as-the-next.html" />
<id>tag:broadcast.oreilly.com,2009://53.36119</id>

<published>2009-05-05T02:39:23Z</published>
<updated>2009-05-05T02:39:23Z</updated>

<summary>Rails?  Microsoft Access?  Aren&apos;t those from different planets?  Well, they may have different origins, but their similarities give me hope.</summary>
<author>
<name>Simon St. Laurent</name>
<uri>http://simonstl.com/</uri>
</author>

<category term="access" label="access" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="database" label="database" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="microsoft" label="microsoft" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="rails" label="rails" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="ruby" label="ruby" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="spreadsheets" label="spreadsheets" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
Rails?  Microsoft Access?  Aren&apos;t those from different planets?  Well, they may have different origins, but their similarities give me hope.
</content>
</entry>

<entry>
<title>Choosing your application&apos;s version of Rails</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/03/choosing-your-applications-ver.html" />
<id>tag:broadcast.oreilly.com,2009://53.35726</id>

<published>2009-03-28T17:37:15Z</published>
<updated>2009-03-28T17:37:15Z</updated>

<summary>Rails updates versions frequently.  There are a few different ways to make sure your application is running the version of Rails you think it should be, and to make sure you can run it under the version it expects.</summary>
<author>
<name>Simon St. Laurent</name>
<uri>http://simonstl.com/</uri>
</author>

<category term="rails" label="rails" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
Rails updates versions frequently.  There are a few different ways to make sure your application is running the version of Rails you think it should be, and to make sure you can run it under the version it expects.
</content>
</entry>

<entry>
<title>Lessons from Saturn&apos;s failure</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/02/web-20-lessons-from-saturns-fa.html" />
<id>tag:broadcast.oreilly.com,2009://53.35358</id>

<published>2009-02-18T17:13:33Z</published>
<updated>2009-02-18T17:13:33Z</updated>

<summary>GM&apos;s putting an end to its Saturn line shines a light on the challenge of building &quot;a different kind of company&quot; inside the &quot;usual kind of company&quot;, at a time when a lot of web companies are aiming to be different.</summary>
<author>
<name>Simon St. Laurent</name>
<uri>http://simonstl.com/</uri>
</author>

<category term="community" label="community" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="saturn" label="Saturn" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
GM&apos;s putting an end to its Saturn line shines a light on the challenge of building &quot;a different kind of company&quot; inside the &quot;usual kind of company&quot;, at a time when a lot of web companies are aiming to be different.
</content>
</entry>

<entry>
<title>ISBN adventures</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/02/isbn-adventures.html" />
<id>tag:broadcast.oreilly.com,2009://53.35334</id>

<published>2009-02-16T15:50:50Z</published>
<updated>2009-02-16T15:50:50Z</updated>

<summary>For most people, ISBNs are random noise on the backs of books, helpful mostly for barcode scanning at the register.  For publishing folk, ISBNs can actually be memorable, magic keys for jumping from one system to the next.  Of course, there are now two different flavors of ISBN, the obsolete (I prefer &apos;classic&apos;) variety with 10 digits, and the new version with 13 digits.  Working with two sets of magic keys can be complicating.</summary>
<author>
<name>Simon St. Laurent</name>
<uri>http://simonstl.com/</uri>
</author>

<category term="isbn" label="isbn" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="ruby" label="ruby" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
For most people, ISBNs are random noise on the backs of books, helpful mostly for barcode scanning at the register.  For publishing folk, ISBNs can actually be memorable, magic keys for jumping from one system to the next.  Of course, there are now two different flavors of ISBN, the obsolete (I prefer &apos;classic&apos;) variety with 10 digits, and the new version with 13 digits.  Working with two sets of magic keys can be complicating.
</content>
</entry>

<entry>
<title>Learning like teens</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/02/learning-like-teens.html" />
<id>tag:broadcast.oreilly.com,2009://53.35310</id>

<published>2009-02-13T16:37:08Z</published>
<updated>2009-02-13T16:37:08Z</updated>

<summary>The way I learned computers back in the 1980s doesn&apos;t seem that different a path from the way teens are learning now - but both seem very different from the way that adults traditionally learn.  Is there a way to improve adult learning by encouraging teen practices?</summary>
<author>
<name>Simon St. Laurent</name>
<uri>http://simonstl.com/</uri>
</author>

<category term="apprentice" label="apprentice" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="learning" label="learning" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="teen" label="teen" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="toc" label="TOC" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
The way I learned computers back in the 1980s doesn&apos;t seem that different a path from the way teens are learning now - but both seem very different from the way that adults traditionally learn.  Is there a way to improve adult learning by encouraging teen practices?
</content>
</entry>

<entry>
<title>Reviving the Labs - &quot;It&apos;s alive....&quot;</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/02/reviving-the-labs---its-alive.html" />
<id>tag:broadcast.oreilly.com,2009://53.35266</id>

<published>2009-02-10T18:30:25Z</published>
<updated>2009-02-10T18:30:25Z</updated>

<summary>After a long hibernation, O&apos;Reilly Labs has returned, with a mix of software and code that should excite casual ebook readers as well as dedicated publishing technologists.</summary>
<author>
<name>Simon St. Laurent</name>
<uri>http://simonstl.com/</uri>
</author>

<category term="docbook" label="DocBook" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="ebook" label="ebook" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="epub" label="epub" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="labs" label="labs" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="metadata" label="metadata" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="rdf" label="RDF" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="xsl" label="xsl" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="xslt" label="xslt" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
After a long hibernation, O&apos;Reilly Labs has returned, with a mix of software and code that should excite casual ebook readers as well as dedicated publishing technologists.
</content>
</entry>

<entry>
<title>Heroku moves forward and sideways</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/01/heroku-moves-forward-and-sidew.html" />
<id>tag:broadcast.oreilly.com,2009://53.35030</id>

<published>2009-01-17T16:05:09Z</published>
<updated>2009-01-17T16:05:09Z</updated>

<summary>I&apos;ve had a lot of positive feedback from readers for including Heroku in Learning Rails. Its web-based interface is the easiest way I know to get started with Rails programming without getting trapped in installation challenges. They&apos;re changing gears a...</summary>
<author>
<name>Simon St. Laurent</name>
<uri>http://simonstl.com/</uri>
</author>

<category term="deploy" label="deploy" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="heroku" label="heroku" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="passenger" label="passenger" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="rails" label="rails" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
I&apos;ve had a lot of positive feedback from readers for including Heroku in Learning Rails. Its web-based interface is the easiest way I know to get started with Rails programming without getting trapped in installation challenges. They&apos;re changing gears a...
</content>
</entry>

<entry>
<title>Practice</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/01/practice.html" />
<id>tag:broadcast.oreilly.com,2009://53.34816</id>

<published>2009-01-01T15:44:49Z</published>
<updated>2009-01-01T15:44:49Z</updated>

<summary>My New Year&apos;s Resolution for this year is simple: practice.  You don&apos;t have to achieve (or even aim for) total mastery for the practice to be worthwhile.</summary>
<author>
<name>Simon St. Laurent</name>
<uri>http://simonstl.com/</uri>
</author>

<category term="java" label="java" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="outlier" label="outlier" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="practice" label="practice" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="programming" label="programming" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="rails" label="rails" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="ruby" label="ruby" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
My New Year&apos;s Resolution for this year is simple: practice.  You don&apos;t have to achieve (or even aim for) total mastery for the practice to be worthwhile.
</content>
</entry>

</feed> 
