Conveniently-posed problems lead to both convenient solutions, as well as a variety of potential ancillary benefits.
One practical application of this, for those who are more business-minded, is that I have set a very clear and tight tech strategy for our team. There have been quite a few instances where posing a problem differently has allowed us to better align with that strategy by enabling us to pursue solutions that make use of our existing technology stack and in-house tooling, rather than requiring us to introduce more dependencies and spread ourselves even thinner.
I think this is why the US govt has been pushing STEM majors because there is a serious lack of people that understand 'advanced' math. I'm learning some fundamentals as we speak and it means nothing if you can't connect the dots. Understanding these concepts is the start but using them and experiencing them is where the real 'magic' happens. Except not many get that far.
Keep up the great work gaze!
It's often more complex in practice, but still, it's easy to focus too much on solving the given problem efficiently efficiently, rather than finding a simpler solution to the underlying mathematics.
Furthermore, a lot can be gleaned from understanding the _structure_ of a differential equation. Writing the equation for the RG flow of a field theory and then understanding the fixed points of the flow is crucial. A numerical solution to the RG flow isn’t really that useful.
Basically, once you’ve simulated it—-assuming you’ve done it right—-what actually have you gained? Often less than you want, and generally less insight than you could have gained had you really analyzed it.
What I’m saying is that “trivial to simulate” is only sometimes true. Ansys’s business exists because solving Maxwell’s equations are not “trivial,” and they’re linear!!
"Basically, once you’ve simulated it—-assuming you’ve done it right—-what actually have you gained? "
Usually you now have a computational model that can give answer for any valid input. This may not help your discipline but it certainly helps others. As you suggested with Ansys, there is always room for improvement on these computational models. I would guess unless there was something really wrong with the approach these improvements are going to be algorithmic in nature. Im not saying algorithms dont potentially have some good mathematical analysis behind them but something like say Barnes–Hut feels far more like a computer science data structure than some symbolic mathematical representation.
We can argue about how much time he and I put into the problem from ground zero. The thing I’m arguing is that one can spend a lot of time misusing the building blocks if one doesn’t understand them. Existence and uniqueness seem hoity toity until you try to numerically solve an equation over a domain for which a solution doesn’t exist, or you try to solve it and you get one of many solutions and think you’re done.
It’s hard to measure the value of knowing the fundamentals... especially 10 years out when it seems like you’re reusing the same tiny subset of your toolset over and over again. The fundamentals though exist as a little voice in the back of your head reminding you not to do something that won’t work.