Task Automation
Coding conventions allow to have simple scripts or programs whose job is to process source code for some purpose other than compiling it into an executable. It is common practice to count the software size (Source lines of code) to track current project progress or establish a baseline for future project estimates.
Consistent coding standards can, in turn, make the measurements more consistent. Special tags within source code comments are often used to process documentation, two notable examples are javadoc and doxygen. The tools specify the use of a set of tags, but their use within a project is determined by convention.
Coding conventions simplify writing new software whose job is to process existing software. Use of static code analysis has grown consistently since the 1950s. Some of the growth of this class of development tools stems from increased maturity and sophistication of the practitioners themselves (and the modern focus on safety and security), but also from the nature of the languages themselves.
Read more about this topic: Coding Conventions
Famous quotes containing the words task and/or automation:
“The difficult and risky task of meeting and mastering the new—whether it be the settlement of new lands or the initiation of new ways of life—is not undertaken by the vanguard of society but by its rear. It is the misfits, failures, fugitives, outcasts and their like who are among the first to grapple with the new.”
—Eric Hoffer (1902–1983)
“Besides black art, there is only automation and mechanization.”
—Federico García Lorca (1898–1936)