|Perl: the Markov chain saw|
Short answer - yes (and yes).
Longer answer - for the very reason you cite - analytical skills.
This results in a "code-first, maybe-figure-things-out-later" attitude (for both coders and managers) that leads to demolished productivity and a bad name for the profession. In fact, a number of programmers I've met are afraid of analysis/design work. We fear what we do not understand. Had they taken Math, even something as simple as Linear Algebra or Advanced Calculus, they would be more secure in their capabilities to attack and solve problems.
The reason why Philo would be better is that, unlike Math, you have to be able to handle problems expressed in English and parse them to their logical equivalents. This is the exact skill I use when handling customer-written requirements. Without that training, I would be lost.
(For the record, I have a double major in both Math and CompSci, with a should've-been-completed minor in Philosophy.)
Don't go borrowing trouble. For programmers, this means Worry only about what you need to implement.
In reply to For CIS, Math is good, but Philo is better.