I'm not sure your list consists of good counter examples, with the exception of the first (as the parent opened himself up to that--implementing accounting form

I'm not sure your list consists of good counter examples, with the exception of the first (as the parent opened himself up to that--implementing accounting formulas most definitely requires at least some mathematical ability, but that's a specific case). The second point isn't mathematics; it's arithmetic. The third and fourth points are really statements that are as too broad as the statement that "math is not necessary for software development". In particular, were were to employ your use of the word "algorithm" it would apply to literally any activity that can be described as a series of instructional steps. Consequently "how to make a peanut butter and jelly sandwich" becomes an exercise in mathematics, for example. As a person who comes from an academic field in science that is rich in applied (and some theoretical) mathematics, my observation is that there exists very few cases where a person writing software at almost any level actually needs to have a deep mathematical/theoretical understanding of the data structures and algorithms he employs. And I mean "deep" in the sense that he even has to understand that a mathematically-backed theory is what he's employing. This is as true for computer science graduates having a prolonged bout of anxiety and envy of mathematicians and scientists as it is for the "lowly" CRUD App Developer. At the deepest, one needs to be able to employ arithmetic to compute a rough "Big O" estimate. That's "doing math" I guess, in the strictest sense, but only in the same sense as a child "does number theory" when he writes, e.g. "10" in the blank for "9+1 = ___".