Good program and poor program good programming, bad programming

Good program and poor program good programming, bad programming release time: 2012-11-20 16:32:21| read: 2,735 views

A good program can make complex things look simple, and a bad program complicates something that's already simple.

Good procedures do not need to be explained, and bad programs require a lot of comment.

Good programming takes more time, but it takes less time in the future, and bad programs tend to take less time, but waste more time in the future.

Good procedures need to take into account current and future needs; bad programs focus only on the present and may not work in the future.

Good programs are easy to maintain, and bad programs are difficult to maintain.

Good programs have a longer life cycle and even a wider range of applications than expected; Bad programs are almost impossible to use outside of their scope of work.

Excellent procedures, like good habits, will have an impact that lasts for a long time and can solve problems almost permanently; bad procedures are like painkillers, which have only a short time to solve and most of them are temporary.

Good procedures are neat and regular; bad procedures are confusing.

Good programs can learn a lot of programming methods and experiences; bad programs can only make the learning worse.

Excellent program, where the reuse of the place is reused, where the invention is invented; the bad program will reinvent the wheel and reuse it where it is suitable for invention.

Good programs rely on programmers ' intuition and knowledge, and have been nurtured by years of good program habits, and bad programs tend to blindly rely on the knowledge and experience of others without their own understanding.

Good programs can be easily transferred from one programmer to another; Bad programs are only understood and implemented by authors.

A good programmer does not deliberately memorize a piece of code, he relies on his logical thinking ability and understanding, and can easily improve the code in the future; bad programmers tend to remember a lot of code that they don't understand.

Good programs have the same characteristics, such as simplicity, readability, and efficiency; bad programs have bad places.

Good programs exist longer than programmers, and bad programs exist for a short time.

Good program and poor program good programming, bad programming