Entering the Software Engineering I, after reading The Pragmatic Programmer feel part of this book very useful, now I read to my most valuable is orthogonal lines, that is, when you compile the project must pay attention try to involve less contact between the various parts, it will not do that when we try to change some part of the contents of the file "do not disturb" to the next folder, maintenance and updating of the late great help, also there is sure to pay attention to the code when writing code reversibility because our plan is not static, he is likely to one day in some part of it will have a finished before the project will affect, reversibility is in when this code is not applicable in the case of his deletion does not affect other code, there spoke of "tracer", this role is to receive in their own project themselves never had contact with, leading to a need in front of the beam, the light can bring you into the right path, the book will write the code likened a gunman in the dark, and very appropriate example, When their exposure to new things like sniper task needs to be done in the dark, no light is difficult to achieve snipers shot and killed, just like us, like we need some programming before programming process, the "tracer" provides us with sufficient beam (although I have not accumulated in this area, but I will from now begin to accumulate my "tracer").
There is what we need to reserve a mistake of our own code base, tools and a library, you can call your own arsenal of tools depending on the project to reduce the workload, so not only can improve efficiency, but also can reduce the code error (because tool battle-hardened when the library).