Good programs vs bad programs

Developer Rahul Singh recently listed outstanding programs and bad programs in his personal blog: Reference Good programs make complex things look simple; bad programs make simple things complicated. Excellent programs do not need to be explained; bad programs require a lot of comments. A good program requires more time, but less time in the future. A bad program usually takes less time, but will waste more time in the future. Outstanding programs need to consider current and future needs; bad programs only focus on the present and may not work normally in the future. Excellent programs are very easy to maintain; poor programs are difficult to maintain. A good program has a longer life cycle and even has a wider application scope than expected; a bad program is almost unusable beyond its work scope. A good program is like a good habit. Its impact will last for a long time and can be solved almost permanently. A bad program is like a painkiller, and its effect is only short, most of the solutions are temporary. Good programs are neat and regular; bad programs are messy. Good programs can make people learn a lot of programming methods and experience; bad programs can only make people learn worse. In an excellent program, the reuse of the place is reused, and the invention of the place is invented; the bad program will re-invent the wheel and reuse it in a suitable place for invention. Excellent programs rely on the intuition and knowledge of programmers and have been edified by good program habits for many years. Bad programs tend to blindly rely on others' knowledge and experience without their own understanding. Good programs can easily be transferred from one programmer to another; bad programs can only be understood and implemented by the writers. A good programmer does not deliberately remember a piece of code. He relies on his logical thinking ability and understanding, and can easily improve the code in the future; bad programmers often remember a lot of code they don't understand. Excellent programs share the same features, such as simplicity, readability, and high efficiency. Poor programs have their own weaknesses. A good program takes longer to exist than a programmer. A bad program takes a short time to exist. Good Programming, bad programmingnovember 17,201 2 Some Thoughts on good programming and bad programming: Good Programming makes even complex things seem simple. Bad programming makes even simple things complex. Good programming is self-explanatory.Bad programming requires explanation. Good programming takes more time now, but less time in future. Bad programming takes less time now, but more time in future. Good Programming involves considering present and future requirements. Bad programming focuses only on the present and may not work in future. Good programs are easy to maintain. Bad programs are hard to maintain. Good programs have a longer lifespan, and may even outlast the purpose for which they were created. Bad programs have short lifespan and barely usable outside their working scope. Good programs are like good habits, whose effects last for a long time and solves the problem almost permanently. bad programs are like painkillers, whose effects last for only short time and solves the problem mostly temporarily. Good programming is clean and disciplined. Bad programming is messy and chaotic. Good programming is learned, practiced and mastered over a period of years. Bad programming is self brought, and when practiced for long time makes it even more difficult to learn good Programming. Good programming is knowing when to invent and when to reuse. Bad programming is inventing what's already TED, and reusing what can be better already Ted. Good programming is relying on your own instincts and knowledge, gained after birth of Good Programming Practice. Bad programming is relying progress on others knowledge and experience, without applying your own understanding. Good programs can be transferred from one programmer to another programmer. Bad programs can only be understood and implemented by the same programmer. Good programmer doesn' t memorize piece of code. He relies on his logical skills and understanding, and can Enhance the code easily in future. Bad programmer memorizes the piece of code instead of taking right efforts to learn it, and has difficulty In making changes to the Code. Good programs are good for similar reasons like simplicity, readability, and efficiency. Every bad program is bad for its own reason. Good Programming Concepts outlast the life of a programmer. Bad programming concepts die with the programmer. Http://www.singhrahul.com/2012/11/good-programming-bad-programming.html