Akins laws

Posted at 2016-08-29.

I came across a post called "Akins laws on spacecraft design" and these make a lot of sense. I thought I'd copy them here, perhaps add a comment or two.

Engineering is done with numbers. Analysis without numbers is only an opinion.
To design a spacecraft right takes an infinite amount of effort. This is why it’s a good idea to design them to operate when some things are wrong.
Design is an iterative process. The necessary number of iterations is one more than the number you have currently done. This is true at any point in time.

Aka "All non-trivil designs have bugs".
Your best design efforts will inevitably wind up being useless in the final design. Learn to live with the disappointment.
(Miller’s Law) Three points determine a curve.
(Mar’s Law) Everything is linear if plotted log-log with a fat magic marker.
At the start of any design effort, the person who most wants to be team leader is least likely to be capable of it.
In nature, the optimum is almost always in the middle somewhere. Distrust assertions that the optimum is at an extreme point.

I've always thought that if any adjustment needs to be at max/min means something is wrong.
Not having all the information you need is never a satisfactory excuse for not starting the analysis.
When in doubt, estimate. In an emergency, guess. But be sure to go back and clean up the mess when the real numbers come along.
Sometimes, the fastest way to get to the end is to throw everything out and start over.

Rewrite is often cheaper (and better) than an incremental version change. But every time you bring in a new design or a component or an idea, you bring in new problems and bugs and interfaces. It's a gamble either way.
There is never a single right solution. There are always multiple wrong ones, though.
Design is based on requirements. There’s no justification for designing something one bit “better” than the requirements dictate.
(Edison’s Law) “Better” is the enemy of “good”.
(Shea’s Law) The ability to improve a design occurs primarily at the interfaces. This is also the prime location for screwing it up.
The previous people who did a similar analysis did not have a direct pipeline to the wisdom of the ages. There is therefore no reason to believe their analysis over yours. There is especially no reason to present their analysis as yours.

This is a common rule of thumb in repair. Never trust previous repairs, especially if you did them yourself. Yourself is the easiest person to fool.
The fact that an analysis appears in print has no relationship to the likelihood of its being correct.

May have been Heinlein where I saw a very good and rather obvious philosophical point: The truthfulness of a statement does not depend on its credibility or vice versa.
Past experience is excellent for providing a reality check. Too much reality can doom an otherwise worthwhile design, though.
The odds are greatly against you being immensely smarter than everyone else in the field. 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.
A bad design with a good presentation is doomed eventually. A good design with a bad presentation is doomed immediately.
(Larrabee’s Law) Half of everything you hear in a classroom is crap. Education is figuring out which half is which.

Most of it is also only useful for understanding some other idea.
When in doubt, document. (Documentation requirements will reach a maximum shortly after the termination of a program.)
The schedule you develop will seem like a complete work of fiction up until the time your customer fires you for not meeting it.
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.
(Bowden’s Law) Following a testing failure, it’s always possible to refine the analysis to show that you really had negative margins all along.
(Montemerlo’s Law) Don’t do nuthin’ dumb.
(Varsi’s Law) Schedules only move in one direction.
(Ranger’s Law) There ain’t no such thing as a free launch.
(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.
(von Tiesenhausen’s Law of Engineering Design) If you want to have a maximum effect on the design of a new engineering system, learn to draw. Engineers always wind up designing the vehicle to look like the initial artist’s concept.
(Mo’s Law of Evolutionary Development) You can’t get to the moon by climbing successively taller trees.
(Atkin’s Law of Demonstrations) When the hardware is working perfectly, the really important visitors don’t show up.
Space is a completely unforgiving environment. If you screw up the engineering, somebody dies (and there’s no partial credit because most of the analysis was right…)

A lot of this is space flavoured, but still, good stuff.

XTL :: blog

Akins laws

See also