There are only two components to work with data structures and algorithms. Low level knowledge of the target system may allow the coder to increase efficiency, and low level knowledge of the chosen language might allow the coder to utilize "tricks" or "quirks" built in to the language (be they bugs or features is unimportant).īottom line is that the only way to make a program better is to make its components better. Unit testing helps to validate the operational correctness of the written code. Design patterns help to sort out the options, and provide an established pattern to follow when creating a new algorithm or data structure. That's where the skills, whatever the instructor wants to focus on, come in to effect. The Science part of Computer Science in programming is finding the way to create the better, or excellent, algorithms and develop the efficient data structures. Sloppy Algorithms + Mediocre Data Structures = Buggy Programsīetter Algorithms + Data Structures = Better ProgramsĮxcellent Algorithms + Efficient Data Structures = Superior Programs.
Stating that programs are built of exactly two components, data structures and algorithms, means that the only way to improve a program is to improve one, or both, of its components. Looking at the formula, however, can show how to improve the first and make it into the second. That formula does not make explicit the difference between a bad, error-riddled program and a good, error-free efficient program. A program is nothing more than algorithms acting on data structures. The Wirth formula, Algorithms + Data Structures = Programs is still valid.
0 kommentar(er)
