3 ms·
I suspect I share your frustration; the academics who teach math tend not to have a very good grasp on why it might be useful. The point is (probably, maybe) t
by roenxi 7y ago
I suspect I share your frustration; the academics who teach math tend not to have a very good grasp on why it might be useful.
The point is (probably, maybe) that nothing in programming is intuitive; all the abstractions have to be learned for a first time somewhere. A lot of math education is about cataloguing common patterns, naming them and providing an environment where students can check if they have internalised the obvious pattern or not.
This allows incremental building of knowledge between different people. So for example if someone is trying to build a Something with [Property Z] and person B points out "this is a [mathematical object X] therefore [theory Y] says the Something won't have [Property Z]" then the builder can understand the implications immediately and abandon the effort, or identify what needs to change to make the Something not an [object X]. Saves a lot of discussion, enables a lot of coordinating. You can ask an expert to check your work for [Object X]s if you never quite got confident in the concept.
A bit like how an engineer might look over another's design and say "the tensile stresses on that beam will be huge!" and the designer will be able to make a lot of assessments in an instant that would need a good half hour if the concept of tensile stresses wasn't part of a common language and the mistake-finder had to explain stress & strain from first principles.
So yeah; a lot of it probably is trivial but it saves hours of discussion and explaining out in the real world. And there is benefit in moving the explaining up early where it is dealt with in a 30:1 classroom setting and it doesn't slow down design work.