Happy Birthday, Paul!

Got my new Canon 5D Mark II camera, and took some pictures at a party in a dark restaurant.

ISO 6400, F/4.0, at a mix of 1/10s, 1/20s, & 1/30s, handheld, 105mm except the wide shot, 24mm. Lenses with Image Stabilization are a good thing.

The real reason people hold birthday parties:

Never leave out the party organier:

Comments

Perl5, Moxie and Enumurated Data Types

Moxie - a new object system for Perl5 Stevan Little created the Moose multiverse to upgrade the Perl 5 programming language's object-oriented system more in line with the wonderfull world of Perl 6. Unfortunately, it's grown into a bloated giant, which has inspired light-weight alternatives Moos, Moo, Mo, and others. Now he's trying to create a modern, efficient OO system that can become built into the language. I've seen a few of his presentations at YAPC (Yet Another Perl Conference, now known as TPC, The Perl Conference), among them ‎p5 mop final final v5 this is the last one i promise tar gz While the package provides some POD documentation about the main module, Moxie, it doesn't actually explain the enum package, Moxie::Enum. But delving into the tests directory reveals its secrets. Creating an Enum package Ranks { use Moxie::Enum; enum by_ARRAY => qw( unused 2 3 4 5 6 7 8 9 10 J Q K A ); enum by_HASH => { 2 => 2, 3 =...

AI crap at 100 words a minute

I requested an AI to create an astable multivibrator that can oscillate at 100KHz with a 50% duty cycle. Of course, this isn't an essay topic, it's a (trivial) electronic circuit. But it set out to provide the required number of words without actually saying anything useful. Here's what came out ... Note the reference to an article from 1968, long before any modern technology. In particular, getting through several paragraphs about oscillators without mentioning the 55 timer ic is unimaginable.

Better Performance Through Transposition

Both Perl and Javascript implement only one-dimensional arrays. To represent a matrix you need to nest arrays within arrays, typically one array for each row, within the overall matrix array. Each element of the result matrix is the product of one row from the first matrix, and one column from the second. Going from one element to the next in the same row is much quicker than going to another row. The first matrix only changes rows once for each row, N changes, but the second matrix has N^3 changes of row, one for each multiplication. If we were to transpose the second array, turn the rows into columns and columns into rows, the multiplication could be carried out by by scanning along a row instead of going from row to row.That reduces the cost to N^2. How much will that save us? I transposed the second array while reading it in: for my $size ( keys %vars ) { my $filestub = q{M_} . $size . q{x} . $size . q{.}; my ( $f1, $f2 ) = ( $filestub . '1', $filestub . '...

If you aren't Happy
Which Dwarf Are You?

Search This Blog