97 Things Every Software Architect Should Know
This Wiki is now Frozen. All the contributions have been moved to the production site which will become the new location for making future contributions when it goes live
Create an Account by clicking create_account. You don't need an email invite to create an account.
This is the (provisional) home page for developing 97 Things Every Software Architect Should Know.
Note: Before the site is made public we will be moving it from a wiki to a much more polished presentation created by professional web designers - this wiki is only an interim solution.
97 Things is a book of wisdom collected from leading software architects. When we have a suitable number of things, we'll open it to the public for comment. When we've reached some still-undetermined magic number, we'll publish it as a book. Right now, 97 sounds good.
What will come of all this?
O'Reilly will publish the contents of this wiki in a public and free web site off of the O'Reilly properties on July 15th, 2008. It will be embodied in a framework that is somewhat like a wiki, anyone can contribute, but looks more professional. It will be free to everyone but you'll have to register to contribute or comment or vote. Users (that's everyone who is registered) will be able to comment on other peoples axioms, rate other people's axioms, tag axioms, and create, edit and improve their own axioms. Anyone and everyone be able to view the material without requiring registration. The web site will be strongly promoted by O'Reilly and all contributers will get full attribution.
From the 97 Things web site O'Reilly plans to pick the top contributions and create a pocket guide which it will sell in bookstores and on-line. If your contribution is chosen any edits recommended by O'Reilly will be contributed back to the 97 Things web site for everyone to enjoy. Only contributions that meet certain requriments will be used in the book. They must be between 250 and 500 words long. The best size is 350 - 500 words. If they are shorter than 250 words O'Reilly might request that you expand them. If they are longer than 500 words O'Reilly will suggest edits to shorten the entry to 500 words. If the entries are not 250 - 500 words long they will not be included in the book, but they will be on the web site. Only works with a full bio will be used in the book. You must include a bio, contact information, and head shot. The contact information will not be in the book unless you want it to be - it will be used by O'Reilly to communicate with authors.
Rules of Engagement
- Contribution is by invitation only. You can nominate others for inclusion by adding them to the Nominations Page; please make sure to include an email address. We don't yet know whether there's one-to-one mapping between contributors and contributions, but for the time being, assume that each author may write one or more contributions. You can set yourself up with an account (just click create_account) and begin writing your first contribution immediately (see Contribution 0).
- Each contributor is asked to provide an axiom and a brief discussion. The axiom should only be a 2 to 10 words long if possible. In print, we want each axiom and discussion to fit on a two-page spread. Keep your discussion between 250 and 500 words. Discussions shorter than 250 words are fine, but only ones that are 250 or more are likely to make it into the final book.
- I'm asking everyone to create an author page (Please create one). Content on your author pages certainly doesn't count towards your 500 words. We'll want (minimally) a bio and a head shot. Only contributions with associated bios (including head shot, and description of background) will be considered for contributions to the book. We may include the bios and head shots in the print version of the book. You may use an icon that's associated with you instead of a picture. Please keep your author page up to date.
For those of us who aren't regular mediawiki users, how is the head shot to be added? To add a head shot, first use the "Upload file" under Toolbox (on the left side) to put the file on the server. Then use a tag like [[Image:filename.jpg]] in the bio.
- Please also add your snail-mail address and email address to the Addresses page. This information will not be released when the site goes public. We need to keep track of it so that we can send you a comp copy of the print book when it's available, and in case O'Reilly's legal department decides we need to get explicit releases from all the contributors prior to publication. (Hmm. The latter can probably be handled with email.) If you still don't want to disclose your contact info (and I cannot promise that this site won't "leak" out to the rest of the world), please still add your name to Addresses, and write "I'd prefer not to" or something like that. Then send me your contact info.
- Please, no illustrations and no code. We want principles of software architecture, not detailed coding examples. 250 - 500 well-chosen words can say a lot more than a picture. Please keep contributions product- and technology-agnostic. For example, don't talk about using Java over C#; just talk about principles that are valid across software technologies.
- Please edit your own contribution only.
- Please keep this URL private sharing it only with people you invite personally. Don't link to it, digg it, put it on your web pages, send it out to a mailing list, etc. First, it's only temporary. This book will not live within O'Reilly commons indefinitely. Second, we'd like to keep this under wraps until we have a decent block of material to release.
- All contributions made to this site are required to be made under the Creative Commons Attribution 3.0 license. This means that by making a content contribution, you are agreeing that it is licensed to us and to others under this license. If you do not want your content to be available under this license, you should not contribute it.
- You warrant that all work that you contribute to this site is your original work, except for material that is in the public domain or for which you have obtained permission.
The Good Stuff
Contribution 21 shows how we want you to structure contributions.
We're looking forward to working with you.
Richard Monson-Haefel, Curl Inc.
Mike Loukides, Editor, O'Reilly Media, Inc.
Please add your contributions here. Go into edit mode for this section to see how to add a new contribution.
Annotations: We are annotating contributions with either "Accepted" which means the axiom as its currently written has been accepted into the book (copy editing pending) or suggested edits. Any contribution that does not say Accepted will need more work in order to be included. We will try to be as explicit about what needs to done as possible. All contributions whether they are Accepted or not will be put on the web site when we go live on July 15th. In other words, Accepted means O'Reilly has chosen that contribution to be in the paper book; all contributions will be on the web site for everyone to enjoy whether they are Accepted or not.