Earlier quoted context omitted.
A personal rule of thumb I derived from the ninety-ninety rule is this: "Before starting a project, ask yourself if you would still do it if you knew it would cost twice as much and take twice as long as you expect. Because it probably will."
Twice is a (reasonable) minimum.
Famous Laws of Software Development (2017)
41–50 of 202 posts
Re: Famous Laws of Software Development (2017)
#42Re: Famous Laws of Software Development (2017)
#43Re: Famous Laws of Software Development (2017)
#44There is an error in the ninety-ninety rule, which should be stated as: The first 90% of the code takes the first 90% of the time. The remaining 10% takes the other 90% of the time.
Re: Famous Laws of Software Development (2017)
#45Moore’s law is dead! Also, I think Murphy’s law should be removed, it’s less true than the other laws here. I read a fantastic article many years ago in the Atlantic where the author was analyzing and deconstructing an airplane crash, and in it was a paragraph about how Murphy’s law is completely backwards, and in reality if things can go right, then they will. Things will almost always go right unless there’s no pos…
As I interpret Murphy's Law, it's not so much about failure in actuality, but more about anticipating the failure, and designing your code/product/system for the worst case scenario.
Murphy himself was unhappy abut the common interpretation of his law, which is negative rather than cautionary, implying a vindictiveness to exist in inanimate objects and the laws of chance.
> but more about anticipating the failure, and designing your code/product/system for the worst case scenario
Which was his intent. IIRC the phrase was coined while working on rocket sleds for a land speed record attempt. He was essentially trying to achieve "no matter what happens we want to maximise the chance of the pilot being alive afterwards, if some of the equipment survives too that is even better" and promoting a defensive always-fail-as-safely-as-possible engineering stance.
Re: Famous Laws of Software Development (2017)
#46Page author, if you read this: Fred Brooks last name has an s. (Brooks, not Brook.) It should be Brooks' law.
Wouldn't it be "Brooks's" rather than "Brooks'"? From what I know, the "*s'" thing works mostly for plural nouns. For singular, it only applies to classical & religious names ending with "s" ("Jesus'", "Archimedes'" etc). I am not an English native so I may be completely off. Feel free to rage :)
Re: Famous Laws of Software Development (2017)
#47Re: Famous Laws of Software Development (2017)
#48I know this is harsh, but if you're a web developer, and your blog requires a loading screen to read, at least on mobile, then maybe you should take a step back, and learn to program, before you start writing about programming.
https://en.m.wikipedia.org/wiki/Flash_of_unstyled_content
Single page apps have quite a bit of control over rendering, however Google prefers that indexed markup be pre rendered from the server. Juggling the two competing priorities leads to byzantine technical issues.
Front end development for content sites can be complex.
Re: Famous Laws of Software Development (2017)
#49Re: Famous Laws of Software Development (2017)
#50Biggest one that is missing from the list in my opinion is Vogels Law: "Everything breaks, all the time" - Dr. Werner Vogels CTO Amazon.com