<?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>2009-06-03T22:08:10Z</updated>

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

<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>

<entry>
<title>Installing Instant Rails on Windows</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2008/12/installing-instant-rails-on-wi.html" />
<id>tag:broadcast.oreilly.com,2008://53.34728</id>

<published>2008-12-22T14:16:33Z</published>
<updated>2008-12-22T14:16:33Z</updated>

<summary>Instant Rails is getting old, but it&apos;s still a quick way to install Rails and start coding.  This screencast shows how to download and install Instant Rails, and shows off how it works with a simple example from Chapter 2 of Learning Rails.</summary>
<author>
<name>Simon St. Laurent</name>
<uri>http://simonstl.com/</uri>
</author>

<category term="202" label="2.02" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="apache" label="apache" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="mysql" label="mysql" 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="vista" label="vista" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="windows" label="windows" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
Instant Rails is getting old, but it&apos;s still a quick way to install Rails and start coding.  This screencast shows how to download and install Instant Rails, and shows off how it works with a simple example from Chapter 2 of Learning Rails.
</content>
</entry>

<entry>
<title>Templates Offer Rails New Path to Ubiquity</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2008/12/application-generators-offer-r.html" />
<id>tag:broadcast.oreilly.com,2008://53.34669</id>

<published>2008-12-16T13:42:37Z</published>
<updated>2008-12-16T13:42:37Z</updated>

<summary>Rails application templates, just added in Edge Rails, offer Rails developers the chance to spread their wings and bring Rails to new audiences and new capabilities - and might even help Rails lead the next generation of frameworks.</summary>
<author>
<name>Simon St. Laurent</name>
<uri>http://simonstl.com/</uri>
</author>

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

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
Rails application templates, just added in Edge Rails, offer Rails developers the chance to spread their wings and bring Rails to new audiences and new capabilities - and might even help Rails lead the next generation of frameworks.
</content>
</entry>

<entry>
<title>Stuck Together</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2008/12/stuck-together.html" />
<id>tag:broadcast.oreilly.com,2008://53.34661</id>

<published>2008-12-15T22:24:05Z</published>
<updated>2008-12-15T22:24:05Z</updated>

<summary>Bailouts are an awful thing, an admission of drastic failure.  They&apos;re also a safety valve that can lessen the impact of disaster in a given area on the rest of the system.  In the immediate and short term, we need to recognize that it&apos;s not just a given group whose boat is being bailed - we&apos;re bailing a very large boat that we&apos;re all riding.</summary>
<author>
<name>Simon St. Laurent</name>
<uri>http://simonstl.com/</uri>
</author>

<category term="bailouts" label="bailouts" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="credit" label="credit" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="finance" label="finance" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="networkeffects" label="network effects" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
Bailouts are an awful thing, an admission of drastic failure.  They&apos;re also a safety valve that can lessen the impact of disaster in a given area on the rest of the system.  In the immediate and short term, we need to recognize that it&apos;s not just a given group whose boat is being bailed - we&apos;re bailing a very large boat that we&apos;re all riding.
</content>
</entry>

<entry>
<title>First Steps in Rails (on Heroku)</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2008/12/first-steps-in-rails-on-heroku.html" />
<id>tag:broadcast.oreilly.com,2008://53.34498</id>

<published>2008-12-02T17:26:20Z</published>
<updated>2008-12-02T17:26:20Z</updated>

<summary>If you want to explore Rails, heroku.com offers an easy way to get started, using a web-based interface that neatly hides the complexity of installation and database management.</summary>
<author>
<name>Simon St. Laurent</name>
<uri>http://simonstl.com/</uri>
</author>

<category term="controller" label="controller" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="heroku" label="heroku" 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/">
If you want to explore Rails, heroku.com offers an easy way to get started, using a web-based interface that neatly hides the complexity of installation and database management.
</content>
</entry>

</feed> 