Code irreplaceable tool will generate the code of the market, but only for customers, a lot of demand are vague or even themselves do not want to know what it was like, so we can not abandon the necessary precision,
So the code forever.
Will have different needs different code, methods, modules. I've seen a lot of programmers (including myself ..) is a demand to immediately get started, the demand for fast by page, the background, to run a database written of a process,
Then what happens?
When a system development and maintenance of more than three months, you will find that the system criss-cross, disordered complex code, coupled with superior method, according to the development and documentation requirements document are not read logical relationship,
For example, I met a code, simply put "int i = 0", was changed to "int i = 1" Such simple changes in demand (similar to the actual course not so simple), I guess you change how long?
Plus half a day in the morning!
This is for me to develop this speed proud man is simply an insult, (the key is the Party is indeed pressing others ...)
Then give reason I find myself is that customers want urgency (in fact, usually the same day the next day to achieve the third day of testing needs rework or release)
Then eventually we found, in fact, because of his lazy
I've been engaged in agile development for five years, two or three years ago out of the exercise of the above-mentioned ability to write fast code, such as peak time, customers in the morning to go to work proposes a new page (including lists, New Laws, export, delete) I probably lunch before the test can be good and then publish directly
But this really fast I want to do? Or is it real fast development of it?
I like this nominally "efficient" approach, in fact, this is the macro-efficiency
Over time, demand increased my efficiency or speed will be getting lower and lower, reaching the final with 0
The new demands may come, I will, as before the "efficient", but need to change some small change.
But the demand is not static, long as the customer needs to change. I like eating rat poison, like despair and sit still ...
It is really a problem of demand changes, or let the programmer to write code that there is a problem?
Actually, the problem has slowly surfaced not it.
Changes in customer demand is not a problem, (after all, people pay, even if there were, that people also pay your money's)
So how to solve it?
Back I will write a detailed solution