Home
Forums
New posts
Search forums
Online Courses
2021 Rankings
2021 MFE Programs Rankings Methodology
Reviews
Latest reviews
Search resources
Tracker
What's new
New posts
New media
New media comments
New resources
New profile posts
Latest activity
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
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!
Home
Forums
Quant Career
Career Advice
What chances nowadays to get into Quant Developer roles with a PhD in Computational Mech. Eng.
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="KillingField" data-source="post: 260407" data-attributes="member: 33740"><p>Effective Modern C++ is not outdated (it's about C++11/14), nor is Meyers syntax only (though the way this particular book opens is on some very tedious arcane differences between auto, template etc. type inference that is basically about syntax). I, however, would not recommend it to you straight out of the box as I regard the book rather advanced (unless I misremember, it does assume a passing knowledge of lvalue, rvalue, std::move etc). </p><p></p><p>What I would recommend, and I think Daniel disagrees with me here, is for you to start with the old Meyers books, in particular Effective C++. The syntax may be outdated, and it will obviously not have all the bells and whistles of modern C++, but I still think its advice has aged well and it is a good starting point of the dos and don'ts of C++. As I said earlier, your knowledge of C++ seems decades---plural---behind (the next book in Meyers series, More Effective C++ published in 95 goes into detail of implementation and usecase of a shared pointer), and Meyers' old books are basically written for someone with your background moving from "C with classes" to C++.</p><p></p><p>Now I'm not here to convince you to learn new things if you have already decided that you know better, and that ignorance is something to be proud of. I will way a couple of things though. A line cook at a Michelin star restaurant does not work with the same equipment you do at home nor could they deliver food consistently perfectly cooked, presented and on time were the operations not organized to the level of small details. The experience has little to do with that of a homr cook. Same goes for writing code. Coding is simple and doing that at home is completely different from programming, or software engineering, which is a discipline unto itself and a form of engineering, large part of it being concerned on how to do things at scale.</p><p></p><p>Rust is a new and a particularly influential systems programming language taking on C++ and fixing its flaws. Memory ownership and killing OOP as it is often (mis)used in C++ being some of its central tenets. C++ in modern times has similarly moved towards smart pointers and borrowed several concepts from languages such as Haskell. It is not simply for fun that people do this or just because someone might forget to type delete (and why this happens is not a matter of simply forgetting delete, but about the more general concept of memory ownership-for someone coding funxtionally simple noninteractive programs at home, these ideas may not come up), but for elegance and to make things work at scale.</p></blockquote><p></p>
[QUOTE="KillingField, post: 260407, member: 33740"] Effective Modern C++ is not outdated (it's about C++11/14), nor is Meyers syntax only (though the way this particular book opens is on some very tedious arcane differences between auto, template etc. type inference that is basically about syntax). I, however, would not recommend it to you straight out of the box as I regard the book rather advanced (unless I misremember, it does assume a passing knowledge of lvalue, rvalue, std::move etc). What I would recommend, and I think Daniel disagrees with me here, is for you to start with the old Meyers books, in particular Effective C++. The syntax may be outdated, and it will obviously not have all the bells and whistles of modern C++, but I still think its advice has aged well and it is a good starting point of the dos and don'ts of C++. As I said earlier, your knowledge of C++ seems decades---plural---behind (the next book in Meyers series, More Effective C++ published in 95 goes into detail of implementation and usecase of a shared pointer), and Meyers' old books are basically written for someone with your background moving from "C with classes" to C++. Now I'm not here to convince you to learn new things if you have already decided that you know better, and that ignorance is something to be proud of. I will way a couple of things though. A line cook at a Michelin star restaurant does not work with the same equipment you do at home nor could they deliver food consistently perfectly cooked, presented and on time were the operations not organized to the level of small details. The experience has little to do with that of a homr cook. Same goes for writing code. Coding is simple and doing that at home is completely different from programming, or software engineering, which is a discipline unto itself and a form of engineering, large part of it being concerned on how to do things at scale. Rust is a new and a particularly influential systems programming language taking on C++ and fixing its flaws. Memory ownership and killing OOP as it is often (mis)used in C++ being some of its central tenets. C++ in modern times has similarly moved towards smart pointers and borrowed several concepts from languages such as Haskell. It is not simply for fun that people do this or just because someone might forget to type delete (and why this happens is not a matter of simply forgetting delete, but about the more general concept of memory ownership-for someone coding funxtionally simple noninteractive programs at home, these ideas may not come up), but for elegance and to make things work at scale. [/QUOTE]
Verification
Post reply
Home
Forums
Quant Career
Career Advice
What chances nowadays to get into Quant Developer roles with a PhD in Computational Mech. Eng.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
Accept
Learn more…
Top