- Paperback: 500 pages
- Publisher: Apress; 1st ed. edition (31 Oct. 2012)
- Language: English
- ISBN-10: 1430241640
- ISBN-13: 978-1430241645
- Product Dimensions: 19 x 2.9 x 23.5 cm
- Average Customer Review: 3.0 out of 5 stars See all reviews (2 customer reviews)
Amazon Bestsellers Rank:
1,520,429 in Books (See Top 100 in Books)
- #2648 in Books > Computers & Internet > Computer Science > Programming > Software Design, Testing & Engineering > Software Architecture
- #2684 in Books > Computers & Internet > Computer Science > Programming > Software Design, Testing & Engineering > Functional Programming
- #4242 in Books > Computers & Internet > Software & Graphics > Software Design & Development
- See Complete Table of Contents
Pro PHP MVC (Professional Apress) (Expert's Voice in Open Source) Paperback – 31 Oct 2012
|New from||Used from|
- Choose from over 13,000 locations across the UK
- Prime members get unlimited deliveries at no additional cost
- Find your preferred location and add it to your address book
- Dispatch to this address when you check out
Customers who bought this item also bought
What other items do customers buy after viewing this item?
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
If you are a seller for this product, would you like to suggest updates through seller support?
About the Author
A bio is not available for this author.
Top Customer Reviews
Most Helpful Customer Reviews on Amazon.com (beta) (May include reviews from Early Reviewer Rewards Program)
In short: not really.
The book's problem is that it drills too far down into topics, complicating them to the point of incomprehensibility, without explaining exactly WHAT we're trying to do, or WHY we need to complicate things in such a way. Would it be so difficult to explain at the beginning of the book what the overall picture is going to look like before we have thousands of lines of code thrown at us? A couple pages detailing how our configuration, caching, registry, routing, template, database, and model classes will be working together to go from a request to an actual view--that doesn't seem like it's asking for much. And yet here I am, struggling to understand how everything links together. Am I really expected to flip back five chapters and skim 1000 lines of code that I barely understood when I read them two days ago to find how one thing links to the other? Such a structure is unforgiving, to say the least.
I've read plenty of PHP/OOP books before coming to this one. I started out with PHP and MySQL Web Development (4th Edition) for the basics, then PHP Objects, Patterns and Practice (Expert's Voice in Open Source) and Head First Design Patterns for OOP and design patterns. I'm about to start PHP Object-Oriented Solutions. Suffice it to say that, while not an "expert" on PHP/OOP/design patterns by any stretch of the imagination, I'm at least starting to understand how everything is supposed to link together. At least, I thought I did, until this book. Now I'm more confused than ever.
I might skim this book again in the future to see if it makes more sense on repeated readings, but for now, I'm just going to shelve it and head back to the Enterprise Patterns chapter of "PHP Objects, Patterns, and Practice." It might not give me the code for a complete framework, but it's at least readable.
What you will find in this book can be learnt (the hard way) from reading source codes of professional open source project,but this book brings all what you need in an easy organized way for learning purposes, so you will get what other people has struggled learning.
It's very unclear on what it wants you to do and therefore seems like the author expects you to read minds. I tried three times to follow the book and finally gave up on it. When finished ca. 150 - 170 pages you feel like a stupid misfit that can't understand or do anything and the book never tells you if you should f.ex. create a file called this or that, and you end up not knowing how your ever going to get through this book. The code examples are therefore very unexplainatory. I advice every intermediate programmer against buying this book. It will not help you on your way on learning anything useful as it begins on the wrong end of a framework. I would demand a refund if I hadn't tried for so long to get through it. This book needs a complete re-write.