[gitgud]

My personal opinion is that "Good Code Quality" is from good communication to the person reading the code.

You need to be able to explain the architecture of what you're programming, the reasons being:

- Code is processed by machines, but read by humans

- Code is read by many people, written by far fewer

- If you cannot explain design decisions, then expect criticism of it

- Naming is hard, but reading badly named code is even harder