When Wrong is Better
chromatic will be giving a talk at YAPC::NA 2012 that he describes as:
Perl 1 was a quick and dirty tool intended to solve problems with minimal ceremony. Perl 5 continues that proud tradition and extends it with our amazing CPAN.
Yet sometimes our amazing tools aren’t what we need. Sometimes we make more work for ourselves. Sometimes the monolingual purity of our conventional orthodoxy gets in the way.
Sometimes solving a problem the best way (performance, ease, simplicity, safety, schedule) means doing it the wrong way.
I’ll show examples from real projects, deployed to real users, and explain why we chose to do things the wrong way. Potential examples include:
* HTML parsing
* Database updates
* Caching and the lack thereof
* Avoiding rework
* Error handling
[From the YAPC::NA Blog.]