This book is recommended from our JAVA teacher, after reading it, I feel a great harvest from this book, I have seen these predecessors of experience, is also a great experience for me, is the basis for software engineering very important. We want to lay a solid foundation, not just focus on the pursuit of fashionable technology, to lay the foundation to studying those techniques or participate in some training on their own development will be better.
Most people find it difficult to accept change, sometimes for good reasons, sometimes just because of the inherent inertia in the "stone soup with boiled frog", we will examine a strategy to promote change. One understand the context of your work benefit is that your software must understand how good easier, and sometimes close to perfection is the only option, but often design tradeoffs. We will explore this issue in "good enough Software".
"Responsibility" of the term, we are intimately familiar with the initiative to take responsibility is what you are. You committed to ensuring that something is done correctly, but you may not be able to directly control every aspect of the matter, except as best you can, but you have to analyze whether the risk out of your control. For the impossible or too risky thing, you have the right not to be held accountable, you have to make a decision based on your own code of ethics and judgment.
If you do agree to be responsible for a result, you should take the responsibility. When you make mistakes or misjudgments, honest enough to admit him, and tried to give a variety of options. Do not blame someone or something else, or put together an excuse. Do not put all problems are attributed to the supplier, programming languages, management, or your colleagues.
To provide a variety of choice, not excuses. Do not say things can not do; to show what can be done to salvage the situation. Code must be thrown away? Tell them about the value of remodeling, you have to spend time to build a prototype, we have determined the best way to move forward, in order to prevent the problem from happening again? Or perhaps you need additional resources. Do not be afraid request, do not be afraid to admit you need help.
Do not tolerate broken windows (poor design, bad decisions or bad code), find a repair on one, if there is no time to properly repair it with wooden planks nailed them up, is about to put comments, take some action to prevent further damage, and explain your situation under control.
We see clean, well-run system, once the windows began to break, quite rapid deterioration, there are other factors that can decay-promoting software, we will discuss them elsewhere, but compared with other factors, will ignore more rapid acceleration of the process of decay.
Software engineering, to lay the foundation, responsible, do not shirk responsibility, do not miss a thing every bug is that we need to pay attention, only to do these things, we can have the most basic condition of the target experts.