Separating Code and Semantics for Maintainability
There is no lack of mediocre code. Advances in Artificial Intelligence give us a vast supply of it. To ensure that systems built from it improve rather than degrade, this work focusses on correctness and maintainability. Traditional wisdom says less code is more maintainable. Code becomes maintainable by removing unused code, generalizing functions to reduce code duplication, and occasionally even dropping features. Maintaining code is traditionally like maintaining a restaurant menu, less like maintaining a recipe book. We aim to change the traditional approach to maintainability by introducing a recipe book.
A recipe book can be maintained in the way that scientific knowledge is maintained: By adding to it. For example, new algorithms do not invalidate old algorithms. Similarly, new definitions do not replace old ones. We proceed with multiple, possibly interchangeable, definitions and algorithms.
Extended abstract (Separating code and semantics for maintainability.pdf) | 200KiB |
Mon 8 JulDisplayed time zone: Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna change
11:00 - 12:30 | |||
11:00 30mTalk | Separating Code and Semantics for Maintainability Research papers File Attached | ||
11:30 30mTalk | Practical Source Code Weaving for Distributed Workflow Abstractions Research papers P: Silviu-George Pantelimon National University of Science and Technology Politehnica Bucharest, Radu Ioan Ciobanu National University of Science and Technology Politehnica Bucharest, Ciprian Dobre National University of Science and Technology Politehnica Bucharest File Attached | ||
12:00 30mTalk | The Algebraic Structure of Parametric Array Theories Research papers File Attached |