Stop Building Monoliths!*
All I needed to do was validate a postcode, and validating non-US postcodes can be tricky, so I didn't want to write that code myself.
The first link was to a library, and it did postcode validation!
Then I read the documentation. Postcode validation was a method. Of a form object. Not a HTML form object, but the library's form object. I'd have to import the whole framework, and rewrite my application, just to validate postcodes.
Hold on here: postcodes are strings first, and maybe form elements later. But wouldn't validating a postcode be a method on a string?
My last tech conference talk was at the 2013 YAPC-NA introducing MVC on the client to Perl devs. I've participated in numerous panel discussions at WisCon, Potlatch, and WorldCons.
- Title: Desigining for Renaming
- Track: Culture
- Room: B204
- Time: 4:45 – 5:30pm
Renaming yourself is never easy. In Santa Clara County in the State of California, to file a petition to change one’s name costs over $400, and may take six months or more. Then one must change one’s name (and possibly one’s gender marker) on the dozens of sites and services one uses.
On many sites, that’s easy, I go to preferences and edit my name.
But then the site addresses me as “Mr. Emma Humphries,” oh really?
Other systems will correctly greet me as “Emma” when I log in. But still call me by $DEAD_NAME when they send an email.
This brings us to the first best practice:
When I change my name in one place, change it in all the places.
- Speakers: Emma Humphries