[drewrbaker]

I run programming at a (relatively) successful digital agency in Los Angeles. Everyone has a different idea of what’s perfect in the web dev world (and I’m scared to even post this for fear of being shredded here on HN lol) but I’ve tried to keep a running list of basic mistakes I see from junior engineers over the years here: https://github.com/funkhaus/best-practices

Maybe that helps point you in the right direction.

My advice: Just do your best, pick a direction that makes sense to you, be consistent with it, and be OK with changing your approach to work with a new team.

[MonaroVXR]

>No CSS resets

Wait why?

I use style guides and bem from several companies, it seems that you come "close" to it. (No idea how to bring this in.)

But there's really an explanation why this has to be done.

[zinekeller]

Not the original commenter, but I believe it's only specific to Meyer's CSS reset and its descendants. Unless you're laboriously redefining every element that you'll be using, the costs far outstrip the benefits of removing everything and starting from scratch.

Plus, there's this tendency to not test for accessibility (I know that a significant portion of websites today aren't accessible for people with disabilities...)

Even ignoring users' concerns (which is to emphasize is plain wrong), depending on the specific reset, it tends to f*** up CSS ordering and makes debugging issues generally harder (since it clutters up everything).

[drewrbaker]

Couldn’t have said it better myself. starts slow clap

[eurasiantiger]

CSS normalisation > CSS reset