XP recommends simplicity, which may or may not lead to reusable code. The result is not automatically reusable across projects regardless of how Good Design it is because reusability costs (hardly anything is without explicit attention to it) and the focus is on current customer value.Originally posted by HS Thomas:
The simplest thing that worked (quick and dirty ) but hardly reusable or OO design, an extra step in compilation, a waste of time in that respect. When XP recommends doing the simplest thing that worked, I expect it also means aiming for reusable OO.
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Originally posted by Lasse Koskela:
the focus is on current customer value.
Personally, I have only reused two things:
1) a set of requirements and an architecture for a specific problem domain
2) a custom library of XML, IO, etc. utility classes
Originally posted by HS Thomas:
The simplest thing that worked (quick and dirty )
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Originally posted by HS Thomas:
Thanks, Ilja. That sounds simple.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Did you see how Paul cut 87% off of his electric heat bill with 82 watts of micro heaters? |