Sass: With Great Power Comes Great Responsibility

Bottom line: don't blame the tool, don't abuse the tool, and know your audience.

Transcript

1. With Great Power Comes Great Responsibility
2. Sass-‐Man
3. Sass doesn't create bad code
4. Bad coders do
5. That’s on us
6. That’s on them
7. What’s on us?
8. Drive a screw with a hammer
9. Feature abuse
10. Not knowing our audience
11. Sass is slow to compile
12. What’s on them?
13. Sass isn’t a programming language
14. Treat CSS as a machine language
15. @extend makes for ugly selectors
16. Duplicate media queries
17. Mixins produce bloated code
18. Always use arguments or @content
19. Nesting screws up specificity
20. Nesting brings context
21. Architecture is outside the {} — Ben Frain (http://roy.io/xxv)
22. Performance is inside the {} — Ben Frain (http://roy.io/xxv)
23. Don’t edit the damn CSS
24. Roy Tomeij @roy