Depends on what you're doing. I've used calculus for physics simulations in games. I had to do a bunch of performance analysis, and a little bit of knowing what distributions actually meant helped a lot. I regret not having taken more statistics in college. I was talking with a philosophy prof once, and somehow we got to DeMorgan's theorem. "I use that nearly every day," I told him, and it kind of floored him -- appa…
Do software engineers need mathematics? (2000)
11–20 of 41 posts
Re: Do software engineers need mathematics? (2000)
#12The thinking is similar too, they're not isolated.
I personally think a large amount of value is in using artificial intelligence, machine learning and statistics to analyse data to optimise a business. I think future grads should be focused on that.
Re: Do software engineers need mathematics? (2000)
#13Re: Do software engineers need mathematics? (2000)
#14Good article. I would just add that Philosophy classes especially the more abstract 19th (Kant, Hegel, Schopenhauer, Nietzsche) and 20th century (Heidegger, Foucault, Mearleu-Ponty, Wittgenstein) philosophers are fantastic and often under appreciated tools for gaining deep abstract thinking skills that mathematics didn't teach me. Often times I've drawn on the modes of thought acquired from learning to read them when…
Re: Do software engineers need mathematics? (2000)
#15Interesting. Ultimately just one person's opinion. I don't use any college math (since I didn't take any) and dont't find a need for it in most programming. In fact, programming is a lot more like writing. Maybe that's why they call it a programming language. Too bad when I was doing programming using more interesting math, more interesting math was not taught in school (US 7th grade and on)
How do you know? It is not impossible to pick up (some of) that knowledge outside of college.
"Maybe that's why they call it a programming language"
Maybe, but it could also be because of the abstract concept 'language' as used in http://en.wikipedia.org/wiki/Formal_language
Re: Do software engineers need mathematics? (2000)
#16He has a point, but after learning about the numbers and basic arithmetic you certainly have enough knowledge to learn to code, and who really knows if you need to know more math than that.
Re: Do software engineers need mathematics? (2000)
#17Re: Do software engineers need mathematics? (2000)
#18Depends on what problems your tackling. If your doing a basic crud website then no. However if you want to analyse customer data on that crud website, and provide recommender systems for it then yes. The thinking is similar too, they're not isolated. I personally think a large amount of value is in using artificial intelligence, machine learning and statistics to analyse data to optimise a business. I think future gr…
Re: Do software engineers need mathematics? (2000)
#19Re: Do software engineers need mathematics? (2000)
#20I don't really buy it. I think practice with tackling bigger and bigger problems teaches you more about the need for the specific kinds of abstractions that are most useful for SE. When you get to problems that are too big to fit entirely in your head, you start realizing the absolute necessity for hiding implementation details, and when you work over time with other people using your code, the similar necessity for…
Reading and writing code does not teach you recursion. Certain abstract ideas fall into the domain of mathematics even if you can pick up some of them outside of a formal mathematical education.
That said, a lot of the higher-level stuff I learnt the hard way, like the difference between tiers and layers. That's abstraction. And it's why I disagree with Keith's post in general, and this comment in particular:
"...mathematics was the only subject that gave them that experience..."
I don't need maths for 99% of what I write.
[Edit] I don't dispute that I'm doing it (mathematics). I do dispute that an expensive maths education is a requisite for good code.
Good of course is an interesting word - there's a difference between the best architecture, the right architecture, and a successful architecture. All can be termed as being "good" architectures, but no amount of maths is going to teach you the difference.