Editorial-Reviews-of-the-Fired-up-Practical Experience-from-readers


Barely a week after this book went live on http://amazon.com, some dare software programmers caught a hold of the book. Upon a curly online search, I stumbled upon their raw reactions. This is the unabridged, or unedited form of their comments. I hope someone finds this useful.

3 thoughts on “Handsonlabs in Php/MySql: The fired up practical Experience in Php/MySql (Volume 1)”

  1. Danilo Gurovich “dan@gurovich.com” June 22, 2013 at 1:51 am

This book would totally be 5 stars if the source code was there. It really lays out how to work with Django and understand best practices, but if you’re a “code-along-with-the-book” kind of person, you’re going to be SEVERELY disappointed since there’s no source code to check against the book, not anywhere.This lack of source code would be excusable if this was a fresh title and there seemed to be an effort to get the source code out, but after searching the blogs and finding an excuse by the author over a year back saying “I have a day job”, well that’s just inexcusable. I’d almost give it two stars for the excuse, but the content of the book itself is very good, except for the thirty or so references to “getting to source code from the Apress site”. Shame on Apress.This book sits on my shelf as a reference for best practices and a collection of white papers for extending my projects, but I would consider this a third choice. If you’re already comfortable with django and “get” everything that’s going on, go for this book. If you’re still a little “noob-ish” on the topic, move on.


  1. Hugh D. Brown “HDB” June 22, 2013 at 1:51 am

I resisted reading the first edition because it came out just shortly before Django 1.0. As a result, the code samples were not fully usable with the latest Django codebase.The second edition does not suffer from this problem. The code matches development version 1.1. It also has a number of helpful additions: material on current version control (git, mercurial, and subversion), pip (for installing packages), virtualenv (for isolating different development environments), fabric (for repeatable releases to servers), and unit testing.The text covers the development of two projects: a CMS and a code-sharing site. It has excellent examples of managers (a topic I have not seen covered in other Django books), templatetags, installable packages (markdown, comments, akismet for anti-spamming, pygments for color code, tinymce for rich text-editing, pydelicious, registration), and native packages (RSS feeds, flatpages, auth), plus all the usual topics: urls, models, views, forms, and templates. The text is very strong on using generic views.The writing is excellent and flows logically. It’s a pleasure to read.


  1. C. Young “C. Young” June 22, 2013 at 1:51 am

I like the Django framework a lot, and really wanted to like this book, but I’m afraid it was pushed to market long before it was ready.There are several cases in the book where I feel the author introduces something, but leaves off pertinent information required to override Django defaults and get what he suggested to work (e.g. using the numerical representation for months in a URL rather than the three-digit representation).Also, there are many places in the book where the author is describing code, but doesn’t state very clearly where the code should go.Finally, the author refers to the book’s accompanying source code, but that source code doesn’t exist. The publisher told me a month ago that they’ve been in contact with the author, and that the source code will be available “shortly,” but it is still unavailable. How many months has the book been out?On the plus side, I think the author’s projects are useful, and with the exception of his use of Markdown for submitting blog entries (in my opinion, he should have showed the use of TinyMCE there as well), well thought out. I also think the author does a good job of introducing the reader to a wide range of Django knowledge.I’m taking one star away for the lack of clarity in several areas, and one away for the missing source code. If the publisher had fixed the ambiguities, missing information, and had the source code available prior to release, this could easily have been a five-star book for learning Django.


  1. Oluwatobi Owoeye ( Author)  July 14, 2013 at 10:58 pm


Funny as it may seem, I never knew Django existed until I read these comments.Funny how giving out what you know can give one much more.

The source code for the book is now available on this link:  Source Codes .
Several titles on Handsonlabs in JAVA, Handsonlabs in php frameworks, Handsonlabs in ASP.NET, ETC. are on their way, therefore
please to stay updated on the issues of this book, kindly bookmark the above url especially the facebook page:
Handsonlabs-Software-Academy on facebook
I have noted your observations and I am working on them right away. Subsequent editions will be improved.
Thank you all for your comments and God bless you all abundantly.