I’ve been bookmarking quite a few guides, docs, and other resources, some of which I thought I’d share here. (Oh and when I say “bookmarking”, I mean saving to a text file. I’m so high tech, dude.)
“All code in any code-base should look like a single person typed it, no matter how many people contributed.”
“Part of being a good steward to a successful project is realizing that writing code for yourself is a Bad Idea™. If thousands of people are using your code, then write your code for maximum clarity, not your personal preference of how to get clever within the spec.”
Developing Backbone.js Applications (Addy Osmani)
Writing forward-compatible websites (MDN)
“This page explains how to write websites that do not break when new browser versions are released. This is especially important for intranets and other non-public websites; if we can’t see your code, we can’t see that it broke. It’s not always possible to follow all of these, but following as many of them as possible will help future-proof your website.”
“Traditionally, a Web page would not contain much scripting, or at least, not much that would affect the performance of that Web page. However, as Web pages become more like applications, the performance of scripts is having a bigger effect. With more and more applications being developed using Web technologies, improving the performance of scripts is becoming increasingly important.”
Got Any Others?
As usual, Addy Osmani dominates authorship in these types of references. I swear, that guy doesn’t sleep.