Loading ...
Sorry, an error occurred while loading the content.

159151Re: [XP] A (more) Constructive Approach to (Emergent) Perfect Programs... A thought experiment.

Expand Messages
  • Adam Sroka
    May 28, 2014

      On Wed, May 28, 2014 at 5:14 PM, John Carter john.carter@... [extremeprogramming] <extremeprogramming@yahoogroups.com> wrote:

      However I want to take the "Just Barely Enough Design" further in two respects.

      * Take it deeper into the code writing process.
      * Have a prethought out sequence in which to apply architectural and design thinking.

      Why? Because nobodies brain is big enough to apply all the principles and guidelines simultaneously.

      Or if they do, they tend to freeze solid trying to find the perfect solution to 50 or more forces.

      Not all principles and guidelines are equal. To apply them well you need to understand why they are there. If you understand why you can draw a path back to first principles. If you are ever confused about what guideline to follow go back to those first principles and think about how they apply to the current context.

      The four rules of simple design are a good set of first principles for software design. There are other, related ways to think about it too, e.g. coupling and cohesion, SOLID, etc. 
    • Show all 9 messages in this topic