wiki.accu.org

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

Back to [[conference:committee:proposals-2013]]\\
\\
**Title**: Worse Is Better, for Better or for Worse\\
**Proposer**: [[2013:kevlin_henney]]\\
**Type**: Keynote\\
**Duration**: 60 minutes\\
**Description**: 
Over two decades ago, Richard P Gabriel proposed the idea of "Worse Is Better" to explain why some things that are designed to be pure and perfect are eclipsed by solutions that are seemingly compromised and imperfect. This is not simply the observation that things should be better but are not, or that flawed and ill-considered solutions are superior to those created with intention, but that many solutions that are narrow and incomplete work out better than the solutions conceived of as being comprehensive and complete.\\
\\
Whether it is programming languages, operating systems or development practices, we find many examples of this in software development, some more provocative and surprising than others. In this talk we revisit the original premise and question, and look at examples that can still teach us something surprising and new.\\
\\