>To make a concrete example, imagine writing an application where requirements changed unpredictably every day, and where the scope of those changes is unbounde

>To make a concrete example, imagine writing an application where requirements changed unpredictably every day, and where the scope of those changes is unbounded. That sounds like software development, alright. It takes a while for domain experts to learn that if programmer ask "is X always true/false", they mean that there are no exceptions from that rule. I would like for researchers to just name variables sensibly. Even that would improve code quality a lot. Still the key problem is that there are zero incentives for researchers to even make their code readable! It does not improve any of the metrics they are judged by.