To be a good programmer, you need to think in a somewhat mathematical way at times, but you almost never actually need to know math beyond the elementary school or early high school level.
There's was an interesting essay in the Notices of the AMS a couple years ago called "What is Mathematics For?" that explored the widespread belief that high school math is an important job skill. The conclusion was that it isn't for most people. However, learning high school math teaches reasoning, and that IS an important skill--so even though most people won't have any use for the math, math classes are important. Here's the essay: http://www.ams.org/notices/201005/rtx100500608p.pdf
I think the same applies for programming. You need to be able to reason, and learning some math is probably the best way to pick up those reasoning skills.
Let's be honest, if you're creating an application to improve or help accounting of a business, you need to know accounting. If you're creating an application for banking and finances companies, you need to know financial math. If you want to make an app that converts a business' Excel data into complex charts you need to at least understand statistics and more complex math than the 15 year old learns in school. Don't even get me started on a program that draws graphics programmatically and the need for some trigonometry in there.
Lastly, though I do a lot of backend and sys admin stuff because of the nature of my speciality at work, I spend half my time doing frontend programming and css (thank god for sass), and if I didn't have knowledge of algebra and trig I would take at least half as much time to do what I do. I know (and work with) a bunch of great programmers, but I'm still the guy people go to at work for mathematical advise when al algorithm is not behaving as it should and it mathematically complex.
I'm not trying to argue with your point though, most of the time you don't need those advanced mathematical concepts, and the important part of learning math is the reasoning aspect. i completely agree with that. Nevertheless I've found that advanced concepts can speed development and in some cases having that knowledge can make or break a project.
As a proof they showed us the list of math graduates who became lawyers, economists, statisticians, teachers, writers, business admin, and of course computer scientists.
One of the important business rules came up in discussion and they were arguing among themselves what's right or just trying to convince each other what the complicate rule really is. I was like, it's just a simple set of formulas if the problem was decomposed into smaller steps. After I told them about it, they were like, oh yeah, it's that simple.
The resulting math were very simple but the process to derive those was greatly benefited from higher level math training.
At my university, there's always an embarrassing number of Algebra 1 sections under the math dept every semester (I'd even say that just the Algebra 1 & 2 offerings make up about 30-40% of their total sessions some semesters). And if I hadn't seen some of my friends tutoring student's in those classes, I wouldn't have really believed there was a necessity for so many sections, but now I do.
People just seem to have a really hard time extracting the concept of 'thinking mathematically', from the act of doing math itself, and I'd say it's because it is so abstract; once you go past basic money/counting scenarios, the real life analogs start to break down for most people, and all they see is numbers, symbols, and mysterious rules.
Programming on the other hand, while still pretty tough to grasp if you're new to that way of thinking, seems like it might be a gentler intro to me. Not only does it tend to have a culture of more intuitive naming schemes than math, and have a faster feedback mechanism (i.e. a REPL/compiler checks your code as opposed to a math teacher), it also makes modeling more real world systems really easy early on (so people won't feel bounded to just money or whatever as their anchor back to reality), especially if the course goes into OOP at all before it's over.
This is the essence of mathematics; all else is commentary (er, details).
What I am rescuing from the article is the ability to learn beyond looking for what is the minimum that needs to be learned; the attitude of "I need to learn this, so I'll stretch my self" as opposed to "I don't need to learn this!, I can learn the least possible!, it is only useful up to this point! I have never used beyond the basics!". If this is your attitude, then good for you, but as an employer, I am not going to choose the employee that it is just looking for the minimum to learn to get by. And that attitude is the difference between a code monkey and professionalism.
This is disturbing to me because today the resistance is towards "math", tomorrow will be towards "C#" ("why do I have to learn that if I can easily scaffold in ruby?" multiple technical reasons, but the one that hit the most for programmer that are not living in their mom's basements is: Because I sign your paycheck), and the day after it would be something else. In general it reflects a problem with learning.
My comment does not goes towards math exclusively, but towards the ability to enjoy learning, and that is a color of the character.
The comments of I don't need to learn this or that (math, or whatever else) tells me more about who you are than engaging in what is the level of math that you need to learn.
Of course some egos will feel offended and call me and my high horse... then again...
You don't need to know math to program, but as you become a better programmer, you _want_ to tackle more challenging problems - some of which inevitably involve math (and knowledge in general) that you aren't familiar with. To solve these problems, you have to learn as you go and that, as others have noted, is the real hallmark of a good programmer.
To call learning "the ugly side" betrays a certain ethos, no?
And
"I guess my point is, that if you want to become a programmer, you have to be comfortable with having to learn new things constantly for the rest of your life."
So many conversations around "but I want to be a programmer, do I really need to learn math? Really, really?"
Yes, you do. But more disturbing than the resistance to learn math is the resistance to learn. Period.
What i like about the article is that, all though the writter admits there are some challenges, he does not whine about them, but instead he overcome them. Because of that, he has a good chance at succeeding in programming, or anything else for that matter.
Maybe not in 6 months... But he will get there