Caribbean Cruise Electra

image informatics rules

Directly from Royal Pingdom, the most useful and realistic rules and laws governing the programming and software development:

90-90 Rule

The first 90% of the code accounts for the first 90% of development time. The other 10% takes the other 90% of the time. Hofstadter Law

always takes longer than you expect, even when you take into account Hofstadter's law. Brooks Act

Add more people to a late project only further delay.

WAB with a corollary: 9 women do not have a child in 1 month. Method

Moscow (ing)
(dare I translate as "Development" Both TDPN For Nothing "or" TeleDePortacióN "

A technique to prioritize requirements during development. MOSCOW corresponds to:

M - Must have this. ----- You have to have it
S - Should Have this if at all possible. ---- You should have it if possible
C - Could Have this if not does it Affect anything else. ---- I could have it if they do not affect just
W - Will not Have But Would like this time in the future. ---- I will not now but could be in the future

KISS Principle

untranslatable: Keep It Simple, Stupid. Linus's law

Given enough eyeballs

, Are all bugs shallow. Murphy Law

If something can go wrong will go wrong. Sutton Law

Go where the money is.

(Explanation: When trying to diagnose a problem, first confirmed the most likely possibilities. Formulated after Willie Sutton, bank robber, who did "because that's where the money is.") Wirth

Law Software slows down faster than it speeds up the hardware. Conway Law

Any piece of software reflects the organizational structure that produced it.

(Example interesting: The Mars Climate Orbiter NASA crashed because one of the development team used English units while the other used the metric system). The first Hollywood

Do not call us, we'll call you.

(instead of your program guide system, the system runs your program.)

The Dilbert Principle

most useless workers are systematically promoted to the place where less Da'na can do: management.