The myth of "best practice"
8 likes2,362 views
The document discusses how best practices in web development are not static and can change radically over time. It notes that terms like "best practice" may actually imply the worst approach. Different techniques for class names, CSS frameworks, object-oriented CSS, valid code, semantics, and priorities like mobile and print-first are mentioned as areas where practices have evolved. The overall message is that there is no single answer in web development and perspectives on what is best can differ depending on specific needs and circumstances.
The myth of "best practice"
- 1. the myth of best PRACTICE
- 2. Not a rave. A discussion.
- 3. practice
- 4. “best practice” often implies worst practice.
- 5. classitis
- 7. semantic
- 8. CSS Frameworks changing how we look at layouts.
- 9. object
- 10. Object Oriented CSS - changing how we structure CSS.
- 11. invalid
- 12. Before HTML5 valid code was considered critical.
- 13. emphasis
- 14. In the <i> of the beholder.
- 15. heading
- 16. There can be only one <h1>.
- 17. mobile
- 18. Changing the way we build - mobile and print first.
- 19. response
- 20. We need to think beyond the single screen.
- 21. wrapup
- 22. Our best practices can change radically over time.
- 23. There is no single answer.
- 24. Beware of those who paint in black and white.
- 25. discuss