This is a really good set of guidelines that "encourage consistency and predictability" during software development. These guidelines are specifically for library developers but I think they offer useful advice for all development tasks.
While we are on the subject, I've been enjoying the latest Larry Osterman series of blogs on code style. Here they are:
What does style look like, part 1
What does style look like, part 2 (structure)
What does style look like, part 3 (indentation)
What does style look like, part 4 (documenting)
What does style look like, part 5 (headers)
What does style look like, part 6 (naming conventions)
What does style look like, part 7 (language specific style)
What does style look like, part 8 (the end)
Larry's Coding Conventions
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment