As the third book I am reviewing in a row through the O’Reilly bloggers program I chose one from a series of books I never actually had the chance to read before; pocket reference/guides.
As you might conclude as well from the title this isn’t a book which deals with top to bottom reading style. Such books should be called among developers: small, internet free, fast, more concise and friendlier examples than your usual quick search online.
Or as I would rather call the book
HTML5 – Up and running away from the madness.
Seriously, if one thing this book taught me; and taught me well is the fact that frontend web development is a mess (no surprise there) and will be even more messier in the years to follow. And all this dirt is publicly exposed in the first chapter of the book.
Amusing, captivating, inspiring and motivational – those would be the words I’d use to describe the book for anyone asking.
The book is so well rounded that I couldn’t complain of any of it’s chapters. While I skimmed the chapters: How to pitch an idea and How to stay motivated; I can say that all the other chapters are packed with interesting ideas, side stories and
Another aspect I liked very much in the book was the very precise way the information was collected and referenced. Basically you could take any chapter, look out some reference and expand your knowledge on the given subject. Go further than the book offers, because that is the means of innovation.
There is no Eureka, falling apple or instant success. It’s all years of hard work, and the book is there to higher your morale, make you feel good about the change you can make.
A great book for any person open enough to innovation. That is the single criteria the author deems, the rest is irrelevant because (as to my surprise) the book is not technical.
The Art of Unit Testing: With Examples in .Net by Roy Osherove is a great book I’ve read a couple of weeks ago, and of which I would like to write a few words.
Before we start I should state that I had no previous experience with unit testing, and as such, in some aspects, I might be stating the obvious.
…especially in the context of web frameworks.
If we think about if for a moment, we can all agree that almost every web framework uses the MVC concept, everybody advocates it, but few people actually grasp the true meaning of MVC.
Foremost I would like to explicitly state that this isn’t an article to refute the use of MVC, or to blame people for using MVC. It must be considered an article which elucidates the concept of MVC and how it doesn’t quite fit the context upon it is advertised.
Posted in Discussion
Tagged mvc, php
The other day I’ve found this interestingly controversial submission on reddit and I must admit that after taking a quick look at the code, I ran of for some eye bleach to erase that image from my mind.
While I know that the author had the intention to experiment with the idea of Prototype based inheritance, god forbid something like this goes into a production environment… and trust me, with enough exposure someone will use it.
I’ll gladly share one of my principles with the author:
If you are fighting the language (or framework, library), it means it’s time to ditch it for something else instead of forcing it to work your way… that never turns out well.
Wanting this to not come out as a rant about somebody else’s code (no one likes that), I will instead suggest an implementation that is somehow less obtrusive towards the language, but still an experimentation idea.
Early this week the book HTTP: The Definitive Guide has finally arrived. I’ve put on hold all my side projects and gave it a read, and have written this post to share my opinion about it.
Posted in Books
Tagged cache, http, proxy
Like many other web developers out there I started developing in PHP somewhere around six years ago (it’s already been that long). In a time when PHP 4 was the king, and the community was producing less than acceptable code in large quantities.
It was a time when having a guestbook on your website made you a rock star; a time when PHP development consisted in browsing scripts on hotscripts and hacking them to your needs. A time when development time was primarily focused on trial & error, without all the fanciness you get nowadays with framework and well implemented design patterns.
Even so, it is not a stage of PHP adolescence that I would likely relieve, quite the opposite… I would rather remove it from my memory, eternally and undisputed.
As mentioned in my last article, I started doing some challenges from the Programming Praxis website. And here comes my PHP solution to the second challenge.