Raw Feed of OpenBSD's Work on Cleaning Up OpenSSL
This is an amazing timeline of how much and how quickly work can get done with a determined, dedicated team of hackers.
Here are some gems:
Continue reading Raw Feed of OpenBSD's Work on Cleaning Up OpenSSL...
Originally posted as: Chicago.PM New Website! New Meetup URL! New Presentations Project! on blogs.perl.org.
Lots of news for the Chicago.PM group! We've got a new Chicago.PM website, powered by Github, up at http://chicago.pm.org. The website is completely editable via Github using the Octopress system. We hope to start sharing resources about Perl on our website, increasing the exposure of the good tutorials and learning sites.
Continue reading Chicago.PM New Website! New Meetup URL! New Presentations Project!...
Originally posted as: Chicago.PM - Beyond grep - Expanding the Programmer Toolset on blogs.perl.org.
Last week, Andy Lester (author of Land the Tech Job You Love) came to talk about tools to help programmers work more efficiently and the 2.0 release of his Ack search tool.
Continue reading Chicago.PM - Beyond grep - Expanding the Programmer Toolset...
Originally posted as: I Bless You in the Name of the Stringified Object on blogs.perl.org.
A co-worker came to me today with a curious error message:
use DateTime;
my $date = DateTime->new( year => 2013, month => 4, day => 15 );
$date->set_time_zone("Australia/Sydney");
print $date->today;'
This code gives the error Can't locate object method "_normalize_nanoseconds"
via package "2013-04-15T00:00:00" at
/usr2/local/perlbrew/perls/perl-5.16.3/lib/site_perl/5.16.3/x86_64-linux-thread-multi/DateTime.pm
line 252.
The package "2013-04-15T00:00:00" is the curious part: It looks like a stringified DateTime, but who could possibly be stringifying a DateTime object and then using that as a package name?
Continue reading I Bless You in the Name of the Stringified Object...
Originally posted as: Thoughts while changing the API of a massive framework... on blogs.perl.org.
At the Bank we have a home-grown ETL framework that we've been using for quite some time. We recently completed a total rewrite, but unfortunately we left out a few changes. Had I gotten those changes in 5 months ago, I would have only had to break the API of about 10 modules. Today, in order to make those changes, I have to break the API of 122 modules.
What follows is an account of this ordeal, provided for entertainment value only. There will be a future post that explains some of the things I did to make this task surmountable.
Continue reading Thoughts while changing the API of a massive framework......