So I wrote a book (See sig, below.)
David A. Black ([email protected])
Ruby Power and Light, LLC (http://www.rubypowerandlight.com)
“Ruby for Rails” PDF now on sale! http://www.manning.com/black
Paper version coming in early May!
Thanks for your book, David.
I am not a typical technical geek. I come from management and sales, and
started with developement from the user angle, I understood the
customers, and quickly become in charge of translating the users demands
to the technical guys.
I have been working with a 4GL tool (eDeveloper Magic) for 12 years, and
a few years ago I decided to learn Java to develop a Web client to our
software application (Oracle-based). I bought books (Eckel etc), read
them and we started programming. But too much overhead (Jakarta,
Velocity, SPring, ANT, Struts, Java WARS, XLM-configuration, etc)
compared to my beloved tool eDeveloper Magic.
And then came Rails. I found out about it a few months ago, and got
really excited. It has a bit of eDev Magic approach to it. And I bought
books (Pickaxe, Agile Dev. w Rails) and started.
Last week I bought your book.
And I give your book the best marks! Superb explanation of objects and
classes. For the first time I actually think I understand it!! And the
chapter on modules and mixing a module with a class is crystal clear. I
just read it and understood. ItÂ´s like reading a work of philosophy
(which I also love!).
From my angle I want to understand what I do, I want to connect “my
world”, the customersÂ´ world to what goes on within an application. Just
repeating what someone else shows you and doing it without knowing what
you do is what I call “Parrot” knowledge. When something goes wrong you
donÂ´t understand why. I tell my customers every day not to settle for
parrot knowledge of my application: “try to understand why to do this,
or why to do that, then you donÂ´t have to call me when you get stuck”.
So I want to learn why does Rails do this or that, and thatÂ´s where your
book stands out in explaining! It has been a real joy to read, and how
often can you say that about a book on computer languages.