I actually think '5 Development Tips Every Designer Should Know' would be more useful. This is because a designer these days probably has to play with CSS and HTML, if not jQuery too.

A developer won't be handling the design themselves, but a designer might well be contributing some code on the front-end. And it's sometimes the case that such code isn't well (or consistently) formatted, or is too complicated, as writing code isn't the primary aspect of their job.

It's like poorly organised PSDs. You might be totally fine littering your file with spurious layers, bad names, and inconsistent groupings. The person you might share it with won't feel the same way, and it'll compel them to waste time figuring it out and possibly spend more time making it sane.

But for personal projects where a developer might want their own site, the advice here is good.