> You are using all of the above whether you know it or not when programming in a high-level language.
Exactly. The average programmer doesn't have to know the math behind things like types to use them.
> The real value comes when you do it with the knowledge of the mathematics in hand because then it allows you to prove your Program as "Correct" (w.r.t. a specification).
I don't think the average software engineer does that or would benefit from doing it. I certainly don't.
> I don't think the average software engineer does that or would benefit from doing it. I certainly don't.
Again; you are drawing the wrong conclusions and projecting your own ignorance on others.
To give a simple analogy; anybody can swing a baseball bat at a ball. But that won't make him a notable player. To become a superlative player one needs to understand body dynamics and train scientifically. In a similar vein, anybody can muddle through and come up with a Program. But more often than not, it will be error-prone and bug-ridden not to mention hard to extend and maintain. Given the importance of Software to our modern society this is not what we want. A little bit of knowledge of Mathematics behind Programming gives you orders of magnitude return in software quality which is absolutely worthwhile.
There is nothing to debate/argue here but merely pointing out the application of scientific method to software engineering.
> Again; you are drawing the wrong conclusions and projecting your own ignorance on others.
I reject your accusation. It's more likely that you are the one who is projecting, namely your ignorance of what the average software engineer is doing.
Your opinion has zero basis in facts and betrays some serious ignorance of Scientific Method. No educated person can deny the importance of Mathematics to our technologically advanced society today. Computer Science is a subfield of Mathematics and Computer Programming is the application of principles and concepts studied therein.
As mentioned earlier, the point of studying Mathematics for Computer Science is to make your "average software engineer" better and more productive than he/she was in the past.
Exactly. The average programmer doesn't have to know the math behind things like types to use them.
> The real value comes when you do it with the knowledge of the mathematics in hand because then it allows you to prove your Program as "Correct" (w.r.t. a specification).
I don't think the average software engineer does that or would benefit from doing it. I certainly don't.