Insomnia night, accidentally read a paragraph, it is said to be "harshna's law" in management (I don't know if there is a law in management): If the actual management person is more than the most The number of good people is twice, and the working hours must be more than four times; if the actual manager is 3 times more than the best number, the working hours must be 3 times, and the working cost is 6 times.
I have no experience in management, but this law seems to be equated to software design. When excessive design brings additional complexity, its negative effect does not seem to be linear growth, but the multiples of upward. BUG, additional maintenance costs, upgrades and transformations have become a nightmare.
I personally vent the body, that is, there is a period of being keen on complex design, using various modes and multi-layer architectures. It is true that such a design has brought considerable elasticity, but excessive excessive procedures are difficult to debug and maintain. Especially for the developers who do not have superb abilities like this, the program is slightly more complicated and will gradually exceed control. Finally, it will be inundated in the ocean of the code.
So recently starting to turn to a lightweight design, and it is increasingly lamenting the spiral trajectory of this world. Yes, we should not pay an additional price for unwanted features, and should not achieve some function for "possible" needs - considering expanding, it should also be expected, while try to reserve Interface instead of implementation. Although there is no in-depth understanding of AOP, it can also feel that this "woven" thinking can really bring such a wonderful balance. If we can easier woven code, you can easily and flexibly iterate our software.
Sample is smart, if it is. Reading STL, feeling a shock, while starting .NET 2.0.
Progress in science and technology should be able to work more easily, not the contrary. As a user or a creator, this is what I should remember.
