The book is solid, well written and covers the most important topics that people need to think about when starting off with PHP. It is one of the few PHP book on the market that you can pass on to your trainees/junior developers without having to "unteach" them half of the taught bad practices afterwards. This is a great achievement in my mind and I'd definitely recommend checking it out and passing it on to your trainees and 'junior developers' ... maybe read it first yourself and rip out a few pages in chapter 4.

His "long version" gets into a more complete list of his thoughts on each of the individual chapters (including "object oriented programming", "APIs", "design patterns" and "security"). Overall, he found the book good, but pointed out a few areas where it was lacking. You can find more detail about the book here (or on Amazon here)

The review includes an overall assessment of the book, a detailed description of how the chapters are laid out and some of the complaints he had about the book's contents - a lack of code examples in some places, demos/screenshots pointing out what the framework can really do and the inclusion of some deprecated methods.

Overall, the book is well organized, focused and will be helpful on it's purpose. I felt it's capable to teach Kohana to a new guy, in a smooth way. Yes, there have some printing mistakes, old (because they are changed in new version) function use and some other minor issues, but seems ignorable to me. I'd recommend it for Kohana beginners.

The book was written explicitly to help you becoming a better PHP programmer and is totally awesome. It not only covers advanced PHP coding topics such as object-oriented programming and design patterns, but also periphery topics that are just as important, such as security, performance profiling, and deployment. If you're ready to hang up your novice hat for good and become a professional-level PHP developer, this book is for you.

He goes through and highlights some of the content in the book, chapters covering relational databases, web services, security topics, caching, automated testing, PEAR/PECL....just to name a few.

Using the Slashdot scale of book ratings, where 1 is fit for lining cages and 10 is destined to be a class, I give PHP Master: Write Cutting-Edge Code a very solid 8.5. The content will grow with you and the book is not something you'll read in a weekend and then donate to the library because you have no need for it.

Savvy PHP web developers can now keep ahead of the game and ensure that their PHP code is safe, secure, and well-structured for the future with the latest release from SitePoint: "PHP Master: Write Cutting-edge Code" by Lorna Mitchell, Davey Shafik, and Matthew Turland.

The book covers a wide range of topics (somewhat replacing SitePoint's usual "anthology" type of book) including:

• An introduction to OOP
• Working with databases
• Creating and working with APIs
• Design patterns
• Security
• Automated testing

As part of a special offer, you can pick up your print+ebook bundle for the price of just the book, about $40 USD. If you'd like a sample before purchasing, they've posted three sample chapters.

Episode 129 of The SitePoint Podcast is now available! This week our regular interview host Louis Simoneau (@rssaddict) interviews Lorna Mitchell (@Lornajane) one of a team of 3 co-authors working on an upcoming release for SitePoint, an advanced book on PHP.

You can either listen to this latest episode using the in-page player or by downloading the mp3 directly. Of course, you can always subscribe to their podcast feed and get this and other new shows as they're released.

In this review I focus on the changes between the editions of the book, which are brief and objective, since the core of the work remains the same and with the same quality. [...] In sum, I recommend reading this book to those looking forward to improve their skills in PHP, or intend to create new frameworks. To put it simply, a good book to read, and with new tricks to learn.

He (the reviewer, Alexandre Altair de Melo) briefly looks at these differences between the versions, with the largest being in Chapter 15 - the building of a sample application to apply all of the theory learned in the rest of the book. You can find more information about the book on Packt's website here.

I got mail yesterday from a former student of a friend of mine who has just been told that he has to teach an "Intro to Software Engineering" class this fall to a bunch of third-year undergraduates. He's not an SE guy-his background is operating systems-so he asked me what he should read to get one step ahead of his future students. As regular readers will know, I don't think much of most traditional software engineering books: I've never seen most of what's in them in the real world, and most of what I've needed to know hasn't been in them.

Included in his books of recommended reading are things like:

• Making Software (of which he's an author)
• Karl Fogel's Producing Open Source Software
• Working Effectively with Legacy Code (from Michael Feathers)
• The Architecture of Open Source Applications

Take a look at the full post for the rest of his list and a bit about why he chose each.

By the time I finished the book a few months later, it rocked my professional world and I couldn't wait to jump into the community fully and completely. To be clear, Karl's book is about the difficulties and challenges of building a team to build a project, but almost all of it is relevant in the building communities in general...

He goes through some of the topics mentioned in the book and highlights three different themes that stood out to him - Political and Social Structure, Communication and one of the most difficult, Managing Volunteers.

So overall, almost every single idea struck me as both blindingly obvious and often missed. And the single best part about this entire book... about 90% of it applies to any project or technical community. Yes, I don't care if you're working on an Open Source project, an internal project, or a commercial shrink-wrapped application. You can use almost any idea from this book and apply it immediately.

It took me a while to grab myself a copy of Matthew Turland's "Guide to Web Scraping with PHP", but a few weeks ago a copy finally arrived and I had the pleasure of reading it. [...] My overall impression of the book is that it was worth the time and I'm really glad that I bought it. Matthew did a great job explaining all the tools we have at our disposal for writing web scrapers and how to use them.

He talks about the content of a few specific chapters (the HTTP protocol, client libraries you can use and how to prepare documents for parsing) and notes that there's not much bad he can think of about the book:

It is a guide, clear and straight-to-the-point, explaining what tools are there, which one to use and how for writing scrapers and that's exactly what I wanted to know.

personally find the "cookbook" style of books to be the most helpful. They enable me to quickly find answers to the problem "show me how to do something realistic using your tool". Hello World doesn't cut it for the tools I need to use. [...] Like any well-thought-out book, they cover the main components of CakePHP. One of the thing I liked was that you didn't have to necessarily read the book from front-to-back in order to get something from it.

He mentions other positive things about the book - like the chapter on using the command-line tools that come with CakePHP - and one of the negatives (not so much about the book as it is the CakePHP project's choices).