No Reuse Before Use
•
6 likes•2,477 views
The software industry has an overloaded expectation for reuse. And different people have different expectation from software reuse. When reuse happens before actual use, the reality is often quite different than everybody's expectation. This talk promotes working software that has customer value, once-and-only-once over reusability, simplicity before generality, use before reuse.
Recommended
Recommended
More Related Content
Similar to No Reuse Before Use
Similar to No Reuse Before Use (20)
More from Terry Yin
Recently uploaded
Recently uploaded (20)
No Reuse Before Use
- 1. No Reuse Before Use terry@odd-e.com
- 2. Who Am I 2 • I am Terry Yin • Work for Odd-e • Experienced in software development • Focus on technical coaching • Love programming • A father Me
- 4. Let’s Visit A City On The Opposite Side of the Globe
- 5. 5
- 6. 6
- 8. 8
- 9. 9 10,000 pedestrian lives are lost on Brazilian road in 2012, whom in theory do not existing in Brasilia. (270, 000 around the world)
- 10. "Organic planning does not begin with a preconceived goal; it moves from need to need, from opportunity to opportunity, in a series of adaptations that themselves become increasingly coherent and purposeful, so that they generate a complex final design, hardly less unified than a pre- formed geometric pattern.” — Lewis Mumford explained further what he admired in medieval cities
- 11. 11
- 12. 12 Now
- 13. 13
- 14. 14 Why the graphic designer doesn’t understand reuse?
- 17. Customer Value 17 People do not on the whole pay for (or need) generality: They tend to have a specific situation, and it is a solution to that specific situation that has value. Simplicity before generality, use before reuse, by Kevlin Henney
- 18. 18
- 19. 19 Design from the perspective of use rather than implementation
- 20. 20 CostofChange 0 1 2 3 4 5 6 7 8 9
- 21. 21 — Kent Beck, inventor of XP
- 22. 22 Duplication may be the root of all evil in software. Clean Code, Robert C. Martin
- 23. Refactoring • Small steps • Look for code smells • Following design principles - SOLID - High cohesion, low coupling - Once And Only Once • Design emerges from working code 23 "Refactoring is the process of changing a software system in such a way that it does not alter the external behavior of the code yet improves its internal structure." Refactoring: Improving the Design of Existing Code by Martin Fowler
- 24. The Second-System Effect 24 Mythical Man Month (1974), Fred Brooks What has been done What was originated but not done In the first system Real experience What the architect himself think his experience is, and will apply to the 2nd system.
- 25. Emergent Design 25 Code, listen you shall. Let the design be the way it wants to be!
- 26. 26 Will Reuse Save Money?
- 27. Reuse Is Not Free 27 All non-trivial abstractions, to some degree, are leaky. The Law of Leaky Abstractions by Joel Spolsky
- 28. Devise 28
- 29. 29 Who Want To Be Reused? Business Logic? OS functionality? Mathematics library? Design Patterns? Framework? Domain Models? Middleware? Open source? No Reuse?
- 30. Project Or Product • When you make a product like a project • you get Brasilia 30
- 31. Working software is our primary goal Simplicity before generality, use before reuse Do emergent design Reuse isn’t always a good thing 31