Making accessibility an important core tenant of your company is one way to make beginners care about it :) emphasize how it's key, don't let inaccessible code get merged to production, and accessibility will quickly become a habit/part of the development process.

Hi Michael! I say, avoid existing frameworks if you're working for a company. You should be building your own framework that fit your needs without the cruft of pre-existing solutions. This way, you can tailor your solution to your needs and use your own pattern library. I think CSS frameworks are good for prototyping -- this means, initial product iterations or 36-hour hackathons. Please, please invest in some design and UI development to then build a custom solution when there is a product at hand. I think the answer, as usual is: it depends. Are you building a prototype for a hackathon, or are you building a product? Hackathon: yes, product: no.

I'm not a very qualified person to give advice on career changing 😛 but I guess I would give the same advice as someone starting in this field -- get a good grasp on the basics and build as much as you can to practice and improve your skills.

I think consuming a lot of content goes hand-in-hand with creativity. When you consume content, you make connections of your own that string the pieces together and come up with new ideas or interpretations. These little bits of inspiration help you to stay creative. And also, its not about coming up with creative ideas (humans do that regularly throughout the day), but executing on them. And the executing part I can definitely pin to writing down these ideas, and working them into a to-do list.

I love CSS 😀 But if I had to pick a few things I love a little less : You can't label interaction style changes in CSS (i.e. there is no ::toggled pseudo-selector) Support may lead to non-uniform vendor prefixing (which is a problem especially if you're writing vanilla CSS) It's not very DRY (i.e. in vanilla CSS you have to rewrite classes to target pseudo-states)

Sleep! Take breaks! Travel! Learn a new skill (particularly an offline skill, such as calligraphy or woodworking, may be useful). And switch up your front-end-related tasks if you can.

Start with contributing documentation and with issues that are labeled help wanted or intro PR . There are some great resources to help people find projects who are looking for beginner contributors like Your First PR and some great open-source projects always looking for beginner help like Hoodie . I think the main thing with open source is: start small. A little bit can go a long way and build your confidence to make larger contributions.

Get on email lists and actually read them ( Codrops is a good resource, there is also CSS Weekly , Javascript Weekly , and many others. I also recommend making time to either attend a conference or watch conference talks at home. Cue up a few on Youtube and spend a few hours watching/discussing with a fellow tech friend. Most of all, practice -- side projects are key! If you want to learn a new skill, build something using that skill. This will force you to find resources and answers.

Haha I wanted to be a fashion designer 😜. In high school I discovered the Wacom tablet and Adobe Flash, fell in love with Actionscript, and didn't realize that I had secretly been coding all my life (Neopets, Myspace, etc.). It seemed that front-end development was a natural fit. More on that here

The web will always be a changing entity. I've learned that the only way to be happy working on it is to embrace that change as an interesting challenge and continue to move the web forward. Always stay on top of emerging technologies, but don't let them overwhelm you. There's no way to become an expert on everything , but that doesn't make you any less valuable of a team member.