In that case, skip to c++14 immediately and try your best to use as much from it as possible as that will erradicate a bunch of unpleasancies you've become accustomed to. Really it's almost like a new language (and yes that comes with it's pros and cons) compared to pre-c++11. Once I realized that I've tried keeping the mindset 'first check if c++14 added something for dealing with this, before writing any code' for nearly everything I write (in practice: search, land on cppreference.com and/or stackoverflow.com, read). In the beginning that costs time but I'm pretty confident I gained that back already because the knowledge it gives you enables to write better code, faster.
Write yourself a side project using as many features as you can.
Or write a cheatsheet (multiple pages) for C++11 onward, taking care to detail example cases of each new item or construct or keyword.
You'll know no end of idiosyncrasies in no time.
Remember, that was ~6 years ago and that's a long time. If we're still writing C++2003 and haven't fully looked into C++11 and beyond or learned swathes of it (like many many many of my colleagues and C++ devs I meet, some of whom call it C++0x), that means they're working to a spec 14 years old (C++2003). 14 years old is a teenager.
The updates are definitely improving the language, so no need to be tired of them.
Many things have become easier, or in some case much, much easier, to do since ++11. And some things that were previously nearly impossible are now intuitive and fluent.
