One of the problems with technical writing is that the instructions you provide will eventually become outdated. Some details, such as the fundamentals of a programming language like C, Ruby, or PHP, change relatively slowly. Others, like libraries, frameworks, and browsers, change frequently. And so, it was not surprising to find out that PayPal changed some of their systems a while back in a way that will affect readers of my “Effortless E-commerce with PHP and MySQL” book. This issue first appeared last summer in my support forums, with Sean and Michael discovering the problem and the solution.
Continue Reading...So progress on “The Yii Book” in the past month has not gone as well as I would have liked. And, sadly, progress has been poor for no particular reason other than my own ability to get things done. These things do happen to us all, but it doesn’t mean I’m happy about. Still, even though it’s been slow, progress is being made. A quick status report…
Continue Reading...
This is the second of a two-part newsletter on “going big”. By “going big” I mean how one transitions from a Web site with little to moderate traffic, to one that can handle tons of traffic. The previous newsletter looked at going big from the macro perspective: theory, implementation, hardware, and networking. In this newsletter, I’ll look at the micro perspective: how to write code that scales well. And, as it turns out, this newsletter again got to be too big, so this is part one of two parts that makes up part two of the two-part series. (Huh?) In this newsletter, I’ll mostly focus on code. The next will mostly focus on the database.
Before going into details, I’m going to define what it means to be a “big” site. As I said in the previous newsletter, it actually depends upon the kind of content and activity the site has: X number of video requests is far more demanding than the same X number of mostly text pages. Likewise, X number of WordPress page requests is far more demanding than the same X number of static HTML page requests. For the purposes of this discussion, let’s say that “big” is a site that gets in the broad neighborhood of 100,000 to 500,000 pageviews per day. At that point (if not before), you’ll need more than one server to handle the load. (As a counterpoint, on the highest end, Netflix sometimes requires up to 20,000 servers at a single time.)
As always, questions, comments, and all feedback are much appreciated. And thanks for your interest in what I have to say and do!
Continue Reading...
I just recently discovered the Web site LayoutIt!. LayoutIt! provides a Web-based drag-and-drop interface for creating HTML layouts using the Twitter Bootstrap framework. For someone like me, with no design skills whatsoever, Twitter Bootstrap and this new LayoutIt! tool are wonderful inventions.
Continue Reading...
When it comes to running a business, a lot of the discussion and effort goes towards getting new clients. Getting new clients is important, of course, especially when you’re just getting started, but I believe that many business and people don’t focus enough on the clients they already have. As happy as you are when you get a new project and client, how long is it before your eyes start to wander to that next possible job? This is natural, and certainly I’ve been guilty of it myself. But I would argue that you should put at least as much thought and effort into treating your current clients right as you put into getting new clients. Let’s look at the why’s and how’s…
Continue Reading...
