 | This is a humorous essay. It contains the advice or opinions of one or more Wikipedia contributors and is made to be humorous. This page is not one of Wikipedia's policies or guidelines, as it has not been thoroughly vetted by the community. Some essays represent widespread norms; others only represent minority viewpoints. This essay isn't meant to be taken seriously. |
 | This page contains material that is kept because it is considered humorous. Such material is not meant to be taken seriously. |
Adapted from Akin's Laws of Spacecraft Design (archive), which has explicitly listed permissions that made the "laws" are compatible with CC BY-SA 3.0 license ("Anyone is welcome to link to these, use them, post them, send me suggestions of additional laws...") Enjoy.
- Articles is written with source. Analysis without source is only an opinion.[a]
- To write a perfect article takes an infinite amount of effort. This is why it's a good idea to write them to work when some things are wrong.[b]
- Writing is an iterative process. The necessary number of edits is one more than the number you have currently done. This is true at any point in time.[c]
- Your best writing efforts will inevitably wind up being useless in the final design. Learn to live with the disappointment.[d]
- (Miller's Law) Seven stuff is ideal, plus or minus two.[e]
- (Mar's Law) Everything is linear if plotted log-log with a fat magic marker.[f]
- At the start of any collaboration effort, the person who most wants to be team leader is least likely to be capable of it.[g]
- In nature, the optimum is almost always in the middle somewhere. Distrust assertions that the optimum is at an extreme point.[h]
- Not having all the information you need is never a satisfactory excuse for not starting the writing.[i]
- When in doubt, compose. In an emergency, scribble. But be sure to go back and clean up the mess when the facts come along.[j]
- Sometimes, the fastest way to get to the end is to throw everything out and start over.[k]
- There is never a single right way of writing. There are always multiple wrong ones, though.[l]
- Writing is based on requirements. There's no justification for designing something one bit "better" than the requirements dictate.[m]
- (Edison's Law) "Better" is the enemy of "good".[n]
- (Shea's Law) The ability to improve an articles occurs primarily at the interfaces. This is also the prime location for screwing it up.[o]
- The previous people who did a similar assessment did not have a direct pipeline to the wisdom of the ages. There is therefore no reason to believe their assessment over yours. There is especially no reason to present their assessment as yours.[p]
- The fact that a source appears in print has no relationship to the likelihood of its being correct.[q]
- Past experience is excellent for providing a reality check. Too much reality can doom an otherwise worthwhile design, though.[r]
- The odds are greatly against you being more correct than everyone else. If your analysis says your terminal velocity is twice the speed of light, you may have invented warp drive, but the chances are a lot better that you've screwed up.[s]
- A bad article with a good presentation is doomed eventually. A good article with a bad presentation is doomed immediately.[t]
- (Larrabee's Law) Half of everything you have heard before is crap. Research is figuring out which half is which.[u]
- When in doubt, document. (Documentation requirements will reach a maximum shortly after the termination of a program.)[v]
- The schedule you develop will seem like a complete work of fiction up until the time when it ends.[w]
- It's called a "work breakdown structure" because the work remaining will grow until you have a breakdown, unless you enforce some structure on it.[x]
- (Bowden's Law) Following a nomination failure, it's always possible to refine the article to show that you really had negative margins all along.[y]
- (Montemerlo's Law) Don't do nuthin' dumb.[z]
Cite error: There are <ref group=lower-alpha> tags or {{efn}} templates on this page, but the references will not show without a {{reflist|group=lower-alpha}} template or {{notelist}} template (see the help page).