(“…and the horse he road in on”)
“What do you think of our new enterprise-wide software”
“ In terms of inventory, it’s great, in terms of job-flow, it needs some work.”
This exchange makes sense. There is some software, and I’m being asked to evaluate it. I can evaluate it in many terms. There might be a list of things that I am asked to evaluate. It might run for pages. It might be an afternoon’s work to fill in the blanks.
Then again, I might be asked the original question in an open ended way so that I will give my impressions.
Note that when I discuss the software in terms of certain issues, my discussion of these issues doesn’t prompt me to say that the issue of inventory must come first. I don’t assert to others that inventory is primary. There are a number of issues here that may be of concern. No one has asked me to say which is most important.
If the software is designed to make inventory primary, that is another matter. Then I can certainly assert that it is.
Is there a limit to the terms in which I can speak of it?
There may be a limit to a list of things I’m asked to review, but there is not a limit to possible remarks about the software. There is always room for fresh insight.
========================================
The software is a big piece of language. Written language.
How do I approach this language for a meaning beyond how it works for the people who are going to use and review it?
I could say something about how it is written, as opposed to what it does for the typical user. I could mention what I thought was a more efficient use of code in it, as opposed to a work of its competitor. I could make an argument for its efficiency just by counting lines. I could speak of its elegance in a mathematical way.
I could say that the way it is written has a meaning for the industry. That it is leading edge. Note that here my point about meaning takes the form of a forecast; it is my opinion that it is leading edge. It may turn out not to be.
What about its meaning beyond this?
Could it mean that the moon is a deity which is green cheese to its core?
There may not be a limit to possible remarks about the software, but the possibility suggested in the prior question is not one of them.
Nor is the possibility of the Rangers winning the series.
Nor is my getting married to Madonna.
Somehow none of these has anything to do with the software.
Why “somehow”?
Is there a “how”? I mean ‘how one thing has something to do with another.’
Sure, but it comes out in the individual case. I may have to say where I am going with my remark or it may get dismissed. If remarks were limited, then anyone might know where I was going with my remark.
“Well, he said that; now he has to go here.”
“No, we need to wait for him to talk.”
There is no Big Chief ‘How’.
If there were, then there would be an ultimate meaning to everything said , for we could say, once and for all, how it had to do (or not do) with everything else.
(Somewhat akin to Leibniz’s monads in his perfect world.)
(Or looking at the meaning of being as a relational data base.)
But as it stands, I may have to say how what I am saying has something to do with the software (remember 'in terms of' ), since remarks are not limited. It may not be clear without my saying how my remark matters.
So there is not a Big Chief 'How'.