From small work to an expert in this book humorous language to us on its programming point of view, the book comes to us should not be penalized because of fear, and not to report the situation to their superiors, but do not hesitate to ask for it. The only positive to solve the problem is the best approach. But the report is not a problem to go to report, but should you have tried all possible ways, the results are not resolved during the reporting method. The second is referred to the changes to the code, no one is willing to modify the code in the time to write those changes is perfect code. But as to avoid stepping dirty carpet and delay the extinguishing of the rich, like, I do not want to change those codes considered perfect, will only lead to the loss of produce will gradually increase. There is the story of stone soup borrow, explains how the leadership team members for better distribution, as the story of stone soup story, we can use big plus what would be better to replace what you have to make the words, this is more effective to get the desired results. In comparison, small work to the experts this book is not so much a book programming ideas, it is more a description of programmers survival of books, not only programming like the idea, and some leadership skills and develop leadership skills. By reading the first chapter, I learned a lot of things, many of which are on how to improve their ability in practice, reduce losses, to more effectively achieve the desired results.
To the craftsmen like thinking tools are added regularly to always look for better ways of doing things.
We are willing to go beyond the limitations of the letter to the applied development environment (IDE).
Programmers all day dealing with the editor, the editor must take ultimate use, choose a powerful editor and cooked it!
Ever wanted to learn emacs, but eventually gave up because my commonly used development tools are visual studio, use the command in emacs there is a pain, a lot of ctrl, alt key combinations commonly used commands and windows of serious conflict, and finally had to Back to the vim editor, but fortunately there are easy to use plug-ins vim in visual studio, and the combination of the previous command ctrl many are still available.
Even if your team only one person, but also the use of source code control system.
Previously used VSS, later replaced SVN, also tried GIT, SVN is enough for me.
Met bug first reaction was, "That's impossible" not to waste emotion in it, it is not only possible, it has already happened.
First to compile the compiler to the highest level.
When you are able to pay attention to this bug, you may soon discover why it happened.
bug may appear in the operating system, databases, compilers, but this should not be your first thought.
After the amendment bug, think about it: Why is not found before the bug is not possible to improve the unit test to discover if this bug to find this bug took a long time, ask yourself why, next time can not be repaired quickly?? similar bug?
At work we always encounter problems difficult to solve, give us an idea of this book is important is not what you think in the box or thinking outside the box, but to find the box - to determine the real constraints, detailed point the interpretation is the face of difficult issues, to list all the possible ways in front of you, do not rule out anything, no matter how useless or stupid it sounds. Then one by one check each item and explain why not adopt a particular way. Sometimes you will find that he seems to deal with much more difficult problems than you think, and this time you've probably wrong way, you need to take a step back and ask yourself there is no easier solution.