Some time ago the "Pragmatic Programmer" read it.
A book ah. Not to mention there's some programming skills (word should be more appropriate)
such as
Orthogonality (high restrained, and finally to affect between two complementary modules)
Drag photoelastic or prototype (lightweight boot program, a direct target, easy adjustment)
Assertion programming, abnormal use (exposure program problem, do not hide him)
Decoupling and Demeter rule (low coupling, reduce dependence)
Algorithm data rates and Reconstruction (better code)
Ubiquitous automation (reduce duplication of code, and the code meaningless, not only makes programming more interesting, but also reduce errors)
These is a relatively advanced techniques of. For beginners who actually become less friendly. Always make too much of the limited novice stalled.
However, "The Pragmatic Programmer" also refers to several law for any phase of the programmer should be followed
1. Your knowledge assets
You should always invest knowledge capital productivity, which is fundamental you grow
Including but not limited to, regular reading, on a regular basis to learn a new language, try new tools
2. broken window principle
Any time you when you should use the highest technology of water products to complete a project, if you do not find a good design or implementation should fix it. Even if the lack of time you should at least be marked with a patch to warn and prompt developers need to fix this place.
3. marked with your label
No longer cherish luck, you are responsible to tag in place and modify. Forcing yourself to write higher level code.
mutual encouragement
