C++ Programming for Financial Engineering
Highly recommended by thousands of MFE students. Covers essential C++ topics with applications to financial engineering. Learn more Join!

Python for Finance with Intro to Data Science
Gain practical understanding of Python to read, understand, and write professional Python code for your first day on the job. Learn more Join!

An Intuition-Based Options Primer for FE
Ideal for entry level positions interviews and graduate studies, specializing in options trading arbitrage and options valuation models. Learn more Join!

Reply to thread

Message: <blockquote data-quote="cgorac" data-source="post: 118185" data-attributes="member: 1689">Why "academia and government" are not legit?Anyway... I can speak from my personal experience only. I recently completed a project for large Oil&Gas company, with critical parts of it written in Fortran - and it was not legacy code, but instead an implementation from scratch of numerical routines used for making decisions where to drill; these codes had to execute on GPU accelerators, and we did them in CUDA Fortran.  On the other side, couple years ago I was working on a pricing engine implementation (again with time critical routines executing on GPU accelerators, but these were implemented in CUDA C), with the idea to sell it to financial institutions of various types - the business plan failed badly, and while there were various reasons why (the spread of crisis at that time etc.), I'm strongly convinced that the main reason was that the engine public interface, that was in C++, was full of sick over-complications, with heavily use of template meta-programming and alike crap. Namely, whenever we've been doing presentations, it was all rosy while we've been showing performance numbers etc., but when the presentation came to explaining the engine interface, so that it could be integrated into client existing in-house solutions, one was able to see client IT people starting rolling their eyes, and just know from that point onwards that we aren't going to make the deal.  Fast forward couple years - the engine external interface is in a functional language now, and it sells rather OK these days (with almost unchanged algorithms implementation below).Now - these are of course just personal anecdotes that aren't telling much, in particular if speaking striclty in the context of the quant finance domain. But my whole point was that it was not said in the initial post that the person in question decided to pursue career in quant finance (in which case, your advice that doing Fortran is waste of time would be certainly sound), so that with masters degree in computational mathematics there exist many other interesting application domains (some of these even paid rather well) where Fortran knowledge and experience could be significant advantages in his CV.</blockquote>

Verification