So, I’ve been going a little crazy with the analog photography lately.

I like that flickr displays the EXIF metadata to let you know what kind of camera took that photo. Obviously pictures that are a scan of photo taken with a non-digital camera do not contain that information. so, i did a quick search on the cpan and found Image::MetaData::JPEG

after reading some docs and using Data::Dumper i was able to come up with this script that sets the make and model info. here is an example I took with my Kodak Jiffy Six-20. if you find this useful, let me know…

download exif_makemodel.pl

Came across this today:

LOAF is a simple extension to email that lets you append your entire address book to outgoing mail message without compromising your privacy. Correspondents can use this information to prioritize their mail, and learn more about their social networks.

[vist http://loaf.cantbedone.org]

I havent tried this out, but it looks interesting: reformed perl. some snips:

Rather than using the cumbersome use base 'Parent' you may write:
package Child < Parent;

It is no longer necessary to fish method parameters out of @_:

    sub method($foo, $bar)
    {
        print "First param: $foo";
        print "Second param: $bar";
    }

While reading Lightning Articles over at perl.com (I think lightning articles are an excellent idea), I came across CPAN::Mini which is based on an article Mirroring your own mini-CPAN by Randall Schwartz

After search and googleing for an answer a nice fellow in #perl (undernet)
came up with the following:
@LWP::Protocol::http::EXTRA_SOCK_OPTS = ( LocalAddr => q(ip.addr) );

cool perl/python translations:

http://www.python.org/moin/PerlPhrasebook

Matt Cashner provides a high-level introduction to POE, the Perl Object Environment, examining the concepts that POE brings to bear when designing long-running Perl applications.

[read the article]

Everyone wants their Perl code to run faster. Unfortunately, without understanding why the code is taking so long to start with, it’s impossible to know where to start optimizing it. This is where “profiling” comes in; it lets us know what our programs are doing.

[ read the article ]

(an older article, but I found it quite good)

You’ve rolled out an application and it produces mysterious, sporadic errors? That’s pretty common, even if fairly well-tested applications are exposed to real-world data. How can you track down when and where exactly your problem occurs? What kind of user data is it caused by? A debugger won’t help you there.

[read the article]

Researchers at Lund University in Sweden grew “nanotrees” out of semiconducting materials, Science News reports. Lars Saumelson and his colleagues spray gold nanoparticles onto nanowire “trunks,” just a few microns in length. (In comparison, a human hair is around 100 microns thick.) Exposing the seeded trunk to a mixture of specific gasses causes branches to grow. The trunk and the branches can even be composed of different materials so that the parts have specific functions:

“For instance, in one experiment, the Lund team made trunks out of gallium phosphide and parts of the branches out of gallium arsenide phosphide. The researchers expect combinations of materials such as these to produce a light-emitting diode: The trunk would carry current to the branches, where the gallium arsenide phosphide would convert it into light. Alternatively, the branches could serve as light-harvesting structures, as in a solar cell, which would then shuttle excited electrons into the trunk.” Link