[craftinator]

A few things can play havoc with this type of measurement. One is that the way we determine the "quality" of the code is based on the current scope of the project.

If the scope right now is pull a bunch of values out of spreadsheets and generate reports on them, the highest quality code would be the most terse: it looks up the files, get the information, then displays it. If tomorrow the scope changes to "do that, but in realtime, across multiple machines", the highest quality code is the one that implemented a database and REST API.

Since scope changes all the time, we can never evaluate which set of code is the highest quality.