3 ms·
Yeah, I have 15 years of C++ experience, but not since 2012. So with C++11 and C++17 (and soon C++20) my skills have not aged well, even though I can still wri
by rabidrat 7y ago
Yeah, I have 15 years of C++ experience, but not since 2012. So with C++11 and C++17 (and soon C++20) my skills have not aged well, even though I can still write C++03 just fine. It's no wonder 'senior' devs prefer to use plain C, where even C11 is not that different from C99.
- ryl00 7y ago> my skills have not aged well I don't think that's necessarily the case. C++'s famed backwards compatibility, source of so many issues, is also a fabulous strength. There's nothing stopping one from writing C++03, while gradually adapting C++11 and beyond as time/circumstances permit (which is what I'm doing at my job, maintaining a massive legacy codebase while stymied by slow uptake on newer compilers by my corporate overlords...) > It's no wonder 'senior' devs prefer to use plain C Not this senior (in years, at least :)) dev. I've tasted RAII and I can't go back...
- elgenie 7y agoThe problem from Dropbox's perspective is that they're not merely hiring someone to create a solo greenfield C++ codebase, but to contribute quickly to a codebase written in whatever arbitrary subset of C++ they blessed.
- bfrog 7y agoC is just easier to keep most of the rules in your head for. I prefer C any day, especially in an embedded system.
- jjtheblunt 7y agoi agree
- PunksATawnyFill 7y agoFunny, I too stopped using C++ around 2011. Recently I had to delve into Swift and learn it with great urgency... then my project changed direction toward C++ and Qt. I find the '14 and '17 additions vastly improve C++ and in fact added things that I had just come to appreciate in Swift. So don't be too put off; learning the new stuff will help you if you need to adopt a more-recent language too.