|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: 26 Rules for FRC Design
You missed the best one!
29. (von Tiesenhausen's Law of Program Management) To get an accurate estimate of final program requirements, multiply the initial time estimates by pi, and slide the decimal point on the cost estimates one place to the right. Quote:
Last edited by Ian Curtis : 29-07-2013 at 19:36. |
|
#2
|
||||
|
||||
|
Re: 26 Rules for FRC Design
love this
|
|
#3
|
|||||
|
|||||
|
Re: 26 Rules for FRC Design
Whenever we'd ask for a estimate on the mechanical subsystems, the mechanicals would double their estimate and then tell our project manager, who would double and then tell myself, the software lead, and then I would double it. Still wasn't accurate enough a lot of the time.
|
|
#4
|
||||
|
||||
|
Re: 26 Rules for FRC Design
Quote:
By the way, who comes up with these names ("de Saint-Exupery's Law of Design")? The fact that they seem so formal and establishment-sounding makes it so much funnier! |
|
#5
|
|||||
|
|||||
|
Re: 26 Rules for FRC Design
[Relevant background to my upcoming comment: My last name is Coulombe.]
My kids (especially the ones who have had physics) have begun keeping track of "sage" things I say during the year and have dubbed them "Coulombe's Laws" #1 above is very close to a favorite of mine: "Do the math!" |
|
#6
|
||||
|
||||
|
Re: 26 Rules for FRC Design
They are named after the rocket scientist that came up with them. Google them, they were smart people that did cool stuff.
|
|
#7
|
|||||
|
|||||
|
Re: 26 Rules for FRC Design
Quote:
Quote:
|
|
#8
|
|||||
|
|||||
|
Re: 26 Rules for FRC Design
Quote:
staring at every part individually asking "do you need to exist?" |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|