When I was a new PHP developer, I discovered that there’s a myriad of solutions, options, configurations and frameworks available. I thought, how does one sift through all the noise and get something done? How can anyone have a grasp of the best practices in PHP, and make sense out of all the options? Which extensions do we use, and how do we use them? What’s a best practice, anyway?
This is why I’ve decided to offer “Do This, Not That” for beginning and intermediate PHP developers looking to find a better grasp on precisely how to develop in PHP. This great series of highly focused e-books will offer tips, tricks and best practices focused on core areas of PHP development, including databases, security, filtering, regular expressions, configuration and more. Since it will be a series of tightly targeted solutions, developers will be able to pick all, some or just one of the offerings that solves their specific problem(s).
Yesterday, an (understandably) frustrated gentlemen tweeted a link saying the fact that my book’s print and ebook editions were priced the same, was “greed.” While this was a bit hyperbolic to be sure (and the price being identical was in fact a mistake that has now been corrected), it sparked a discussion about book pricing and content value that gave me pause to reconsider all I had previously thought about buying a print versus an ebook.
It’s not uncommon to see ebooks priced lower, and in many cases significantly lower than their print counterparts. It makes logical sense on first pass: the cost of printing, storing and distributing physical media is higher than the cost to send an ebook to a purchaser via email. Marco Tabini points out that “when you buy a can of beans at the supermarket, it’s the beans you really want, not the can, which is simply a convenient medium for the manufacturer to sell you their goods.”