Please Read this Guideline before Making Your Own Contribution
Welcome! Thanks for taking the time to read this (meta)contribution.
With a limit of 500 words, a contribution should not have any need of any headings, so don't worry about that aspect of wiki markup. External links and normal text formatting are fine. However, as the intent is also to publish accepted contributions in book form, each contribution should be able to stand on its own and should not rely on an external link in order to make sense.
As already mentioned on the main page, the recommended length of a contribution is between 250 and 500 words. Spell-checked (US English) contributions are always appreciated! O'Reilly have a stylesheet which you can read through if you're interested. Not all of it is applicable to the 97 Things format, but you may find it useful nonetheless.
Advice that is focused on programming should be as independent of programming language as possible. The set of contributions is intended to appeal to programmers across the board, so items on metaprogramming in Ruby, hardcore templates in C++, or the ins and outs of annotations in Java would not be appropriate. Of course, programming languages can be mentioned, their features discussed, and code fragments included, but the advice offered should not be so specific to a programming language that it does not speak to readers working with other languages.
And don't forget to include your bio or to put your name on your contribution (see line below). Thanks and I look forward to your contribution(s)!
This work is licensed under a Creative Commons Attribution 3
Back to 97 Things Every Programmer Should Know home page