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="Daniel Duffy" data-source="post: 260616" data-attributes="member: 607">A follow-on and related discussion on C++11 and using it in applications1. Pareto rule: 20% of C++ syntax delivers 80% of its efficacy.2. Some developers wax lyrical on super-cool syntax such as constexpr, too much emphasis on auto, generic lambdas. Determine why you want to use them and what the consequences are before wasting time that you may never use. Always provide a business case (time costs money).3. 25 years ago multiple inheritance in C++ was the new hype; it was in fact a train wreck. I _never_ used it because there are better ways to do software design. In fact, inheritance is neither necessary nor sufficient:<a href="https://en.wikipedia.org/wiki/Object_composition">https://en.wikipedia.org/wiki/Object_composition</a>4. There are different kinds of programmers<a href="https://forum.wilmott.com/viewtopic.php?f=10&t=99650">https://forum.wilmott.com/viewtopic.php?f=10&t=99650</a>5. Syntax for syntax sake is mind-numbing.6. Code is written once and read/modified/debugged/hacked many times for the next 20 years. And this costs $$$ and it doesn't grow on trees. It is always good to first write a proof-of-concept.7. Forget step 6 if you have money to burn.Of course, these remarks apply universally.</blockquote>