3 ms·
Lot's of theorems to use, and lots of proving your design is sound. If you've actually tried to build an actual bridge you'll know that that is just a small, b
by dagw 13y ago
Lot's of theorems to use, and lots of proving your design is sound.
If you've actually tried to build an actual bridge you'll know that that is just a small, but very important, part. Getting the structural math right is necessary, but far from sufficient, for getting a bridge built. You've also got bridge and landscape architects designing how to make the bridge work in the existing landscape, you've got traffic and city planners working on exactly where the bridge should start and end and which roads it should connect to. You've got traffic analysts trying to work out the traffic flow implications on the large area based on the different placements of the bridge. You've got building engineers that are trying to work out how to build this thing on time and on budget. You've got logistics people working on designing the building schedule so that the right amount of people and building materials get to the right point at the right time. And then there are the finance people and the insurance people doing their magic money dance in background. Oh and lawyers arguing about land use and building permissions and whatever else lawyers like to argue about. And each of these decisions feed back into the structural calculations, and the results of these calculations feed back into all these parts and so on. And yes there is math involved in many of these steps, but that doesn't make the whole process a field of mathematics. Not everything that uses math is mathematics.
PS: While I've never had the word "mathematician" on a business card, my Masters was in mathematics and much of the work I've done has involved modeling and data analysis, so I know in broad strokes how math gets done.
- loup-vaillant 13y ago> Not everything that uses math is mathematics. Of course not. And I never intended to say so. I originally said that "programming is applied math" (I insist on "applied"). Because if you ignore the math behind programming, you're running into trouble. Same goes for bridge building, by the way: you can't ignore math. It's like Dracula: you may not see it often, but it is ever present, and influences everything. (I'm not talking about the laws of physics here, but about a bunch of people doing math, then using the results to make far reaching decisions.) Saying that programming is a branch of mathematics is a stronger claim, but not such an outlandish one either. After all, it is all about the manipulation of a formal system. But I wouldn't go that far. Rather, I'd say computer science is math (not applied, just math).