I get paid to do css. If you write your own CSS for a while, get used to the syntax and solving certain problems that popup. display:block and position:relative

I get paid to do css. If you write your own CSS for a while, get used to the syntax and solving certain problems that popup. display:block and position:relative for example are always things I try when something doesn't behave. Then make sure you are able to code around bootstraps constraints and defaults. bootstrap is very popular. I tend to do smaller sites where performance / downloads isn't an issue even on mobile. For a site with a lot more users, people can optimize all day and it will all be worth it. If you can get very familiar with bootstrap out of the box you can start to rip out the things you won't / never use. one way I deviate from a lot of the popular frontend trends is I don't really like using preprocessors (LESS SASS) for projects. I totally get the benefits but the drawbacks of confusion within a collaborative environment offset the benefits. My experience, teams of coders have various skills and build processes and have to pick up slack across many projects, I don't want to enforce another level of abstraction unless I'm certain it will pay off for everybody and be easy to get going. So far, I see enough drawbacks that regular CSS is better when you're out for the week sick, or bringing on some outside help for overflow work. But if you've got a small team and every one agrees on it and can and will back each other up with that same process, have at it. I've never met those people though.