Is Design Dead?

I believe that it is important to design first and then code, this will avoid the code and fix. Also, I think that “if you listen to your code a good design will appear” is one of the worst quotes. It is very interesting to know that there are two styles of design. The first one is the evolutionary design, which is a disaster, it makes the code harder to alter. Now, the counter part is the planned design, which contain a notion born from other branches of engineering. Building codes into this design is to follow the rules about how you design structures based on experience of what works.

This las one design is not the perfect one, it has some faults. The first fault is that it is impossible for a person to think in all the issues that are going to be present when they are programming. There is a cultural problem with this type of design, the designers are designers because their skills and experience, but they are too busy with this job, so they do not have enough time to code any more.

A feasible way to deal with changing requirements is to build flexibility into the design so it would be easier to change it as the requirement need it.

In extreme programming the continuous integration is necessary to keep the teamwork in sync, it will be easier to make changes and do not need to integrate other people.  Refactoring is also important because people who do it, find a difference between their effectiveness compared to doing looser, more ad-hoc restructuring.

I agree with the quotes “Do the simplest thing that could possibly work” and “You aren´t going to need it” because we have to think in present requirements and try to make them as easy as we can so that we can change them when the requirement needs it.