A program may direct its attention to any sort of digitally represented piece of information–as computer science progresses the things that can be represented expand over time. What in the main analytic philosophers care about are philosophical concepts which are a subset of all knowledge. Therefore by this reckoning computer programming is not applied analytic philosophy.
You are also suggesting that there is some sort of pure/applied distinction within analytic philosophy. That's unorthodox. If there were such a distinction though you're suggesting that software engineering might be the way we take philosophical formalisms and apply them to the world. I think philosophers would argue that philosophy already does that.
"As a philosophical practice, [analytic philosophy] is characterized by an emphasis on argumentative clarity and precision, often making use of formal logic, conceptual analysis, and, to a lesser degree, mathematics and the natural sciences."
That is exactly what you do when you are doing computer programming. So computer programming is the practice of applying the techniques of analytic philosophy to computers.
Read your own excerpt. analytic philosophy is a philosophical practice; computer programming is a software engineering practice.
They are not the same thing.
That's not to say that the practice of philosophy couldn't be done digitally. I'm sure over time more and more of it will. But to go from there to applied analytic philosophy is computer programming is nonsensical.
The main reason being, and I'll restate myself–philosophy is not concerned with all concepts, only a subset of them, those that are deemed to be philosophical concepts–what those are is another matter and a very very very interesting question in its own right. This is what differentiates philosophy from other fields that use the same cognitive techniques and methods, the same proscriptions and sensitivities‡ of which there are both many fields, many methods, and many pitfalls. How all the latter translates into software is one matter and is not up for debate here. What I am saying is that computer programming (as an activity, one that is done by a human to a computer) can deal with any concept and that makes it potentially much broader in scope than what philosopher's do, methodologically they can over time be made compatible–at the moment they are distant kin.
† i've made a best guess/good faith at what that's supposed to refer to
‡ what I mean by "cognitive techniques and methods, the same proscriptions and sensitivities" is the business of conceptual analysis and construction–learning about how concepts work and how we manipulate them mentally and how we communicate them, the practice of training oneself to to avoid errors in your thinking, learning about fallacies and applying them, learning to debate in good faith with yourself and others, learning about biases in human cognition, learning to spot these biases in ones own thoughts
That is exactly the issue - computing is the closest thing we will ever have to Platonic Idealism. You can create simple, elegant, symmetric worlds. Many people instead assume that whatever poorly designed programming language is around at the moment is the be-all, end-all Platonic world that they must inhabit, and then proceed to come up with all kinds of dumb workarounds because the programming language does not model whatever they are trying to express, all the while patting themselves on the back for being clever and creating "abstractions."
OO patterns do not make any kind of sense. There is no "generality" or "abstraction" about Singletons or Factories. They are made-up nonsense terms for ad-hoc techniques people hacked together to work around the problems they had trying to apply certain classes of OO languages to modeling certain kinds of problems in the real world.
So the contrast should be between different philosophic schools - if patterns (and OO inheritance) is like Platonism, what would materialism be? I think DSLs and DDD is a kind of materialist view on computer programming. And DDD's emphasis on clear and precise naming and concepts is very much what analytic philosophy is also concerned with.
Isn't this a matter of perspective, though? I've been thinking recently that programming languages are kinda like hexidecimal numbers or logarithms - essentially shorthands that allow us to handle stuff the human brain isn't built for. In this sense, object oriented thinking shouldn't be any worse than any other kind of thinking, provided the practitioner finds it useful for making the problem at hand tractable.
I can see there would be two obvious problems with this kind of relativism - if there were performance implications, or maintenance implications. But I don't see OO stuff causing these in and of itself.
Without digressing too much from the topic however, I think OO has it's place. Sometimes it's rather like constructing scaffolding prior to building a small dog house, unnecessarily complex.