Applied Mathematical Programming (1977)
web.mit.edu
Applied Mathematical Programming (1977)
1–10 of 57 posts
Re: Applied Mathematical Programming (1977)
#2Re: Applied Mathematical Programming (1977)
#3Has this been updated since 1977? Because the field and tools and even the view points have changed a ton.
Re: Applied Mathematical Programming (1977)
#4Has this been updated since 1977? Because the field and tools and even the view points have changed a ton.
Re: Applied Mathematical Programming (1977)
#5 Model Building in Mathematical Programming by H. Paul Williams (5th Edition)Re: Applied Mathematical Programming (1977)
#6Has this been updated since 1977? Because the field and tools and even the view points have changed a ton.
Re: Applied Mathematical Programming (1977)
#7Has this been updated since 1977? Because the field and tools and even the view points have changed a ton.
For example all of the "hard" leetcode problems can be casted as math programming ones. But the interviewers will not appreciate this solution approach lol.
Once you conquer the logic/language then learning the tools is the easy part.
Re: Applied Mathematical Programming (1977)
#8This is from 1977. I suppose it's ok for fundamentals but you can probably do better going with a modern text like Model Building in Mathematical Programming by H. Paul Williams (5th Edition)
Re: Applied Mathematical Programming (1977)
#9Has this been updated since 1977? Because the field and tools and even the view points have changed a ton.
The tools probably have changed but the fundamental language is the same. The same way that you need to wire your brain to see how a problem can be casted as a dynamic programming one, you also need to learn how to formulate problems as integer/linear programming ones. For example all of the "hard" leetcode problems can be casted as math programming ones. But the interviewers will not appreciate this solution approac…
I once witnessed a programmer with a PhD in Maths find closed form formulas for a lot of questions where it was expected to write some code with loops building/accumulating a result. As a simple example, to explain what was going on, if the question would be "calculate the 100th fibonacci number", she would just use Binet's formula to do so (as opposed to using a loop). I was rather impressed how often that happened.