Dev / non dev communication

  • 1,664 views
Uploaded on

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

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

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
1,664
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
30
Comments
0
Likes
2

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. What are you saying? http://aaron.jorb.in @aaronjorbin
  • 2. A designer knowsthat he hasachievedperfection notwhen there isnothing left toadd, but whenthere is nothingleft to take away.
  • 3. Engineering is done with numbers. Analysis without numbers is only an opinion.
  • 4. Design is aniterative process.The necessarynumber ofiterations is onemore than thenumber you havecurrently done.This is true at anypoint in time.
  • 5. The odds are greatly againstyou being immenselysmarter than everyone elsein the field. If your analysissays your terminal velocityis twice the speed of light,you may have inventedwarp drive, but the chancesare a lot better that youvescrewed up.
  • 6. The fact that ananalysis appears in print has no relationship to the likelihood of its being correct.
  • 7. There is never a single rightsolution. There arealwaysmultiple wrong ones,though.
  • 8. Sometimes, the fastestway to get to the end is to throw everything out and start over.
  • 9. The schedule youdevelop will seem likea complete work offiction up until thetime your customerfires you for notmeeting it.
  • 10. You cant get to the moon byclimbing successively taller trees.
  • 11. A good plan violentlyexecuted nowis better thana perfect plan next week.
  • 12. Capabilitiesdriverequirements,regardless ofwhat thesystemsengineeringtextbooks say.
  • 13. Not having all the information you need is never a satisfactory excuse for not starting the analysis.
  • 14. When in doubt, estimate.In an emergency, guess.But be sure to go back andclean up the mess when thereal numbers come along
  • 15. The fact that an analysis appears in print has no relationship to the likelihood of its being correct.
  • 16. A bad design with a goodpresentation is doomedeventually. A good design with a bad presentation is doomed immediately.
  • 17. "Better" isthe enemyof "good".
  • 18. Dont do nuthin dumb.
  • 19. When in doubt, document. (Documentation requirements will reach a maximum shortly after the termination of a program.)
  • 20. Aaron Jorbin @aaronjorbin http://aaron.jorb.in http://addthis.comAll Quotes from: Akins Laws of Spacecraft Design http://spacecraft.ssl.umd. edu/akins_laws.html