Software developers for years employ object-oriented methodologies (OO) for application design. Leaving aside some “conceptually pure” OO’s issues and problems, it would be worth to mention that OO methods share with audio reviewing the very same basic concepts: Encapsulation, Inheritance, Abstraction, Polymorphism, separation data into the unit of definition (classes) and so on. Make your own mental efforts to think further why.
Interesting that object-oriented methodologies do not exist in Realty and they are juts the subject of algorithmic processing of deferent business tasks. The object-oriented methods are juts the processes’ extrapolations that are explicitly pre-structured for alertness of machinery in order to let machinery to process the tasks more efficiently. While doing the “OO processing” the machinery eliminates from the actions any humanly interpretable understanding but instead it present to a human just finally “swallowable” and understandable results. The audio reviews do the same but here is a catch: during software processing an average human (not a software engineer) do not care about reasoning but rather only about the final outcome. However, in case of audio reviewing a person does not case about the results but rather about the cognitive sequence of mental efforts that made a reviewer (or a “critic” to be more precise) to surmise his/her decisions.
So, could the Object-oriented audio reviewing be even theoretically humanly beneficial? From the pleace where I stay I do not think it could, even theoretically.
Romy the Cat
"I wish I could score everything for horns." - Richard Wagner. "Our writing equipment takes part in the forming of our thoughts." - Friedrich Nietzsche