Chapter One: pragmatic philosophy
A. The code I let the cat to eat
In programming, we need, every line of code, each of the variables responsible for each function we write, but the fact is, we are afraid to be responsible, we are afraid of being accused of this type of encounter negative phenomena. However, a software engineer, we have to do is not only a design feature, is to meet the need of thing never happened, we may have no way to solve this problem, but we need to offer solutions, rather than to escape to the surface responsibility. The courage to honestly admit mistakes, and try to give a variety of choice, and should not be transferred responsibility or find excuses. In fact, this phenomenon can be seen in the code syntax, in case if there is no judge to, we can use else in place, there is no switch in unforeseen circumstances, we can set the default option, if we can not advance possible danger, it should provide hedging program.
II. Entropy Software
When the software code sprawl, programmers call it "software rot", indeed, in the amount of code in the software is growing, but there is no effective management, the result must be brought out of order. Blocking software entropy becomes larger and larger in only one way, that is, the amount of code is not large enough in time to manage. Inspiration broken window is: intolerable broken windows and found a broken window repaired immediately to avoid the impact of the expansion. APP assistant in the preparation of the course, I always like the button listeners to write one, so that the code becomes very redundant, as the switch statement look neat, but did not like the beginning of a writing instrument class, when the call is not very easy to know afterwards have this awareness, but after some time you need to write code to integrate these are made one by one broken window accumulated generated. If your code is simple and beautiful, then you will continue to maintain this good coding style.
III. Stone Soup and cook the frog
As a team leader, we need a step by step to motivate his team members to give them the temptation to urge everybody to act, for a better product, leaders need to be a catalyst for these changes, but even with a catalyst, but the result is not a member of the team much-needed time, it is difficult to mobilize the people's enthusiasm. Conversely, in order to make the team getting worse, it just needs someone to slowly drag everyone morale of the team, also it allows a team to collapse.
IV. Software good enough
It can be said the world is not perfect software products, but there must be good enough, like a work of art, became need to know when to stop, stop here is to know how to balance the cost of complete software functionality, and at the time there is enough space on balance, Meng teacher is like a computer network in the class said that every algorithm requires a certain price. Engineers need to do is to balance these costs, allowing users to feel comfortable.
V. your knowledge assets
Knowledge of computer science replacement fast, the old knowledge must be outdated, it took java, before many methods have been abandoned, do not learn, can only be eliminated, of course, this is for programming purposes, If the job from the program, then the knowledge of whether the software structure also need to update it? Of course, learning is a critical process in the past eighteen years, we've learned they are being advertised is correct, but later? Carefully look back, whether or not in the end be all right, if you choose another direction, we will succeed it? Future are going to be challenges in life, who do not know what will happen.
VI. AC
This is undoubtedly an extremely important part of software engineering, and whether the team or your customers, excellent communication let each other know what we need so that they understand what your partner is going, of course, the exchange itself is a great performance art, we need the right time occasion with appropriate ways to style.