Simple is hard
Download as KEY, PDF
3 likes1,041 views
Writing good software is not easy. Clear methods, solid classes, well designed services, and successful applications have something in common: they were hard to write. The opposite is also true complex software is easy to write. This is known as spaghetti code. In this talk well uncover some tips and techniques to improve your software quality and help you identify and articulate when its worth investing time into simplicity so that you can grow your applications into something incredible!
Simple is hard
- 2. Jim Siegienski Architect
- 3. Simple: easily understood; presenting no dif鍖culty.
- 4. Complex: hard to understand or deal with.
- 8. Easy: requiring no great labor or effort.
- 9. Hard: dif鍖cult to do or accomplish; fatiguing; troublesome.
- 13. Postulate: logic - as a set of instructions - is easy for developers.
- 15. Postulate: structure - as a disparate organization of logic - is hard for developers.
- 17. Creation -> Hard Comprehension & Use -> Easy
- 18. "Our goal is to try to bring a calm and simplicity to what are incredibly complex problems so that you're not aware really of the solution, you're not aware of how hard the problem was that was eventually solved." -Jonathan Ive
- 19. E = mc^2 quod erat demonstrandum E Pluribus Unum a^2 + b^2 = c^2 circumference / diameter = pi
- 20. Whatever is predicated universally for a given class is predicated for anything within that class.
- 23. Syllogism
- 25. If all A are B and C is in A then C is B
- 26. A B C B C A
- 27. If all Getters only get records and GetPerson is a getter GetPerson only gets a record!
- 29. "Systems break down when assumptions are invalidated." -Jimski
- 30. Why Structure? One big 鍖le? What is a Helper? What is a Utils?
- 31. Structure is a byproduct of naming and classi鍖cation.
- 36. Logical Random Analytical Synthesizing Parts Holistic
- 40. Readability Clarity Purpose Code Wants to be Stoopid
- 41. Naming Cohesion One Job Consistency
- 42. Naming Tips The more local the smaller the variable name Consistent idioms Magic numbers are not logical - proprietary knowledge that's not transferrable
- 43. Reusability Abstract Useful Named Appropriately
- 46. "I don't like bad Abstractions!" -anonymous
- 47. "I don't like bad Abstractions!" -anonymous
- 48. Refactorability Insulate change "if it's ugly put it in a box." Name, Name, Name
- 52. E.g. CMS Rules Engine Database
- 55. E.g. Differentiator High Reuse Critical
- 56. Logical Hard Work + Naming & = Structure Simple Elegance
- 57. "We choose to go to the moon. We choose to go to the moon in this decade and do the other things, not because they are easy, but because they are hard" -John F. Kennedy, September 12, 1962
- 59. Resources: http://www.infoq.com/presentations/Simple-Made-Easy Rich Hickey - Author of Clojure http://www.carlopescio.com/2010/11/notes-on-software-design-chapter-12.html Carlo Pescio - Entanglement http://www.carlopescio.com/2011/04/your-coding-conventions-are-hurting-you.html Carlos Pescio - Naming http://www.telegraph.co.uk/technology/apple/9283706/Jonathan-Ive-interview-simplicity-isnt-simple.html Jonathan Ive - Simplicity isn't Simple Books: Elements of Logic - Richard Whately (1826) The Practice of Programming - Brian Kernighan, Rob Pike Refactoring - Martin Fowler
- 60. Comments for CodeFaire 2012: https://joind.in/6720 Jim Siegienski: jim.siegienski@gmail.com @JimSiegienski http://www.linkedin.com/in/jimsiegienski http://www.slideshare.net/jimsiegienski
Editor's Notes
- #2: \n\n
- #3: \n\n
- #4: \n\n
- #5: \n\n
- #6: \n\n
- #7: \n\n
- #8: \n\n
- #9: \n\n
- #10: \n\n
- #11: \n\n
- #12: \n\n
- #13: \n\n
- #14: \n\n
- #15: \n\n
- #16: \n\n
- #17: \n\n
- #18: \n\n
- #19: \n\n
- #20: \n\n
- #21: \n\n
- #22: \n\n
- #23: \n\n
- #24: \n\n
- #25: \n\n
- #26: \n\n
- #27: \n\n
- #28: \n\n
- #29: \n\n
- #30: \n\n
- #31: \n\n
- #32: \n\n
- #33: \n\n
- #34: \n\n
- #35: \n\n
- #36: \n\n
- #37: \n\n
- #38: \n\n
- #39: \n\n
- #40: \n\n
- #41: \n\n
- #42: \n\n
- #43: \n\n
- #44: \n\n
- #45: \n\n
- #46: \n\n
- #47: \n\n
- #48: \n\n
- #49: \n\n
- #50: \n\n
- #51: \n\n
- #52: \n\n
- #53: \n\n
- #54: \n\n
- #55: \n\n
- #56: \n\n
- #57: \n\n
- #58: \n\n
- #59: \n\n
- #60: \n\n
- #61: \n\n
- #62: \n\n