Published in Link Wrap on Thursday, September 1st, 2005
As this blog matures, and I get a better handle on the different things that I like to write about, I'm slowly starting to realize a few things, and as a result, I've decided to set up the first "regularily scheduled post", Link Wrap.
Here's the situation. This site has about 1200 readers on RSS for the main content, and another 500 for the link blog.
Given that breadth, I figure it would be alright, and perhaps good marketing, to feature a run down of links from the link blog in the main blog on a once a week basis. Chances are that I will add a few more ephemeral links too, stuff that maybe isn't worth storing in the resources but is timely and interesting.
Why? Well, for starters, I follow several link blogs around the web. Sometimes those folks will post something old, something that I have seen before and maybe even bookmarked but forgotten about. Upon seeing it again, I happen to find that at that moment it is very useful. If that happens to me, it must happen to others too.
Next, I tend to write about the same kind of stuff that I link to. Therefore, it could follow that the readers of this blog may be interested in the links that I post.
Finally, as a result of #2 there, it may be a great way for those who haven't realized that I even have a link section that I in fact do have one.
Some people have tried them and left them, others received negative feedback and dropped them. You may be asking yourself "why then, Mike, in the face of this do you start Link Wrap now?"... or you may not, but I'm going to tell you why anyway.
Those folks had different objectives, I think. I am a web developer, and the links I post here are useful for me. I'm not doing it for link-love, not linking it because he or she is, and they aren't for entertainment.
So there. Introducing Link Wrap - a wrap up of links, posted every Friday. Why Friday? Well, in that way, you can review link wrap to fill that little gap of time after-lunch-pre-first-beer when you don't feel like working and need something to do.
I started freelancing by diving in head first and getting on with it. Many years and a lot of experience later I was still able to take away some gems from this book, and there are plenty I wish I had thought of beforehand. If you are new to freelancing and have a lot of questions (or maybe don't know what questions to ask!) do yourself a favor and at least check out the sample chapters.
Like the other books listed here, this provides a great reference for the PHP developer looking to have the right answers from the right people at their fingertips. I tend to pull this off the shelf when I need to delve into new territory and usually find a workable solution to keep development moving. This only needs to happen once and you recoup the price of the book in time saved from having to develop the solution or find the right pattern for getting the job done..