This msg for Chad F. or anyone who fits the subject line.
I bought the Recipes book and really like the way it has been
progressing. There is one subject I’d like to see explored in detail.
Having come from Assembly and C background I find that a ‘must have’
tool in your collection is the debugger.
I find debugging a Rails App the most thorny issue inversely
proportional to its simplicity and beauty. I have tried breakpointer,
mr.guid, arachnoruby etc but they are either inadequate or slow or
both. What do you do when you set a breakpoint in your code and it
doesn’t hit and there are no messages in the log or in the browser.
What is going on in the framework? How can I learn the framework by
actually tracing through the code vs. simply reading it? These are
some of the issues I grapple with in daily development of Rails. Don’t
get me wrong, while for the most part Rails gives very meaningful
messages which makes development go smoothly, the rare occasions when
I hit one of the ‘bugs of the strange kind’ it can take me days to
figure it out!
I’d like to know what the methods/techniques core developers and other
ruby/rails gurus use and how they are able to be so productive…not
withstanding the fact that they by definition write better code than I
It is incomprehensible to my average brain when I hear that DHH
wrote basecamp + rails in 6 weeks or so (rails first rails video) -or-
that Gosling cobbled up Java over a weekend -or- that Jim Fulton
wrote zope on a plane ride home
-http://www.plope.com/Books/2_7Edition/IntroducingZope.stx and other
There seems to be precious little written on the subject in the wiki.
Thanks for the opportunity to vent,