Developers define code quality in terms of readability, structure, and documentation.
Other than *Empirical Software Engineering*, what journals do you find most useful for developer productivity and enablement?
Anil Vaitla and I were emailing back and forth about this at one point, and we realized that there are different audiences for "code quality". Someone who's debugging the code wants a lot of intermediate variables to make it easier to inspect things. Someone who's reading the code for understanding wants code that's well structured. The author just wants to get something working, so their code is more likely to look like a Jupyter notebook, full of little explorations, commented out sections, etc. Optimizing for performance is a whole other category... and so on