Many of the books that I read that are typically referrals from a web page or cited in other book reviews. I can’t remember exactly how I was referred to Coders At Work, but it has been the most fortunate of happenings. I suspect that what drew me to the book is the interview with Joe Armstrong, because I’m currently obsessed with learning Erlang as well as its development.
At long last another book dedicated to wxPython application development is finally published.
The author is an active member of the wxPython users list and quite often posts answers to problems people are having with wxPython. He is more than qualified to write a book on the subject. Additionally, he has written Editra; a well-known editor which uses the wxPython framework.
wxPython has matured over the years, the documentation has also gotten better and a lot of experienced users can be found on the wxPython users list. That said users still stumble over various issues making their programs work. Books like this one will quickly find their way to the hands of wxPython users in need.
I’m very disappointed in this book, primarily because it is a repeat of so much other material. I’m also not happy that the publisher approved of the contents of this book, when they have published many books on the same introductory material that this book includes. If you’re going to publish an intermediate or advanced book, state the prerequisites and get on with the “real world instrumentation”.
“Erlang and OTP in Action” is not a repeat of the existing introductory books on the Erlang language, although there is a brief introduction to the language in Chapter 2. This book continues where other books leave off. If you are just learning Erlang, this book is probably not the best place to start, however it is an excellent reference for more advanced topics
If you're a Perl programmer, or you need to work with some legacy logic and want to pull it into an modern web application framework then Catalyst is likely your best choice. This book is your best choice to learn all about it and more.
What first attracted me to this book is its coverage of several languages that I know little or nothing about. For reasons mostly due to chance, I’ve been exposed to only a handful of well-known programming languages during my professional career. Recently, I’ve been quite intrigued by Erlang’s concurrency model and robustness even though there is no place for it in my day-day tasks. Having the opportunity to read about Erlang being evaluated against other languages was just what I wanted. So, I took the red pill and found out just how deep the rabbit hole goes.
Django 1.1 Testing and Debugging covers all the essential tools for testing web applications, specifically Django apps. The topics covered are sometimes specific to Django but many are applicable to other web frameworks or straight Python code. Weighing in at about 400 pages, the book includes a balanced mix of discussion, code examples screenshots and stack traces. The book is targeted at web developers familiar with Python, Django and relational databases who are eager to learn more about testing and debugging. The author's writing style is relaxed yet not full of the smarmy jokes found in some technical books. She does a find job of explaining the concepts covered in the book. It should be considered required reading for perfectionists with deadlines.
The authors of this book are also the creators of the Processing language and environment. Processing is “an open source programming environment for teaching computational design and sketching interactive media”.
Vernon Cedar, the author of The Quick Python Book, First Edition, has written a well rounded introduction and reference manual to the Python scripting language. My previous experience with coding was writing C at Nortel in the 90's. I hadn't done much coding since, but I always had the bug to get back into it. My friend suggested that I read and review this book as my introduction to Python.
The Quick Python Book is a good and short introduction/overview of Python 3. The book covers a lot of ground,
but because it is relatively slim (about 300 pages or so) it is no wonder that in many places the author instructs
the reader to look for more information from online sources. Additionally some more challenging topics (like decorators)
are not explained in enough detail, which leaves the reader wondering if those part should have been left out of the book
completely (or explained better).