Published in Web Development on Monday, March 15th, 2004
Some great conversations going on over at Alex King's website and spun off to Anne van Kesteren's blog about Alex's post, The Myth of CSS.
Alex basically points out how true separation of style from content is not acheived in a lot of websites, as extranoues div's and span's are often used simply as style hooks. There are some significant points raised in the comments that follow on both sites.
In the end this is sort of a semantic argument about semantics and markup, but something worth being aware of if we really want to have an accurate understanding of the tools that we use, how to properly use them and where they can be improved in the future.
Sitepoint's web devlopment books have helped me out on many occasions both for finding a quick solution to a problem but also to level out my knowlegde in weaker areas (JavaScript, I'm looking at you!). I am recommending the following titles from my bookshelf:
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.
The author line-up for this book says it all. 7 excellent developers show you how to get your JavaScript coding up to speed with 7 chapters of great theory, code and examples. Metaprogramming with JavaScript (chapter 5 from Dan Webb) really helped me iron out some things I was missing about JavaScript. That said each chapter really helped me to develop my JavaScript skills beyond simple Ajax calls and html insertion with libs like JQuery.
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..
Comments and Feedback