The example from early on is about how Pirsig sees a beer can as a perfect shim for motorcycle handlebars because it meets the specifications of what's needed for the job (classical quality) while his friend isn't sure because it doesn't feel right to put a beer can into a BMW motorcycle (subjective quality).
The book's resolution of this dilemma is kind of hazy to me (something about cleaving a marble in half while reaching the top of a mountain?) but I think it's about how these are individually insufficient ways to define quality and you need both.
I suppose the software version of this is like: passing tests don't imply that anybody is going to want the thing you've made.
Because quality is often subjective, I'll be shocked if you can provide a generalized definition.
> One of Phaedrus' realizations was that quality is neither subjective (depending on the judge) nor objective (an objective fact, like the mass of a book in kilograms).
Sounds like a contradiction in terms, like a binary value that's neither true nor false. Unless the conclusion was that quality is a composite of some objective properties and some subjective ones.
How “well” something fits is absolutely subjective. It’s a judgement call with no objective measure.
I was picturing a requirements list of numerical ranges, which a specific unit of a product must satisfy. "How well" is what came to mind when I pictured a unit that nearly exceeded the limits of its requirements, compared to a unit that sat perfectly in the middle of the range of every requirement.
I never pictured any kind of "judgement call", and I'd hoped that would be clear, in the context that I'd set, talking about objective measurements of quality.