Lake Tahoe // April 29th, 2008
One of the few photos (actually, there are 2 or 3 stitched together here) of I mine I consider a favorite. From a weekend trip to Lake Tahoe a few weeks back.
Movie Theaters Starting to Listen // October 25th, 2007
Studio Briefing reports details on two movie theater chains (in the mid-west, no less) that are making efforts to increase audience size.
Kerasotes Theaters in starting to ban children after 8:30 if they are not accompanied by their parents. Nothing worse than having to watch a movie in a theater that is the dumping ground of shitty parents not wanting to deal with their kids. These theaters are called AMC Theaters.
Marcus Theatres is providing baby-sitting services as well as offering alcoholic drinks and entrees in their adult-only theaters. I wouldn’t care either way about being able to drink during a movie, but I think that is the only way to ban people under 21 from a commercial operation.
Now theaters just need to remove the talkative, annoying, and or cell phone viewing patrons from auditoriums and I might attend more movies. The only sure-fire way to get me to see more movies: reserved seating, start the movie on-time, no commercials or advertisements at all, and wider aisles. Dream improvements: private box seats, sofa recliners with built-in speakers, personal concession services. You know, to mimic the experience you already have at home.
- Theaters Begin Barring Children [IMDB]
Review: PHP Web 2.0 Mashup Projects // October 22nd, 2007
[Note: Once again, I received a book from Packt Publishing to review for my blog. This time I review a copy of PHP Web 2.0 Mashup Projects. The following is my as honest and objective as possible review.]
In the past couple of years, mashups have become the “new thing” when it comes to web development. Not as over-hyped as AJAX and actually useful, mashups take data from multiple sources (usually web sites through their application programming interface–API) and output the merged data into a single distinct application. Not well experienced with accessing API’s and web services, I decided to create my own mashups involving services I currently use as part of moving my web space from just blog to more of a personal/professional site. Having the desire to work with mashups is a big reason I decided to review PHP Web 2.0 Mashup Projects from Packt Publishing for my blog.
Diving right in this book is aimed at knowledgeable PHP developers familiar with HTML and CSS basics. I would say that the reader should have intermediate PHP skills to be able to understand and follow the example code and application flow of accessing API data.
What I like about this book is that it takes the time needed to explain the various formats, protocols, and web services for accessing data via API’s. As a way to help convey the power, flexibility, and ease of creating mashups, the author provides 5 different mashup project examples. Those projects are: using the Internet UPC database API to find products on Amazon. The second is to create your own search engine with Yahoo and Microsoft Live Search API’s. Third, create your own video jukebox, mashing up YouTube and Last.fm data. The fourth project involves receiving traffic incident updates via SMS. The final project deals with using API’s from Flickr and Google Maps to show photographs based on map location. Each example is thorough, from the overview to instruction on using various methods and protocols to actual coding. I was not very familiar with most of these methods but with the help of the examples I was able gain a better understanding of the technologies and have now even experimented in creating my own mashups with Twitter and Flickr.
I can’t imagine that there is any doubt about the importance of mashups in the future of the web. The idea behind mashups, API’s, and opening up of data is not a trend but a positive shift in thinking of dealing with data. To be viable, web companies now need to offer API, not because it is cool, but because the competition will. This book mentions two companies, MapQuest and Barnes & Noble, that did not and are nearly no longer relevant. And like companies needing to provide access to data and services, developers need to be experienced in dealing with services as well to remain viable. For web developers, in particular front-end developers with below expert level PHP skills (like myself), this book can be a great resource to learning about API’s and web services.
Review: CodeIgniter for Rapid PHP Application Development // September 23rd, 2007
[Note: I recently had the pleasure of receiving a sample copy of CodeIgniter for Rapid PHP Application Development from Packt Publishing to review for my blog. The following is my as honest and objective as possible review.]
Several months ago I mentioned that I had found a new open-source PHP web application framework, CodeIgniter (CI). I used CI to build a light-weight CMS for the administration of a jewelry web site I created for a client. By using CI I was able to complete the construction in a few days rather than weeks. Since that time I have used CI for a variety of personal projects I constructed to gain a better understanding of CI, PHP, application design, and web services.
Had I known about any books providing more details about CI, I most certainly would have purchased one. But I was unaware of any and thus needed to learn as much as I could about CI on my own. So I was glad to receive what is probably one of the first books to cover Code Igniter, CodeIgniter for Rapid PHP Application Development from Packt Publishing which provides plenty of information to get one started in developing CI applications.
To be honest, I had, to my recollection, never heard of Packt Publishing before so I was slightly concerned about the exact level of CodeIgniter expertise presented in this book. But those concerns subsided when I noticed that CI creator Rick Ellis was one of the book’s reviewers, along with Derek Allard and employee of Rick Ellis’ company Ellis Lab. I doubt either would let bad code or bad coding practices to reach publication.
One thing I liked about this book from the start was the author’s writing and the text readability. I have read quite a few technical books in the past few years and many authors go overboard with technical jargon or fake a vocabulary straight from a thesaurus in attempts to either up word count or merely for inflation of ego. David Upton does neither, leaving the book to stand on its own and be a relatively thin at 244 total pages. The text reads more like Upton is teaching you on a person-to-person bassis rather than other books that seem to instruct like a lecture or textbook.
One the back cover of the book, it is accurately stated:
this book explains how to work with CodeIgniter in a clear logical way. It is not a detailed guide to the syntax of CodeIgniter, but makes an ideal complement to existing online CodeIgniter user guide, helping you grasp the bigger picture and bringing together many ideas to get your application development started as smoothly as possible
This book won’t teach you the granular details of CI or how to build the next great app with a few key-strokes. And this book does present a lot of information that is available in the free CI user guide. You may ask, “Then why bother with this book?” Because this book builds upon that information not only to showcase the power of CI, but also provide a better understanding of how to build better applications with CI. Another reason to check out this book is that Upton also provides examples with the afore mentioned readability that allow for a quicker grasp of concepts than the user guide. And in a couple instances Upton also takes time to compare typical PHP code with its CI counterpart. If you’re not swayed by the simplicity of connecting to and querying your database in a few lines of code within CI, I don’t think anything will get you to move to CodeIgniter or MVC coding.
Even though I have been using CodeIgniter for several months now, this book still presented some useful information and provided a better understanding of the CI framework. Some of the things I picked up from reading this book were testing code (unit tests and benchmarking) and a better grasp on the language class. But it’s not all a love fest with Upton and CI, he does keep it objective and reminds you that CI is not perfect, and lets you know what aspects of CI he does have issues with (one of which is one I too have an issue with — the validation class).
As I said before, you won’t get the finer details of CI. But if you’re at that point with CI already, then this book isn’t for you anyway. Again, right on the back cover it is accurately stated, “This book is for developers who are new to CodeIgniter. Basic skills in PHP and MySQL are required, but only rudimentary object-oriented knowledge is required.” If that is you, then you should consider this book to speed up the learning process with CI.
The book does seem to be a bit steep in price at $35 US for 244 pages, especially if you consider the user guide and forums. However, what I learned about CodeIgniter these past few months occurred after wading through literally hundreds of useless forum and blog posts and spending hours going through my own trial and error of coding to figure things out. Right now, I have a hard time deciding whether or not I would pay $35 for this book since I am already familiar with CodeIgniter, but if I had to go back to when I first started learning about CI, then it would be a no-brainer to buy.