Ooh that's good! Works on several levels and does what it says on the
tin! I vote for "The Hobo Code Guide".

On Dec 29, 6:17 pm, "Andrew Shindyapin" <[email protected]>
wrote:
> Or something like "The Hobo Code Guide" 
> (http://en.wikipedia.org/wiki/Hobo#Hobo_code)
>
> On Mon, Dec 29, 2008 at 1:14 PM, Ian Wood
> <[email protected]>wrote:
>
>
>
> > This is excellent news indeed, I'd be happy to help out in any way
> > that I can.
> > As for the title how about: "Becoming a Hobo" :-)
>
> > On Dec 29, 5:58 pm, Owen <[email protected]> wrote:
> > > Thanks, Tiago, we WILL need it.
>
> > > We also need help for a REAL title. Until we get a brainstorm from
> > > someone we are using the interim designation "The Hobo Primer."
>
> > > -Owen
>
> > > On Dec 29, 10:41 am, Tiago Franco <[email protected]> wrote:
>
> > > > Hi,
>
> > > > Excellent news and many thanks to the supporters.
>
> > > > You may count with my feedback if needed.
>
> > > > TF
>
> > > > On Dec 29, 3:27 pm, Owen <[email protected]> wrote:
>
> > > > > Thanks, James--we'll need you!
>
> > > > > On Dec 29, 10:21 am, James Garlick <[email protected]> wrote:
>
> > > > > > That's great Owen, I'd be happy to provide feedback.
>
> > > > > > On 29 Dec 2008, at 15:11, Owen wrote:
>
> > > > > > > Tom, James & All Dedicated Hoboists,
>
> > > > > > > I received the green light from Ramon Barquin to pursue writing
> > this
> > > > > > > book ASAP.  We are lucky to have Jeffrey Lapides leading this
> > effort.
> > > > > > > Jeff has created a draft outline of goals and chapters that we
> > aare
> > > > > > > reviewing today.
>
> > > > > > > The "draft" intended audiences:
>
> > > > > > >     * The RoR and Hobo novice, especially someone who wants to
> > avoid
> > > > > > > RoR coding
> > > > > > >     * Technology leaders, architects, and evangelists
> > > > > > >     * A Technically savvy manager/designer who wants to develop
> > but
> > > > > > > not code
> > > > > > >     * Advanced RoR developer who wants to go in a different
> > direction
>
> > > > > > > Our goal is to have the first 100 pages by February 1...
>
> > > > > > > Stay tuned for more details.  To make this successful we will
> > need
> > > > > > > input and editorial feedback from all.  How we will do this is
> > yet
> > > > > > > TBD.
>
> > > > > > > Looking  forward to an exciting 2009!
>
> > > > > > > Owen
>
> > > > > > > On Dec 29, 5:31 am, Tom Locke <[email protected]> wrote:
> > > > > > >>> While it would be nice to be able to use Hobo without Rails
> > > > > > >>> experience, it really doesn't seem practical - Hobo *is* Rails,
> > in
> > > > > > >>> many parts. Trying to educate brand-new users about
> > *everything*
> > > > > > >>> seems doomed to repeat much of the Rails docs.
>
> > > > > > >> Yes you would have to repeat a lot, but I'm not sure the word
> > > > > > >> "doomed"
> > > > > > >> is warranted : ) In the world of docs, DRY is not a virtue.
>
> > > > > > >> Although there's a lot in Rails that Hobo people need a thorough
>
> > > > > > >> grasp
> > > > > > >> of, there's also lot that they don't need to know tons about.
> > E.g.
> > > > > > >> routing. Or rather, it's not that you don't need to know about
> > > > > > >> routing, but it becomes an advanced topic rather than an
> > essential
> > > > > > >> one. The order of learning changes.
>
> > > > > > >> The only way to give a seamless learning experience is for a
> > book/
> > > > > > >> course/other on Rails and Hobo together. It is a lot of work
> > though.
>
> > > > > > >> I'm hoping someone else will write that book!
>
> > > > > > >> Tom- Hide quoted text -
>
> > > > > > - Show quoted text -- Hide quoted text -
>
> > > > - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Hobo 
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/hobousers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to