We talk about Best Practices as though somewhere there exists an “ideal” way to write software, and we just need to discover what it is. When we do it will probably be bullet-shaped and silvery. This is at best a naive and at worst an irresponsible way to approach anything, especially writing software. This keynote explains why the term “best practices” is inherently flawed, and suggests some more useful ways of sharing experience and evolving what we do.
