From 4b6c0e31385f5f27a151088c0a2b614495c4e589 Mon Sep 17 00:00:00 2001 From: Paul Duncan Date: Thu, 14 Oct 2021 12:47:50 -0400 Subject: initial commit, including theme --- content/posts/2004-03-23-pickaxe-ii-feedback.html | 57 +++++++++++++++++++++++ 1 file changed, 57 insertions(+) create mode 100644 content/posts/2004-03-23-pickaxe-ii-feedback.html (limited to 'content/posts/2004-03-23-pickaxe-ii-feedback.html') diff --git a/content/posts/2004-03-23-pickaxe-ii-feedback.html b/content/posts/2004-03-23-pickaxe-ii-feedback.html new file mode 100644 index 0000000..1df7241 --- /dev/null +++ b/content/posts/2004-03-23-pickaxe-ii-feedback.html @@ -0,0 +1,57 @@ +--- +date: "2004-03-23T14:11:00Z" +title: PickAxe II Feedback +--- + +

+Dave Thomas (pragdave) is +soliciting feedback for a second edition of Programming Ruby (aka the "PickAxe"). Here's what he's +saying on the ruby-talk mailing +list: +

+ +
+

+So, this is what I'm thinking. Rather than document all the methods in +all the lib/ and ext/ classes and modules, I'd like to have a one-page +summary for each. Each page would contain a synopsis of the function of +the library, along with a small number of samples of use. The idea is +that you can read through this to find libraries that would be useful, +and then consult the RDoc for details. Think of it as a kind of +exhaustive library cookbook. I've posted sample pages at + +

+   http://www.pragmaticprogrammer.com/extracts/sl.pdf +

+ +

+(These are rough, and contain typesetting problems and other errors---I +just wanted to give folks a feel for what I was talking about). +

+ +

+So, here's the question: is this the way to go? Are folks happy seeing +this kind of synoptic information in the book, and then referring to +the online or local documentation for the details? (Don't worry about +the built-in stuff: I'm keeping the existing format for all of that, so +you'll still have the complete method listing for String, Array, and +friends). +

+
+ +

+The full message (and thread) is available here. +

+ +

+Update: Apparently the ruby-talk archive code is a bit +behind; the link is correct, but the message isn't archived yet. At the +moment, there's nothing on the ruby-talk archive page dated past +March 19th. +

+ -- cgit v1.2.3