The only constant is change itself
" The only constant is change itself." Today's famous words from the Greek philosopher Heraclitus (circa 540 before 480).
Recognizing that the experimental system must be constructed and discarded, ideas have changed redesign is inevitable, so the whole face change phenomenon is very useful. The first step is to accept the fact: change is innate, not outdated and annoying anomalies.
Easy to grasp the characteristics of software products and invisibility, leading to its builders faced eternal needs change.
However, some inevitable changes on the target, advance to prepare for them than to assume that they do not appear much better. Not only inevitable changes on the target, and design strategies and technological change is inevitable. Abandoned prototype concept itself is acceptance of the fact that - as the process of learning to change the design.
How to design systems for the above changes, it is a very well-known problems, is widely discussed in the book - but also much more likely to discuss than practice. They include detailed modular, scalable function, complete and accurate interface design between modules, complete documentation. In addition, they may even use some techniques include call queue and table-driven. The most important measure is the use of high-level language and self-documenting technologies to reduce errors caused by the change. The use of compile-time operations to integrate the standard statement, to a large extent helped to adjust the change. Stage of change is a necessary technology. Each product should have a digital version, each version should have its own calendar and freeze date, change after this part of the next version of the category.
For the formation of the team is more difficult than changing the design was changed. Each person is assigned work must be diverse, rich expansion of work, from a technical point of view, the whole team can be flexibly arranged. In large projects, the project manager needs to have two and three top programmers technology as light cavalry, when busy most intensive, they can gallops flew to solve various problems.
When the system changes, the management structure needs to be adjusted. This means that, as long as management and technical personnel of talent allows, the boss must give great attention to develop their ability to make management and technical personnel interchangeable.
Among these barriers are social, people must fight against stubborn wariness. First, managers often believe their own senior staff too "valuable", and reluctant to let them do the actual programming work; Second, management has a higher prestige. To overcome this problem, some labs such as Bell Labs, the abolition of all job titles. Each professional is "a technician in."