Ahh, I'm actually thinking of a book like that for a typical 10-page web-based application, using CGI::Prototype, Template::Toolkit, and Class::DBI. Well, not exactly thinking of it... more like being encouraged strongly by my clients to write such a book to give a broader overview than all the details that are out there so far.

The problem with books is that unless your book is wildly successful, you end up getting paid roughly minimum wage to write it. And no, I'm not kidding. I could make more money flinging hamburgers than writing some of the books I've written. {grin}

So, the purpose of writing a book is to act as a credential, or to be done as a labor of love, or to support a class as a textbook. I already spend time here (and everywhere else) as a labor of love, so I'm sort of labored out there. And I really don't need another credential.

The third option is intriguing, but I'm not sure what the classroom sales would be of a course that covers the "small web app" market. The problem isn't that there aren't a lot of people doing it: there are! The problem is getting 10 to 20 of them in the same room for a week. Ugh.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.