[Animus7]

How is a non-programmer supposed to understand best practices, redundancies in code, or time to implement a complex class?

I've been programming my entire life and I still wouldn't be able to tell you if a Python class follows best practices simply because I don't know enough python.

The problem is that a non-programmer can't quantify what makes a good programmer any more than a non-mathematician can tell who writes the best topology proofs.

I suppose anyone can get a feel for who "gets shit done" and who doesn't, but then you're measuring something much less tangible than "programming".

[gwillis13]

Quality is a "measure". So regardless you still have to have a basic understanding of what your considering "quality" and what isn't "quality" to you. Otherwise you just shooting in the dark.

Make sure to read my post thoroughly, even I know what the OP is asking is impossible without a basic understanding of what to measure by. I'm just giving them ideas of what to research themselves to help apply some ideas for their "quality" measure.

Also if you can't code a problem without requiring redundancies in your logic, then you might be looking at the problem wrong. This is not absolute, but there are better ways at problem solving in most cases.

edit: grammar