If you see "HTML5 & CSS3" and expect IE6/7/8 relevance, then you are pretty much always going to be disappointed. For some of the features there there is no "graceful degradation" there is only "having two code paths, one for IE-old and one for everything else" or "left IE-old in the dust".
Spent a solid year fighting that reality and now I completely agree.
My company has recently decided to ditch support for IE6-8 when we roll out a new front-end design (and a handful of features). Any time our CEO and designer would dream up something new, they would come to me about, and would leave with an asterisk slapped on it which read "except in older IE". It prompted us to really dig into how much of our user base was even using IE6-8, and it was shockingly low. Shocking when you consider that many of our users are restaurants, who often just have a machine in the back running Windows WhoCaresHowOld Edition.
Exactly. It's too easy to find a job when you're a dev, you really get to chose where (including remote) and what to work on. I don't understand devs who keep working on jobs they hate.
No guide will cure that... Your two options are to learn in your own time if you have any free, or find a job for a company that offers some career development (or just has clients that allow it to work to more modern standards).
