Coding is not mechanical work. If you want the resulting program enjoy a long, error-free and productive "life", it must be carefully thought these decisions. Do not take the initiative to think about their code, developers are programming by coincidence - the code may be able to work, but there is no particular reason why they work. Sometimes despite our code can run fast, we occasionally develop some algorithms, may make the fastest processor in trouble. We must learn the method to estimate the speed of some of the code, find these potential problems. Most non-trivial algorithm must deal with some variable input. The more input, the longer running time, or use of memory: Typically, these inputs will affect the size of the algorithm.
Do not Use Wizard Code You Don, t Understand. Do not use the wizard the code you do not understand. Wizard-generated code into a Joe integral part of the application. Code and the wizard has not been factored out, on the back clean interface - it line by line with Joe intertwined write function. Finally, it is no longer wizard code, and become Joe code. No one should make the code they do not fully understand.
Perfect, not when there is no need to increase, but reached when there is no need to remove. Little demand exists on the surface, usually, they are deeply buried under layers of assumptions, misunderstandings and political means. Demand is a statement of the need to complete something.
Write a program specification is to demand a reduction of the extent to programmers to take over the process. This is an exchange of activities designed to explain and clarify the system requirements, such as eliminating a major ambiguity. In addition to talking with developers initially realized, specifications or left to future installments record programmers code maintenance and enhancement. Specification also agreed with the user - is a compilation of demand for them, but also a hidden contract: the final system will meet the requirements of the contract.