dev / non dev communication

20

Click here to load reader

Upload: aaronjorbin

Post on 25-Jun-2015

1.714 views

Category:

Technology


4 download

DESCRIPTION

The slides from my lightening talk that have nothing to do with what I actually said, but are quotes meant to inspire you

TRANSCRIPT

Page 1: Dev / non dev communication

What are you saying?

http://aaron.jorb.in @aaronjorbin

Page 2: Dev / non dev communication

A designer knows that he has achieved perfection not when there is nothing left to add, but when there is nothing left to take away.

Page 3: Dev / non dev communication

Engineering is done with numbers.

Analysis without numbers is only an opinion.

Page 4: Dev / non dev communication

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.

Page 5: Dev / non dev communication

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.

Page 6: Dev / non dev communication

The fact that an analysis appears in

print has no relationship to the

likelihood of its being correct.

Page 7: Dev / non dev communication

There is

never a

single right

solution.

There are

always multiple wrong ones,

though.

Page 8: Dev / non dev communication

Sometimes, the fastest way to get to the end is to throw everything out and

start over.

Page 9: Dev / non dev communication

The schedule you develop will seem like a complete work of fiction up until the time your customer fires you for not meeting it.

Page 10: Dev / non dev communication

You can't get to the moon by climbing successively taller trees.

Page 11: Dev / non dev communication

A good plan violently

executed now is better than a perfect plan

next week.

Page 12: Dev / non dev communication

Capabilities drive requirements, regardless of what the systems engineering textbooks say.

Page 13: Dev / non dev communication

Not having all the information you

need is never a satisfactory

excuse for not starting the

analysis.

Page 14: Dev / non dev communication

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

Page 15: Dev / non dev communication

The fact that an analysis appears in print has no

relationship to the likelihood of its being

correct.

Page 16: Dev / non dev communication

A bad design with a good presentation is doomed eventually.

A good design with a bad presentation is doomed

immediately.

Page 17: Dev / non dev communication

"Better" is the enemy of "good".

Page 18: Dev / non dev communication

Don't do nuthin' dumb.

Page 19: Dev / non dev communication

When in doubt, document.

(Documentation requirements will reach a

maximum shortly after the termination of a program.)

Page 20: Dev / non dev communication

Aaron Jorbin

@aaronjorbinhttp://aaron.jorb.in

http://addthis.com

All Quotes from:Akin's Laws of Spacecraft Design http://spacecraft.ssl.umd.

edu/akins_laws.html