DRAFT
Idea: use phenomenology as a tool to judge the quality of code.
Good experience working with the code? Good code! Bad experience working with the code? Bad code!
Caveat: people’s experiences differ.
Who are on the team? What are they familiar with?
When the experience working with code is poor, should the code be changed, or does the programmer need to learn something?
(inspired by a comment on ergonomics by Oddmund)