Your Work in Open Source, 3 years of Incremental Change

Chris DiBona (Google, Inc.)

Google crawled 40 million files in Google Code to generate statistics on what’s in there. Lines of code and numbers of commits are not the most useful of metrics but that’s what they have to use.

The Gnu General Public License is the most used license, at over 50%. Of those, more than half have moved to GPL version 3. Perl has declined a bit, but C has the most use, at about 40%.

Many companies are committing code, too.

Mayor Sam Adams

Sam Adams (City of Portland, Oregon)

Last September, Portland adopted one of the first Open Source policies in the nation. They’ve committed themselves to open software, open data, and Open Source in the procurement process for software.

It’s pretty cool when a politician gets it.

Situation Normal, Everything Must Change

Simon Wardley (Leading Edge Forum (CSC))

Simon started with a recap of the talk he gave last year, which showed correlations between the ubiquity and certainty. All technologies follow the same curve, from having both low ubiquity and certainty up to having both high ubiquity and certainty. The stages tend to be the innovation of a technology, the productization, and finally the comoditization.

The basic idea was that the cloud, as it is known, is still in its infancy. As it matures, we will see innovations built on it at an accelerated rate. If we don’t pay attention to it, we’ll be left behind.

Well defined processes stifle innovation.

Projects or teams can be organized by lifecycle: innovation, leverage, and commoditize. This circles back on itself. When one thing is commoditized, a new innovation can be built on top of it.

Larry claims that so rarely does he talk about Perl in the States of the Onion addresses that he has brought his conscience with him today to prod him in the right direction (the aforementioned angel and devil).

The current state of the onion is segmented into left, central, and right sections. It can be labeled, say, 5 and 6. They can also be labeled 0 and 1, for false and true. Larry then asked a series of boolean questions, asking the audience to weigh in on the veracity.

Do you think Perl 5 and Perl 6 are really the same language?

Do you think Perl 5 and Perl 6 are really different languages?

As the angel and the devil argued, Larry pointed out that an important skill for a language designer is to be able to stay on the fence long enough until he can determine which side the grass is greener on. Sometimes you discover that you’re sitting on the wrong fence and the voices in your head start to argue about which side has the greener grass.

When the voices in your head start arguing if the purple cow eats greener grass than the brown fence, it’s time to see a doctor. Or find a better drug dealer.

— Larry Wall

This is, of course, a metaphor for being a language designer. Sometimes you sit on the fence for language features, without ever knowing which direction is the better one.

Next up is a live demo of Perl 6; or, more specifically, of Rakudo Star, which is scheduled to be released next week. Some of the demos, without comment:

.say if 6 %% $_ for 1..^6

[+] gather { take $_ if 6 %% $_ for 1..^6 }

[+] grep { 6 %% $_ }, 1..^6

~[+] grep 6 %% *, 1..^6

-> $n { $n == [+] grep $n %% *,  ..^ $n }

-> $n { $n == [+] grep $n %% *,  ..^ $n }(6)

At this point, the examples scrolled off the screen due to a “whatever” example being run. That’s good news, though. It means Rakudo Star supports lazy lists and, as such, we finally have those infinite lists we’ve been promised:

0, 1, ... *

The whatever star can, in addition to being used as in an infinite series, can be used to curry a function:

(1, 1, *+* ... *)[^20]    # Fibbonacci

(0, !* ... *)[^20]        # 0 1 0 1 0 1 ...

In a recent video interview, Larry was asked, if he were hit by a bus, has he designated anyone to be his successor as the leader of the Perl 6 project? His response was that he trusts the Perl community to choose the right person.

Onions can make you cry, so can disruptive technologies or innovations. Almost everyone has labeled their technology as disruptive. As such, the phrase has lost most of its meaning.

A disruptive technology simultaneously does something worse and does something better than its competitors. In a time of the Unix philosophy of “do one thing and do it well,” Perl came along and attempted to do everything, but didn’t necessarily do any of it well. The Unix philosophy was broken by its own utilities. No one knew what a “thing” was, and no utility of the time did it well. By the time Perl 4 turned into Perl 5, it demonstrated that a tool that was itself an entire tool shed could run circles around shell scripts.

In California, we once had many, many colonies of ants. Now, most of California is populated by a single colony of Argentine ants. This is because the colonies have forgotten how to fight with each other. Perl 6 has benefited from multiple teams creating multiple implementations, in the end working together to create a better product, even if that product takes longer to complete.

If you don’t like Camelia, you can just fork off.

— Larry Wall

The takeaway, I think: It is up to all of us to determine what Perl 6 will be. What kind of disruptive technology will it be?

Ever since I saw An Illustrated History of Failure two years ago, I’ve made it a point to see @pjf‘s talks. That’s how I find myself in his mid-afternoon session, Awesome Things You’ve Missed in Perl. Judging by the size of the crowd, I’m not the only one. However, I won’t attempt to pass along his humour in this post. I’d never do it justice.

In his introduction, Piers Cawley asked that we go wild when Paul took the stage, so the folks in the Google Wave session next door would be taken aback, and realize that Perl is not, in fact, dead.

People are still out there writing Perl as if still in the dark ages of 2008. Paul doesn’t want us to write old Perl, but only new and shiny Perl. This talk only covers practices that have come about since Perl Best Practices was released.

Object-oriented Perl is not awesome. Not even close. If you look at the old ways of doing it, all of them are either wrong, stupid, or both. The rest are too hard. There’s a simple way to fix this: use Moose. This module does so much of the infrastructure work of composing classes, it makes object-oriented programming enjoyable again.

Paul spent a lot of time giving a humorous, high-level overview of the features available in Moose.

The Moose module contains a huge number of extension modules in the MooseX namespace.

When I have a problem, I go down to the pub with other Perl mongers and bitch.

One of the limitations of Perl, that is exposed to Moose, is that not everything is an object. This means methods like push() or isa() can’t be called on everything. And checking types defeats the purpose of polymorphism. Enter the autobox module, which turns everything into an object. As a bonus, it operates in lexical scope. Moose exposes autobox through the Moose::Autobox module.

A module that Paul wrote, autodie, which is now included in core. This lexically scoped module removes all of the boilerplate code that goes along with trapping errors from subroutines.

Not only is Perl 5.10 awesome, but Perl 5.10 regular expressions are awesome. In particular, the introduction of named captures (via %+) made regular expressions extremely awesome.

Perl 5.10 also provides grammars in the regular expression engine. This is the basis for Damian Conway’s Regexp::Grammars module.

Referring to an article on SweeperBot in The Perl Review. However, there’s the problem of distributing a program that uses half of CPAN to users of inferior operating systems, such as Microsoft Windows. That’s where the PAR module comes in. It will pack up all of the modules used by the program, including the Perl interpreter itself if necessary, so a single, self-reliant file can be distributed to users who need it.

Remember to never optimize code. Programmer time is far more valuable than CPU time. However, when you must optimize code, profile first. The Devel::NYTProf makes profiling awesome.

Code reviews are important, but Perl programmers are lazy. Fortunately, the Perl::Critic module has read Perl Best Practices for you and will complain about where your code violates the practices in the book. At my day job, it does about half the work of code reviews for me, loudly announcing violations of the coding standards that I enforce with an iron fist.

If you find an awesome module, buy the author a beer if you have the opportunity. There’s also CPAN Ratings to leave feedback or perlthanks in recent versions of Perl.

The full title of this session is, 21st Century Systems Perl – the New Perl Enlightment for sysadmins

Introduction

While Perl isn’t dying, “PERL” most certainly is dying. This is a good thing, because it includes all the really crappy stuff, such as Matt’s Script Archive. Thank goodness for that. To be fair, this code would have been horrible written in any language. Remember, blame the artist, not the tool.

We have a very mature community, which means we also have very mature practices. We are also converging on a standard platform, even if there are more than one ways to do something.

Part 1: Minimising Developer Fatalities

As a developer, we should do what we can to make our sysadmins’ lives easier.

Right off the bat, we should use the local::lib module, which allows an application to use custom library areas without polluting the system installation areas. It can even work with /etc/skel. Matt is a big fan of using a local library path, included with the application, so it can be maintained separately from both the operating system vendor’s modules and even other applications.

Improve module installation using Module::Install.

Package modules for your distribution of choice using cpan2dist.

Improve the CPAN experience using App::cpanminus, which is amazing easy to bootstrap:

> wget cpanmin.us
> ./cpanm

Start using all of the modules associated with best practices by installing Task::Kensho.

Vendors are getting better at distributing Perl and keeping up with module releases. The Debian Perl team is the strongest, with Fedora lagging quite a bit far behind. Fedora is finally getting better, now that members of the Perl community have a say in the packaging of Perl and the modules.

After many debug sessions, Matt has come to the conclusion that mod_$lang is evil. Jamming languages into the web server is a bad, bad idea. However, actually hooking into the different handlers can be useful. Matt’s preference now is now FastCGI.

Part 2: Maximising Automation Banality

“In the systems world, shiny and exciting is not good.”

Use the autodie (in core as of 5.10) and the IPC::System::Simple modules to reduce the repetitiveness and the common errors of systems programming.

Use IO::All to fix the syntax and semantics of I/O operations.

Systems script shouldn’t need to be deployed. It should be possible to just drop the script onto a host and it will Just Work. That’s where PAR::Packer.

The full title of this talk is, Dist::Zilla – Maximum Overkill for CPAN Distributions.

Every CPAN distribution contains a significant amount of crap. It’s infrastructure used for the distribution tools.

ExtUtils::MakeMaker has been the traditional way to work on the infrastructure code. By necessity, it contains a lot of legacy, which can be cumbersome to maintain. Enter Module::Install, which can look in the expected places for the necessary information, such as the author name. But, the author still must write all the boilerplate. Module::Starter was written to address this, composing all the boilerplate on behalf of the author. There is so much boilerplate that, by default, Module::Starter also provides a boilerplate test to detect it.

Why are we doing all of this? How much repetitive work are we doing?

What can Dist::Zilla do for us? For starters, we can remove some files:

• LICENSE
• MANIFEST.SKIP
• Makefile.PL
• README
• t/pod.t
• t/pod-coverage.t

Leaving us with only our Changes file, our code, and our tests. The non-infrastructure parts. On top of that, Dist::Zilla does all of the boring distribution bits for us. It only handles the make dist command. It does not handle the make install command, which means the users who install the module don’t need all of the dependencies.

Dist::Zilla puts all of its functionality into plugins, which will be the meat of the rest of this session. It also uses a very simple INI-style configuration file.

The main command provided by the module is dzil build. This bundles the distribution, which will contain all of the infrastructure necessary for users to install the module. When building, it follows a simple work flow:

1. Gather files
2. Munge files
3. Collect metadata
4. Write out

There is no default configuration, but there is a Basic plugin bundle that will include all of the most common plugins.

What followed were examples of what the plugins can do. Of course, all of them are designed to reduce cruft—the non-code, non-documentation bits that we’re forced to maintain. The philosophy is the same one I advocate to anyone who will listen: computers are good at doing boring, repetitive tasks with derived data; why don’t we let them do more of that stuff?

I’ve followed @rjbs on Twitter for a while, and I’ve seen him talk about Dist::Zilla. I’ve wanted to try it out for a while, to simplify my distributions—both for CPAN and for my day job—but I didn’t realize until this session just how awesome the tool is. It’s a complete framework for managing Perl module distributions. Dist::Zilla will give my Laziness score a huge bump.

To be fair, this vagueness and my pessimism are precisely why these speakers have been invited to the O’Reilly Open Source Convention. Tim O’Reilly has a grand vision for the cloud, for ubiquitous computing, and the use of technology to help solve the world’s problems. I commend him for that. I hope this morning’s speakers do justice to his vision and that, if there are valuable lessons to be learned, that we learn them.

Today’s LAMP Stack

David Recordon (Facebook)

Over the last decade, the LAMP stack hasn’t been fundamentally updated. A cache, such as memcached has been added. Different languages (Perl, Python, Ruby) have been used in place of the original PHP. Even different web servers have been used in place of Apache.

Facebook created HipHop for PHP, which compiles PHP into C++. Creating native executables in this way reduces CPU use by a large factor (a number I didn’t catch).

There are alternatives for the database component in the stack, too. MySQL is ubiquitous at this point. Facebook doesn’t really use the relational bits of MySQL very much. So they have been using databases from the NoSQL family—Hadoop, according to the presentation.

David made a point I think a lot of people miss. When evaluating databases, or any other software, first look at what problem needs solving, then find a product that solves it in the correct way. Too often I see people advocating their preferred solution without even looking at the problem.

Data is the lifeblood of Facebook (and we all have our own opinions about that). They are able to use a plethora of Open Source tools to store the data, scale the data, and analyze the data.

This talk wasn’t very focused on the cloud, aside from Facebook being a nebulous site where people store their data without really knowing where it goes or how it’s used. I expect this was more for public relations, given all the bad press they’ve had. Not that anyone stops using Facebook.

Open SETIQuest – It Will Be What You Make It!

Jill Tarter (SETI Institute)

Jill started her talk by explaining what SETI is and why it exists, which I won’t go into here, since it’s just a Google search away. I used to run SETI@home a bit over a decade ago when I was in college and felt like using my computer as a space heater.

Jill is here, representing SETI, because she wants to involve the world in their search. SETI has classroom materials covered, but they are lacking in the social networking world. Jill wants people to first identify themselves as Earthlings, recognizing our place in the Universe.

SETI, with the development of the setiQuest community, hopes to use the vast resources available in the Open Source world to improve the project. These include physical resources, such as cloud storage and compute cycles, to human resources, such as programmers and analysts.

Cloudant has created a SETI stack on the Amazon AWS infrastructure.

Open Cloud, Open Data

Jean Paoli (Microsoft)

I’m always a little concerned when I see a speaker from Microsoft at OSCON. While I can imagine that there are employees at the company who genuinely embrace Open Source—and, presumably from this talk, open data—I can’t lay aside my suspicion. Microsoft does not have a benevolent history with competition, so when a representative shows up to talk about an open cloud with open data, I instinctively look for the company’s angle. What is their nefarious plan?

Jean talked about open standards and open data. Data portability, standards, easy migration and deployment, and developer choice. For some reason, when he talks about the “open cloud,” I have thoughts about Microsoft’s OpenDocument move a few years ago. Sure, parts of it were open, but the format as a whole was useless for non-Microsoft tools.

He claimed that Microsoft Windows Azure is an open and interoperable platform. I have a hard time swallowing that. The #oscon IRC channel was not kind in its commentary. A selection from the channel logs:

<b3gl> "Microsoft totally agrees..." as long as you pay your Windows, Azure and MSSQL license fees

<alapapa> standards are great…as long as they're ours

<dbrewer> wow, thanks Microsoft.  You think I should be able to use any language I want, I appreciate your permissions.

<b3gl> dbrewer: Notice he didn't say "We believe if you want to use Linux ...."

Public Static Void

Rob Pike (Google, Inc.)

Programming languages used to be relatively simple, but still fairly powerful. They’ve gotten considerably more complex and confusing. The C++ language was used as an easy target during the talk. Rob went on to bash various (in most cases deservedly) programming languages as a way to lead into what he called the renaissance of language design.

Many of the emerging languages are dynamic and interpreted, and there’s a false dichotomy that they are considered good while the static and compiled languages are considered bad. Part of the problem is that the latter class of languages are old, designed in a different age of computing.

Obviously, the end goal of this talk was to talk about the Go language, which tries to bridge the gap between the dynamic interpreted languages and the static compiled languages.

Toward an Open Cloud

Lew Moorman (Rackspace.com)

Lew’s talk was to introduce OpenStack. Rackspace took the internal software that powers their cloud and donated it to OpenStack. I wonder if this is something we can use at my day job to build an internal cloud. The stack is licensed under the Apache 2 license and they don’t use a dual licensing model, which sounds nice.

I was wrong, the talks weren’t really about demonstrating the wonder of ubiquitous computing and how we can move in that direction so much as a showcase of organizations in the cloud or using the cloud. It was really just one long commercial.

I’ve been told by those that attended the full tutorial that the first half wasn’t really worth attending. In fact, when I arrived at the beginning of the second half, I caught the tail end of the presenter demonstrating how he recreated Twitter using Cassandra, something he dubbed Twissandra. This seems to be the exercise of choice for any distributed system. In a way, that’s smart. Take a highly distributed system everyone is familiar with, explain the challenges faced by such a system, then demonstrate the effectiveness with which the software in question can solve the problem.

In any case, the second half of the tutorial was mostly dedicated to an explanation of how Cassandra distributes its data. The details and, frankly, the delivery weren’t that interesting for me, so I didn’t follow the discussion. It was too high level to keep my interest.

I still think that Cassandra is deserving of some investigation. I have a project in mind that it may be perfect for. At my day job, we have what is essentially a distributed, key-based data store. We’ve had to implement all of the data replication functionality. If Cassandra can alleviate the need to design and implement our own data replication and integrity systems, we can put more effort into the final delivery of the data, instead of its transmission.

For my final session of the day, I’m in Environmental Monitoring with Arduino and Compatibles. Since I attended the Arduino tutorial on Monday, I thought it would be fun to attend a session on using them.

The take-away points, presented up front for our convenience:

• Environmental monitoring is important
• Arduino is cheap and easy
• Small computers are fun

The Arduino is not just the chip and board, but the IDE used to program the board. It also, as I learned on Monday, has a very shallow learning curve.

Russell works for a company doing water monitoring of the Hudson River. He’s using his domain knowledge from his job to explain how one would do something similar on a smaller scale. The values he describes detecting, and the circuits used to take the measurements, are,

• Temperature
• Turbidity
• Salinity – can’t measure this directly, but salinity conducts and we can measure resistance

Now I just need to figure out what I want to monitor at home.

After a long break, an apple, a cup of coffee, and a beer, I’m back in the Perl track.

The full title of this session is, Scratching the 40-Year Itch of Inheritance with Smalltalk-style Traits.

This is not a tutorial. How to use traits is easy, but why to use them is a more complex discussion.

Inheritance is a very complex problem and an easy one to get wrong. Then people start doing things with multiple inheritance and, even if they’re not doing something deliberately stupid, they end up with diamond inheritance. Not only is this a problem, but it’s been a problem for a very long time—40 years, in fact.

Complex systems can lead to deep class hierarchies. When hierarchies are deep, in particular with a dynamic language like Perl, it becomes difficult to determine where a method came from. Even when its known where a method comes from, undesired behavior may be inherited. This becomes worse when multiple inheritance is used.

As systems grow, the problem becomes two-fold:

1. Class responsibility – larger classes are desired
2. Class reuse – smaller classes are desired

Inheritance, by itself, cannot solve this problem. So the solution is to
decouple the sub-problems.

Several solutions have been tried:

• Interfaces
• Delegation
• Mixins – incredibly popular

As expected by the name of this session, traits (or roles in the nomenclature of Moose) solve the problem far better than any of the above solutions. Much of the session involved showing real-world application of roles to clean up code at the BBC.

http://www.oscon.com/oscon2010/public/schedule/detail/13976

I finally left the Perl track. I attended Tim Bunce’s presentation on Devel::NYTProf at OSCON two years ago and, while there have been many enhancements made to module since that time, I expect this year’s talk won’t differ much from the previous one.

This session on Simple Cloud is being presented by IBM’s Cloud Computing Evangelist. The drivers behind this product (is it a product?) are the development and promotion of a standard cloud API. There is some relevancy with my day job, not only because of the possibility of using cloud services, but as a way of getting ideas for the API I develop for our engineers to interact with the batch compute system.

There are several levels of where we can work. The levels start at the wire, where we have to generate and parse data ourselves. From there, we have vendor-specific APIs, service-specific APIs, and finally service-neutral APIs. This last level is where we want to be.

The Simple Cloud API covers three areas: file storage, document storage, and simple queues. Once thought of in these simplified concepts, there really isn’t any reason the interface used by a program can’t be standardized. A program should no more need to concern itself with the implementation details of an individual cloud provider than it does the details of the file system of the computer on which it runs.

The API uses the Factory and Adapter design patterns, with a configuration file used by the Factory object to determine which Adapter should be created. These patterns are exactly what I’ve been looking at for the API I work on at my day job.

A demo of the Simple Cloud API followed. There wasn’t much to these demos. The first showed listing data stored at two different providers. The second showed queue manipulation.

After the demo, the Apache libcloud, which is getting a good deal of vendor support.

Unlike Monday, I chose tutorials on Tuesday that held some relevance to the work I’m doing. At my day job, we have a MySQL database backing a critical production system. We have spent years fighting with it and dealing with its failures and instability. I have a bias towards PostgreSQL, having used it in the past, and finding it a superior database to MySQL. That, however, is beside the point. What is pertinent is that I have been considering a complete redesign of the system, using PostgreSQL as the data source, and a tutorial on the built-in standby and replication capabilities coming with the release of PostgreSQL 9.0 is timely.

The slides for this tutorial were distributed to us when we registered. They are intended to stand on their own, serving as documentation if we later work on implementing the concepts presented here. That said, the information density of the slides didn’t at all detract from the presentation. As a hands-on demonstration, Chander didn’t project the slides very often and, when he did, only referenced them as he spent time explaining the material.

In order to better understand how PostgreSQL implements hot standby and replication, Chander first gave us an overview of how PostgreSQL manages the data a database. I’ll be brief, so this is probably not entirely correct. For efficiency, data is manipulated in 8 kilobyte pages stored in memory, in what is called the shared buffer pool. These pages remain in memory until the pool is exhausted, at which point one or ore infrequently used pages will have any changes written to disk and purged from the pool. This means that while the updates are stored in the pool, there is a (potentially long) window of time in which a crash will cause data loss. To prevent data loss, all update operations are first written to the write-ahead log (WAL) files. During a recovery operation, these WAL files can be used to play back any transactions that were lost in the crash.

Having these WAL files means that, from a given point in time, the database can be reconstructed. It’s not a stretch to shift the playback of these WAL files into real time on a secondary system. This automatically creates the possibility of a live replicated database, which can be queried in place of the primary database.

The rest of the tutorial was devoted to demonstrating how to set up and use warm standby databases, hot standby databases, and streaming replication.

I’m just back from lunch at Burgerville with Juan and Jonathan. On the way back into the convention center, I ran into Alasdair, who has been attending the hardware hacking sessions. That made me think that I may want to try to find non-Perl sessions to attend. After all, I tend to keep up with Perl news, so the sessions are of marginal usefulness. Unfortunately, nothing on the schedule looked very interesting to me. I was curious about the session on Open Source Tool Chains for Cloud Computing until I read the description. While it looked cool, it wouldn’t be useful for me in my work. The session would go through provisioning, setup, and maintenance of hosts, all of which we already have well-entrenched solutions for in my day job. So, I ended up back in the Perl track. My friends in the San Diego Perl Mongers group will appreciate that, I think.

Anyway, on to the session.

The name Perl 6 is a language specification, rather than any particular implementation. All of the references and links off-handedly mentioned in this post are available from the Perl 6 website.

Patrick is the lead developer of Rakudo Perl, which is the most feature complete and up-to-date.

Perl 6 has a language specification and a test suite. There are still many places in Perl 6 that are not being tested yet.

Rakudo * (Star) is scheduled to be released a week from tomorrow, targeted at being a useful, usable, early adopter distribution.

At this point, Patrick began to enumerate the new language features and how they work in Perl 6, such as variables, loops, interpolation, and so on. I won’t go into these here, since there are numerous places on the Web where this has been documented.

About half way through this session, I realized that “r0ml” was presenting in another room. If I’d noticed that before, I would have attended that session.

This talk could be titled something along the lines of “Lessons Learned from Project Management.”

Jesse Vincent is the current Perl 5 pumpking, which for the moment can be thought of as the project janitor.

People who say “Perl is dead” or that Perl hackers are “desperate” are behind the times.

There are a lot of exiting things happening that are not in the Perl core. Audrey Tang has said that “CPAN is the language, Perl is the syntax.” Like Piers in the previous session, Jesse enumerated a handful of things that make Perl awesome:

• Moose
• Plack
• cpanm – makes installing CPAN modules Just Work
• Devel::Declare
• Devel::NYTProf

While some of the coolest new things happening in the CPAN world, it merely scratches the surface of what is available.

About three months ago, Jesse uploaded Perl 5.12. Amazingly, no one has reported any critical regressions.

Jesse has been assured that Rakudo * will be out next week, on 29 July. However, Perl 6 will not replace Perl 5, which has paid Jesse’s mortgage for many, many years. Also, thanks to Perl 5.12, Perl 5.10 is no longer “too new to use.”

Perl 5.12 marks the latest release in the process of cleaning up the inernals and adding much desired features. Some of the highlights:

• Deprecations warn by default
• suidperl is dead
• package Foo::Bar 1.0; – better version import syntax
• Y2038 compliant – thanks to Schwern
• Unicode improvements; upgrade to 5.2
• Pluggable keywords
• Overridable function lookup
• Dtrace support
• Deprecated modules – Class::ISA, Pod::Plainer, Shell, Switch (but still on CPAN)
• Yadda, yadda, yadda operator

Jesse believes the best new thing in Perl 5.12 is the release process, including him as the pumpking. Twenty years ago, Perl didn’t use version control. He recommends learning from this mistake.

It took five years to release Perl 5.10, after burning through two pumpkings.

Before 5.12, maintenance releases contained all sorts of bug fixes and updates, but could not break binary compatibility. Doing so was a huge task, was very difficult, and, contrary to its name, is unmaintainable. Even without all this work, the pumpking’s job is a lot of work. Jesse really doesn’t want to burn out after a release of Perl.

Traditionally, the process of turning someone with the necessary skills to be the pumpking involves preventing them from using those skills and replacing them with management skills. It’s a shame.

The system is broken and Perl 5 isn’t going anywhere, so how can it be fixed? We can reinvent it, but that’s already being done by Perl 6. Alternatively, we can refactor it. There is no reason many of the skills and duties required of the pumpking can’t be delegated out to people with those skills. In effect, the most important skill and duty for the pumpking is project management.

The 5.9 releases, leading up to 5.10, were haphazard. The 5.11 releases, leading up to 5.12, have settled into a new release every month on the twentieth, with a couple of exceptions. The 5.13 series has followed suit. One of the reasons this was possible was documenting the entire release process.

Releases in the 5.12 series are on a fixed schedule, every three months. A release schedule has been created for 5.14, too.

One of the things I’ve learned working in an enterprise and my observations of the Fedora Project is that good project management is vital. Jesse Vincent is exactly what Perl needed and he continues to demonstrate that, with regular, high quality releases of Perl. What’s more, he is a good spokesman for the project, being able to come to OSCON and give a session on all of this detail in a cojent and interesting format.

After reviewing today’s session schedule, I quickly came to the conclusion that I will spend my entire day sitting in the room “Portland 256.” This is, apparently, where the Perl track is located.

Paul Fenwick introduced Piers in song, to the tune of Gilligan’s Island.

Piers switched from Perl to Ruby a while back and swore that he wouldn’t return to Perl until 6. Facetiously, the reason he switched to Ruby was the handsome community associated with it and he reason he switched back to Perl was the amazingly supportive community associted with it. He began with a point about programming style. We think of code as describing what we are doing, but in reality the majority of our code actually describes how we are doing it. This infrastructure code is noise.

More seriously, he absolutely hated unrolling the @_ variable in every function. In such a high level language like Perl, why must we pop arguments off the stack in the same manner we would in an assembly language? This leads to long subroutines, every single one containing anti-patterns designed to implement the language infrastructure, instead of the language doing the work for us.

Moose does a lot to improve writing classes, using a more declarative syntax. However, even within Moose methods we need to write the infrastructure code. The MooseX::Declare module solves this problem, giving method syntax a more declarative style. By moving the infrastructure code out of sight, we can better focus on what we are trying to do, rather than how we are doing it.

Piers proceeded to list the modules that “rock” and brought him back to Perl:

• Plack
• Devel::NYTProf
• Moose

Perl’s object-orientation absolutely “sucks.” However, this turns out to be a good thing. It allows very clever people to create modules that extend the semantics of the language. In a language like Ruby, which has a good object-orientation built-in, it’s essentially stuck. If, in the future better ideas of object-orientation are developed, they can be implemented in Perl far more easily than in Ruby. An interesting point: sometimes when the tool sucks, things are better. People develop layers of tools that enhance and extend the original.

It also helps that the Perl release schedule has accelerated.

Piers continued with a high-level, hand-waving explanation of how MooseX::Declare works. While not informative, it was entertaining. Including a video of Matt Trout attempting to hypnotize the room.

Piers ended by thanking the Perl community and expressing how good it feels to be back into it and developing in Perl again.

It’s Wednesday morning at the O’Reilly Open Source Convention, which means it’s time for the introductory keynotes. The first thing I’ve noticed this morning is how crowded it is. Certainly more so than when I was last here in 2008. I don’t know if that’s just because we aren’t being given breakfast in the expo hall this year, so everyone is crowded into the area outside the ballroom. Another thing I’ve noticed is the gender makeup of the attendees. While still overwhelmingly male, I have noticed more women in attendance this year. Diversity is good.

Without any further ado, we’re getting started.

Welcome

Allison Randal, Edd Dumbill (O’Reilly Media Inc.)

This year’s co-chairs welcomed us and talked a bit about OSCON this year. Obviously, there wasn’t a lot of content, but they did mention the Android Hands-on event being sponsored by Google tonight. I did register for that, since it sounds like it will be fun.

Keynote

Tim O’Reilly (O’Reilly Media Inc.)

First up is the namesake of the convention. Every year he presents his vision, not just for the conference, but for the future he wants to see. He has been steering his company away from being just a book publisher or a content producer, but a company trying to make the world a better place. He urges the Open Source community to think about the cloud. Don’t just think about Linux, or whatever project, but about the bigger picture and where we’re going as a society.

He is fascinated by the ability of technology to reinvent government, a concept he’s dubbed “Gov 2.0.” We fall into the cycle of thinking of government as a vending machine, something we simply get things out of, and get frustrated when we don’t. Over the last few years, he has been talking about government as a platform.

We shouldn’t think just about selling to the enterprise, but about building a better world. We all benefit when that happens.

Coding the Next Generation of American History

Jennifer Pahlka (Code for America)

The government doesn’t have to be this obscure, opaque thing we get stuff from. It can be a platform for us to work together. Currently, the majority of the municipal workforce is over 40, and a significant percentage will retire soon. This creates a huge age gap, which leads to a technology gap.

In Oakland, California, the city workers can’t search city council meeting notes online. The method of entering the data in the computer is to scan the written notes, which are impossible for them to index.

Code for America was created to encourage younger, technologically-savvy individuals to apply their talents to government. It’s designed to create technology to open up government, to make it more accessible to the citizens. It’s a little like the iPhone or Android ecosystems. Government provides the platform, essentially the data. We, the citizens, build the apps.

Keynote

Bryan Sivak (Government of the District of Columbia

Those in the government of DC are big fans of Open Source, running Linux among other projects. They’ve long talked about being committed to Open Source, partly to save the taxpayers’ money. Unfortunately, much of this commitment is all talk.

For any project used in DC, forms are required to be filled out, justifying the choice and the expense. On this form is the question, “What Open Source projects were considered?” This is often left blank and still slips through without comment.

Proprietary solutions tend to come with copious documentation and an implementation plan. Open Source projects are more open-ended, which requires people within the government to have that vision and that creativity. This goes back to the age and technology gaps mentioned previously.

It’s good that these challenges have been identified and are being addressed.

Got MeeGo?

Dirk Hohndel (Intel Corporation)

MeeGo is the result of the unification of Moblin and Maemo. It targets netbooks, handset, tablets, and just about anything designed to be more mobile than a traditional notebook. It offers a full client Linux Open Source stack, from the kernel all the way up to the user interface, including the flexibility to support proprietary devices.

Dirk went over the primary goals and philosophy of the project (to be completely open), then went on to describe the organization of MeeGo at a high level. This included both the technical building blocks and the relationship with upstream projects.

Is Your Data Free?

Stormy Peters (GNOME Foundation)

Many of us use completely Free software on our computers, some even insist on it. However, when it comes to online services, we’ve gotten lazy.

Free software was driven by two types of people. There were those who advocated that all software should be Free, that it should be available to all people, regardless of their means. There were others who used and advocated Free software because they wanted something that didn’t crash. It’s this latter It Just Works motivation that Stormy believes has caused us to get lazy about demanding Freedom from our Web services.

She asks how many of us control our own email or have alternative ways to access it if something should happen to the primary service. What if Twitter or Facebook decides to delete your account? What happens to your data? She then went through a few examples of alternative services that have open data policies, such as Identica and Tomboy Online (it’s funny, I don’t use Tomboy because I won’t use Mono).

How many of us have read the agreements when signing up for Web services? Do we know who owns our data? Can we back it up ourselves? Who owns it, both while we’re using the service and if or when we decide to delete our data?

Keynote

Marten Mickos (Eucalyptus Systems)

The shift to the cloud is causing computing to scale, both up and out, far faster and far larger than any of the previous trends (mainframes, minicomputers, or client/server).

Many of the Open Source licenses were designed in an environment where everyone runs software on their own computers, software that requires distribution to be useful. Today we’re seeing more services being offered by companies running software within their own grids. Users never run the software themselves but rather send data in and get data out.

Eucalyptus is designed to be a highly scalable platform for on-premise use. As someone who supports many thousands of hosts in many data centers, this product has intrigued me for a while. Unfortunately, I’ve never taken the time to investigate it. It’s nice to see that those behind the company are committed to Open Source, using the split model. Users are free to download and use the software, while the company sells a supported version to enterprise.

The keynote sessions at OSCON tend to drag on for a while, making it difficult to pay attention the whole time. But they are finally over for now. We have a break before the first session of the day. I’m going to try to get some work done on yesterday’s posts before starting on my long day of Perl sessions.

I’m really impressed with the wireless network today. It had its problems during the tutorials on Monday and Tuesday. Traditionally, the network becomes almost unusable on Wednesday morning. This year, however, I have been able to connect to the Internet and write this blog post without any frustration.

For lunch, I met up with some coworkers and some friends to head across the river for lunch at Old Town Pizza. I had a small sausage and mushroom pizza, and washed that down with a pale ale.

After the Arduino tutorial, having sat down for much of the day, I grew restless. I really wanted to take a walk. More importantly, I really wanted to make my way over to Rogue Ales Public House for some beer. So I called Jonathan and we made our way over there. We each started with a four beer sampler.

I started with the Chatoe Oregasmic, finding it to be a pleasant, light pale ale with moderate hoppiness. Upon tasting it, one of my coworkers commented that it was what he expected the pale ale, which he had ordered to be.

Second in line was the Double Mocha Porter. It had a faint mocha aroma, but very little of this made its way to my pallette. I could detect a hint of smokiness, if I concentrated on it.  For something advertised as a double mocha, I was disappointed.

Having enjoyed Rogue’s Dead Guy Ale in the past, I chose for my third beer the Double Dead Guy Ale.  I don’t think I was fair to this beer. The name made me think of Stone’s Double Bastard and the Double Dead Guy Ale is nothing like that. Even so, I found it smooth with a pleasant maltiness and light hop flavors.

Saving what I expected to be the best for last, I finished with the Brutal IPA While nicely hopped, I was left disappointed after building my expectations on what I consider to be its undeserved moniker. Once I got over that, I still found it to be a perfectly enjoyabl beer. It had mild malty notes and, like the other Rogue ales I sampled, it too was smooth.  I found it to be an all around decent IPA.  Since Juan wasn’t able to join us for dinner, I bought a bottle of the Brutal IPA to share with him later.

After I had finished my samples, it was the decision of those in my party that I was criminally without beer and that, to pay penance, I was to order the Issaquah Menage A Frog.  When the bartender told me it was only available in a 12 ounce glass, I suspected that an imperial style ale.  The aroma and taste soon confirmed this.  Coming in at 9% ABV, it was not as strong as some of the ales I occasionally drink back home in San Diego, but it went very well with the beer and cheese stew I had for dinner.

And now it’s late, just a few minutes until two o’clock in the morning. I should have closed my computer and gone to bed hours ago, but I refused to do so knowing that my first day of OSCON blog entries were unfinished. Hopefully, I will have more food and beer to write about tomorrow.

In the beginning, I was shamed.  While I tried and failed to follow the Linux installation instructions, my coworker, Debbie, was able to plug my Arduino board into her Microsoft Windows notebook and get the first example running.  When the udev tip didn’t work, things were looking bleak for my attempt to control open hardware with an open operating system.  Finally, a trip to Google landed me right back on the Arduno wiki at the installation instructions for Fedora.  Finally, I could upload code to my Arduino board.  After getting the initial example to work, I modified it to change the pattern of the blinking on-board LED bulb:

int ledPin = 13;

void setup() {
    pinMode(ledPin, OUTPUT);
}

void loop() {
    digitalWrite(ledPin, HIGH); delay(300);
    digitalWrite(ledPin, LOW);  delay(300);
    digitalWrite(ledPin, HIGH); delay(300);
    digitalWrite(ledPin, LOW);  delay(300);
    digitalWrite(ledPin, HIGH); delay(1000);
    digitalWrite(ledPin, LOW);  delay(1000);
}

While we were playing with our new toys, we were treated to the history of the Arduino project, some other open hardware projects, and some of the things people have done with them.  Unfortunately, I was too busy playing with my new toy to take notes on these things, so the history lesson, by way of Wikipedia, is left as an exercise for the reader.

The editor embedded in the Arduino IDE leaves a lot to be desired.  It’s like Microsoft Notepad with syntax coloring.  My coworker found a setting that forces the IDE to use an external editor.  Basically, all it does is to make the editing window read-only.  Files edited outside of the IDE are re-read when the code is compiled.  In short order, I was able to find a Vim syntax file for Arduino code files.

After the break, we were introduced to using the Arduino board in combination with a breadboard, which allows for the creation of more complex circuits.  I’m excited, because I still have the breadboard, components, and multi-meter I bought in college for a computer engineering class.  I’ve been waiting all these years to finally have an excuse to dig them out of the closet and put them to use.  The Arduino will be a fun learning tool when my daughter is older, too.

To commence our unstructured time, which would last until the end of the tutorial (and the day), we were shown a simple circuit to wire up between the Arduino board and the breadboard.  Using a copy of the first blinking code, we could acheive the same effect of blinking the external LED simply by modifying which pin was referenced.  I took this a step further and made my LED bulb pulse like the light on a suspended MacBook.

I’m glad I decided to attend the Arduino tutorial this year. I’ve just picked up yet another hobby I don’t have time for.

The version of Blender available in the Fedora 13 package repository is 2.49b, but the tutorial focused on the beta version of 2.5, which has a redesigned user interface and new and improved features.  A Linux version was available on the internal cache website offered by OSCON, but it was 32 bit.  I ended up downloading a copy from the Blender website (the conference wifi doesn’t start to get really bad until Wednesday).  Unfortunately, Blender proved unstable and would frequently crash with a segmentation fault.  Matthew had provided files to serve as starting points for each section of the tutorial, so it was relatively easy to follow along, even if I didn’t complete the previous section.

Matthew walked us through generating a simple animation of a flying saucer approaching a planet and hitting it with a beam of light.  We started with simple shapes, two spheres, one flattened, for the saucer, a cone for the beam of light, and another sphere for the planet.  From there we learned how to apply surfaces and textures, manipulate light sources, and perform a simple animation.

All in all, I think the tutorial was worthwhile.  If I had launched Blender without it, I would be lost.  I’m still lost, but at least I have some semblance of an idea about how it works.

At the beginning of the trip, I ran into a coworker, Juan, at the airport in San Diego, who was on his way to OSCON, too.  We weren’t able to sit together on the flight, but that worked out in the end.  A man was traveling with his son of around five years.  The son had the seat next to mine, while the father was several rows back.  I offered to trade seats with the father, so he could sit with his son.  One of the flight attendants bought me a beer for my trouble.  On top of all that, the we arrived in Portland earlier than expected.

After checking into our respective hotels, we swung by the Oregon Convention Center to register for OSCON and pick up our badges and associated crap.  Actually, a mug was included in the bag o’ stuff, which I can actually use.  Plus, the bag can be kept in the trunk of my car for use at farmers markets.

Finally, it was time for dinner.  Juan and I met up with a friend of mine from the San Diego Perl Mongers and hopped on the MAX to head downtown.  After wandering around aimlessly for a bit, I searched for Kells Irish Restaurant & Pub on my phone and we found it in short order, taking a seat out back in their new beer garden.  I washed a corned beef and turkey sandwich down with three pints of Mt. Hood Ice Axe IPA and one pint of Kilkenny Irish Cream Ale.  Shortly after we finished our food, we were joined by two more coworkers, who ordered some food of their own.  We spent some time doing what one does in an Irish pub, namely drinking and talking, then we made a failed attempt to find coffee.

That brings an end to OSCON travel day.  Tomorrow morning I will head to the convention center for breakfast and will hopefully run into more people I know (or will meet new friends).  I have two tutorials scheduled for tomorrow: Introduction to 3D Animation with Blender and Get Started with the Arduino – A Hands-On Introductory Workshop. I know these tutorials don’t appear obviously relevent to my job, but I’m looking at them as useful for relaxing and enriching.  One of the reasons I like to attend OSCON is because I return to work refreshed and with a state of mind more prone to imagining creative solutions.  So, tutorials outside of my immediate area of expertise are exactly what I need when I come here.

The initial message read thusly:

Hi friends in greenness-~-

I concocted a way to save plastic bags from the environment (doing my part!) I hid my trashcan from the janitorial night-staff, and have stopped using it!

If I ever have garbage items in-hand, which is rarely, I walk over to my area’s printer and trashcan nook and deposit it there, saving the bags at my desk which otherwise are replaced each night. Someone one-up that

The follow up:

One up that? Easy!

I use no plastic bags at all and keep my garbage in my Acme in-office composter. This allows me tocompost my (and a couple of coworkers) lunch waste into soil that I can use to grow wheat in my office window. I grow wheat using a solar powered, hydroponic system, where the water for the hydroponic system is collected from the building AC condensation, and pumped through the compost. This both filters and nutritionalizes the water, as the water is also pumped through my fish tank (600liters) where I grow Tilapia for my lunch, fish sandwiches.

The wheat is grown staggered in such a way that I have a continuous harvest of grain. I grind thisgrain in my hand operated grinder to make the buns in my solar oven (I keep this in the parking lotfor cooking my fish sandwiches and buns). The stalks/straw from the wheat I cut long and weave into tatami mats that I have put around a small zen garden where I can go to get centered after a long stressful day (raking gravel really does it for me) in the office. The bones from the fish, Iput through a “fast fossilization process” (yes the same one that makes dino bones seem older than 5k years) that makes them very hard. I can then use them as rakes in my zen garden or donate them to be used for combs by some of the less well kempt engineers in my group.

I am sure you other engineers out there have designed similar system. I cannot wait to hear about yours!

While unboxing my brand new computer, I remarked to my wife that Dell is one of the few brands trying to emulate Apple’s success with simple, elegant designs. Then I pulled out the power brick. The thing is a behemoth. If only Dell had followed Apple’s lead there. Unfortunately, at that point I had to put my new toy aside without booting it, because I still had an entire day of work to get through.

Perhaps the best part of this experience was never even booting into the default Windows 7 install. The very first thing I did was to insert my USB stick with a Fedora 12 Live USB Image and boot off that. It worked like a charm. I even successfully fired up Cheese, the web cam application. Sound didn’t work, but I ignored that. I clicked the install icon on the desktop and a few minutes later I had Fedora 12 installed.

This is Linux on a notebook, so there were a few hurdles to overcome. Sound started working sometime during the installation of the 351 MB of package updates. Unfortunately, the system started freezing on me. I suspected the video driver, but nothing showed up in the logs. Compiz didn’t work either, complaining that my driver lacked 3D hardware support. The latter problem was easier to debug, so I went after it first. Digging through logs, I found that the Open Source ATi driver was attempting to load the /usr/lib64/dri/r600_dri.so library, but it wasn’t found. Installing the mesa-dri-drivers-experimental package solved this and, voila, Compiz was working. This also seems to have solved the random freezes, so bonus.

Wireless networking didn’t initially work, either. This simply required the installation of the iwl6000-firmware package. I attribute both this and the missing graphics driver to installing Fedora using the live USB image. I assume that, instead of going through the usual hardware detection and downloading the appropriate packages, it just copies the live image to the hard drive and does some basic setup. In any case, everything works now, which is pretty impressive for a relatively high end notebook.

Speaking of high end, just what are the specifications?

• Processor: Intel Core i7 720
• Memory: 8 GiB
• Hard Drive: 500 GiB 7200 RPM SATA
• Screen Size: 1920×1080 15.6″

I expect this notebook to last me for about four or five years. I’m currently restoring data from my off-site JungleDisk backup. That should be done in a couple of days (it’s time to find a good NAS).

Update (2010-05-18)

The notebook is currently sitting on a desk behind me running the shred command in preparation for its journey back to Dell. As it turns out, the random freezing persisted. After several frustrating days experimenting with drivers, I finally discovered a sticky thread on Dell’s forums. Wow, I wish I’d taken the time to find that before I ordered this notebook.

There are posts dating back months and as recently as a few days ago. It doesn’t seem to matter what OS people have installed. I saw a glimmer of hope with a BIOS update, but it turns out the notebook was already running the most recent BIOS. So it was time to give up and return the notebook.

I called Dell on Saturday, only to be told that their systems were down. I called Dell on Sunday, only to discover that their customer support is closed over the weekend (that would have been a nice piece of information to have on the website). I called on Monday and, after being placed on hold for 30 minutes (important safety tip: don’t consume coffee before calling), I had a return shipping label in my e-mail inbox. I will say this for Dell, the return process was relatively painless. Well, aside from hearing “Lollipop” every time I called.

I’ll drop the notebook off at a UPS Store tomorrow. So now I need to decide what to get instead. The MacBook Pro is looking a lot more tempting. While I like ThinkPads, Lenovo apparently has a supply problem right now, so I can’t order a 15-inch with what I consider to be a good display resolution. Maybe I’ll just pick up a 10-inch notebook and a Synology NAS while I shop around.

After giving it some thought, I decided that it’s not worth repairing or replacing the server. I was able to get my e-mail flowing again by switching my domain’s MX record to use Google, so that wasn’t a problem. To get my blog and other web sites back online, I decided to go with a virtual private server (VPS). I have several friends who use Linode and highly recommend their service. I signed up for the smallest plan and was back up and running in minutes. It took a bit longer to get my blog back online, but that’s only because I had tinkered with the WordPress directory and left the themes in an inconsistent state.

So far, I’m pretty happy with the arrangement. A VPS should give me far fewer headaches in the long run. I was starting to grow weary of owning hardware, especially since it had long ago passed its prime.

Orszag says a new health care system could use psychology to figure out ways to give better medical care, not just more health care. That’s what he really wants to do: combine caring for people with good economic decisions.

The next story, Postal Deficit Grounds Wilderness Mail, was about the United States Postal Service discontinuing weekly airmail deliveries to remote locations.

The flights from Cascade, Idaho, have served ranches, outfitters, lodges and a University of Idaho research station for 50 years. But the $46,000 annual cost is too much for a postal service $6 billion in the red.

I don’t know if the scheduling was by design or by accident, but listening to them in this order got me thinking about something. Something that could be rather important.

If the federal government’s universal health care plan runs a deficit, will the coverage for outlying individuals, as it were, simply be cut? Who will those unlucky people be who had their care red lined because they were considered an unnecessary expense?

I heard you’ve been collecting payments on a private loan or “note.” I would love to give you cash right now so you don’t have to worry about collecting payments anymore.

They varied slightly in word choice, but both were careful to use the quotation marks around the word note. Have phishing attacks using e-mail lost their effectiveness? Are scam artists turning to the old postal mail standby?

One of the postcards listed a web site, a classic “turn key” business site, where hundreds or thousands of users will have their own URI and a standard template, such as www.scams-r-us.com/dirt-bag. I’m sure the parent site takes their cut, too.

Anyway, I loaded the main site (http://www.cash4cashflows.com/) and it looks like every other scam out there. Some dirt bag scrapes web sites or purchases address lists, then he hands them out to everyone who signs up for the site. Of course, everyone who signs up gets the same set of leads, but that’s the best way to make money off a single lead more than once.

Oh yeah, I may try to write once in a while, too.

Into this fray steps KPBS, San Diego’s public radio station. Clearly, they have Internet-savvy employees, because in short order their Web site was moved temporarily to a hosting provider that could handle the load. More impressive, however, was their use of so-called Web 2.0 tools. Using the Google Maps API, KPBS was able to create a map of the fires, evacuation zones, and emergency shelters. This was so useful to the residents of San Diego (and anyone outside the area who was desperate for information) that Google even published a case study.

But that’s not what I want to write about. The fires, and KPBS in particular, were my introduction to Twitter. The very first user I chose to follow was @KPBS News. From them, I was able to stay up to date in a way that neither television nor radio could deliver. This was before Twitter’s amazing popularity led to frequent appearances of the Fail Whale.

I was reminded of this tonight when I read this tweet:

@chslaw your analysis is based purely on two days of sporadic tweets by 1 person and assuming there was equal protest at both conventions?

There is so much going on in this single tweet, I barely know where to begin. First, and perhaps most obvious, KPBS is once again taking advantage of Twitter to keep their readers abreast of goings on in a way that neither radio nor even blog articles can deliver. And they’re doing it well—even going so far as to advertise it during their station identification breaks. This is micro-blogging at its finest: delivering short, pertinent news updates to readers in real-time. Not only is it real-time, but it’s time-shifted as well. I don’t need to pay active attention to the tweets. Instead, if I’ve been away from the computer for a few hours, I can quickly look over the list of tweets I missed.

The contributors to KPBS’s Twitter feed, though I don’t know who they are, clearly enjoy doing it. During the Democratic and Republican National Conventions, there has been a constant stream of tweets, keeping us informed of not only the important news of the day—the kind of thing that will show up on the wire services after the fact— but the seemingly trivial events as well. A VIP sighting in the security line, who just stopped by the news desk for a quick interview, or even unedited, first-person, subjective comments on police actions. This is why I respect KPBS and why we will likely never see a so-called real news service use Twitter: the people running the show would be scared to death to allow this kind of uncensored commentary. Even blogs allow the writer to spend time thinking about the article before they post it, and editors to retract information after the fact. Twitter is immediate. Twitter is real life, as it happens.

Finally, there’s whyu this specific tweet caused me to sit up and take notice. It wasn’t a news bite or color commentary. It was a specific response to another user. This is interactive news—News 2.0 if you will. Suddenly, the audience is a live participant in the story, as it happens. Is there a question the reporter isn’t asking? Is there an angle not being covered completely? Direct a tweet at the news organization and maybe those concerns will be addressed.

That, to me, is what is truly amazing about Twitter. Sure, anyone following me knows what I had for breakfast, or what’s bothering me at work (or, in the near future, when my daughter will be born), but that’s merely the fun stuff. I’ve only been active on Twitter since early summer, but already I can’t remember life before it.

Seriously, there are a lot people out there, swimming for their country. Unfortunately, all the NBC announcers can do is talk about Phelps. I don’t contest that he’s an excellent swimmer and will most likely do quite well, but why can’t they talk about the people currently swimming?

It reminds me of the old joke, “But enough about me, let’s talk about you. What do you think of me?”

[tags]2008 Olympic Games, Michael Phelps, swimming, NBC[/tags]

I’m not entirely sure how to take that. Have I really changed so little? Sure, I’m probably as arrogant as I’ve ever been, but at least now I’m aware of it.

About half way through the week I was accused of being a prolific blogger. Just how prolific, I wondered. So I went through the list of all of my posts prefixed with “OSCON 2008,” including this one. As it turns out, I wrote a grand total of 17,270 words. The post for Damian Conway’s Perl Worst Practices has the dubious distinction of containing the most words, at a scale-tipping 1,209. Other posts I made during the conference, but not directly related to any sessions totaled 1,608 additional words. Prolific? Perhaps.

My primary reason for writing so much about the sessions is for my own reference. These posts allow me to go back and remind myself of what I did and what I learned. I just happen to post my notes publicly, because I hope they may be useful or informative for others. In particular, anyone who couldn’t join me at OSCON. Naturally, I was a bit curious to know if anyone was actually reading my articles. So I checked.

I typically receive about four visits per day. Google’s Analytics service uses JavaScript to collect data, so I’m fairly comfortable declaring that my visitors are probably real people using real Web browsers, rather than search engines or even feed readers. The regularity of visits is curious, though. I’ll have to investigate my traffic a bit more closely. Visits to my site began to rise dramatically on the first day of OSCON, peaking mid-week when the main conference got started. Hopefully, people are enjoying my writings, because I enjoy doing it. I’ve tagged all of my 2008 OSCON posts with the oscon08 tag, which will make it easy to refer to them later.

Thinking back over what I’ve written, I’m not completely pleased with the finished product. I don’t think attempting to post entries so immediately after each session is the best approach. In the end, I don’t believe I’ve done the topic or the speakers justice. Next time, I may simply take notes in preparation for a proper article after the fact. The Tuesday night keynotes, in particular, would have benefited from this treatment.

I’ve been a fan of Damian Conway since I first attended one of his talks at a San Diego Perl Mongers meeting in late 2005. Since then, I’ve been fortunate enough to see him speak at two OSCONs as well as attending his Perl training at my place of employment. There must be something about Australians, because one of the best presenters at OSCON this year was Paul Fenwick, also from Down Under. I highly recommend them both. Entertaining and educational, a far too uncommon combination.

This year I found that I wasn’t as excited about OSCON as I have been in the past. It’s been more than just this past week, too. A lot of things that once brought me joy have left me feeling empty. I didn’t know why, and assumed that I was simply too busy, trying to juggle too many balls again. I was wrong, though.

Near the end of the Perl Worst Practices tutorial, Dr. Conway was asked how he became so proficient at what he does. In response he asked who in the room practiced martial arts. No one in front of me raised their hand, but I suspect at least one person behind me, in addition to myself, raised their hand. Disappointed, he cycled through a couple other sports (cycling and tennis, I think) until he received a reasonable response. The point, of course, was that, like these sports, programming requires passion and should be practiced every day.

That’s when it hit me. I don’t write code every day anymore. I’ve been writing code as long as I can remember. My first Hello World was written in BASIC at the tender age of four. Lately, I haven’t spent any time at all writing code. I’ve been waking up early, working long hours, going to bed early, and spending what free time I have left with my pregnant wife. That has to change. So now I’m back to staying up late, doing more work from home, and stealing moments to write code; even if it’s just a few lines. I’m also working on a talk I plan on presenting to my coworkers and would also like to give at SCALE 7x next year.

Conferences are not always about the tutorials or the sessions. Sure, they offer plenty of opportunities to learn something new, but that’s almost a complement to the main event. It’s about networking with our peers. Most importantly, it’s about revitalization. My annual pilgrimage to Portland replenishes my spirit. I return refreshed and full of creative energy. The trick is maintaining the momentum.

I suppose O’Reilly is targeting the same market as Gartner. Companies willing to spend what, to an individual, is a lot of money to have experts tell them what to think.

The named officers—president, vice president, secretary, and treasurer—are all members of the San Diego PC Users Group. Four out of the five current directors, of which I am counted, are members of the Kernel Panic Linux User Group.

This is the first time I’ve participated in a not-for-profit 501(c)(3) organization, so I don’t know how a typical group works. This one is contentious. I don’t know the motivation behind the typical volunteer board member of the San Diego Computer Society, but I now know that a cantankerous, argumentative disposition is a requirement for the job. It’s impossible, it seems, to hold a discussion without a formal, lengthy, and largely unnecessary motion first being introduced, then argued about. At one point during the board meeting last night, we were referred to as the San Diego Debate Society. I can only hope that made it into the minutes.

One member delivered an emotionally heated monologue to his fellow members. He was quite passionate, almost livid, in the belief that the organization is shrinking. He insisted that it should be growing, and he wanted to do whatever it would take to bring more groups into the fold. That got me thinking. What in fact is the purpose of the San Diego Computer Society?

The best anyone could come up with in the way of services in return for dues paid were the provision of a meeting location for the so-called special interest groups (SIGs) and liability insurance for the same. These days I would be surprised if a group couldn’t find a location to meet. Many companies are willing to provide space to employees’ groups, and free wifi is available at Panera Bread—though it’s not a convenient location for presentations. My experience with the modern technical user group has been informal gatherings instead of officially sanctioned events. In these situations, what use is liability insurance?

If asked today, I couldn’t provide an answer to any of my queries. I term as director lasts two years. In that time, I hope to find those answers.

I recently oversaw the dissolution of a failed Web-based start up company. We made the mistake of forming a board of directors. This led to more bickering than actual work. When we were launching our venture, I attempted to avoid the formation of a board, in favor of a more loosely organized company. Unfortunately, we were left to learn our lessons the hard way. Perhaps that’s just the way people are. In my experience, any time more than one person is handed any amount of power in an organization, strife will inevitably follow.

Every conference I’ve attended—though that hasn’t been many—have used the same gimmick in an attempt to get people to visit vendors. Each markattendee is given a “passport” with a number of vendors listed. The goal is to visit each of them and receive a sticker for the effort. The reward is entry into a contest, the odds of winning being proportional to the number of people who fall for the scam. I always start out collecting stickers, but quickly realize why I’ve never gotten as far as entering the contest. I really hate talking to salespeople. I’m not interested in any of the products being pitched and, even if I were, there’s nothing they can’t tell me that I can’t discover for myself on the Web. At one point, I’m pretty sure Eric S. Raymond even tried to hand me a flyer—I’m unsure if it was about Free Software or sex—but I politely declined and went on my way.

I was pleased to run into Alyson at the Ticketmaster booth. We met at SCALE6x in February, where she was again working the Ticketmaster booth, but also assisting us with the Perl Mongers booth. It was good to catch up with her. I was sure to tell her how much I admire what she does for the Los Angeles Perl Mongers and how I wish we had someone like her in San Diego.

Sun actually had a nice booth this year. They provided a place to relax, snacks, and a wifi network with a hidden ESSID for people fed up with the one provided by the conference. I didn’t spend much time there, but I did take advantage of the wifi as I lounged in the O’Reilly booth.

Amazon was running what I found to be an interesting gimmick in their booth. “Ninja” code. It was just a bit of self-modifying Perl written out on some poster board. Tell them what it did and get entered into a raffle. It was actually a fairly clever way of advertising for talent to hire. Heck, it got me coming back to the booth a few times, if only to make fun of it. I did spot some potential improvements.

Intel’s gimmick this year was actually kind of interesting. Everyone who visited their booth could receive a sticker with a number on it to wear. The goal then is to find the person wearing the matching number. People would post a phone number or Twitter handle on a cork board at the Intel booth for others to find. I posted my Twitter information but unfortunately my default view only includes friends, not replies. That, and the ever present fail whale made me miss my partner’s tweet. Mere minutes after the raffle on Wednesday, as I was getting ready to throw away my sticker, I hear Jonathan call out to me that he’s found my partner. As it turns out, there would be another drawing on Thursday, so we went ahead and entered. That led to an extremely annoying sales pitch. He wanted us to tell him about Moblin. Just to spite him, I told him about Snapdragon instead. What do I keep telling myself? Stupid gimmick contests aren’t worth it. What I did like about it was the social aspect. I met someone new, had a pleasant conversation, and he’s now following me on Twitter.

On Thursday at the O’Reilly booth, Brad was interviewed on camera by chromatic. I expressed my desire to see it play during a keynote, but that wasn’t meant to be. Brad uses Perl to do cool things with telescopes and munge astronomical data, which is of interest to the O’Reilly editors. He’s been asked to write an article about it, and I’m trying to convince him to give a talk at next year’s Open Source Conference.

[tags]oscon, oscon08, oscon2008[/tags]

Based on past experience, this is likely to be a fast-paced, highly-entertaining talk. One which will be impossible to summarize, or no doubt even to explain, here. Needless to say, if you’re not here, you’re missing out. I intend to sit back, relax, and enjoy.

He’s talking about the defining characteristic of a hacker. Particularly when they’re told that something is impossible and can’t be done. The reaction is typically, “you wanna bet?”

He just presented a slide that read, “Let’s leave behind the shackles of sanity…”

Now I’m scared.

This is a great talk. It’s a series of examples of things “you can’t do in Perl.” At least, not until Damian shows us how.

I think Brad may have taken notes. Which is good, because now I wish I had.

[tags]oscon, oscon08, ocon2008, Perl, Damian Conway[/tags]

There are so many holy wars debates about whether one language is better than another. Instead, the right question to ask is whether or not the developer’s skill set is right for the job. I agree. When I look for a developer, I’m more concerned with how they think than in what language they think.

Unfortunately, Tim is preaching to the converted in this talk. Nearly the entire attendance already uses Perl and don’t believe the myths. With that, let’s conquer them anyway.

Perl is Dead

No it isn’t. It’s two decades old and still growing strong. The books aren’t flying off the presses with great speed because the Perl community already has excellent books.

The trend when searching for “web development” jobs shows Perl growing very slowly in relation to other languages, particularly PHP. However, searching for “developer” jobs shows Perl growing very strongly and holding its own extremely well.

As a lurking member of the Perl community and an active member of my local Perl Mongers group, it’s been my experience that Perl programmers tend to be quite happy with their jobs. Which, unfortunately, has made it very difficult for me to find talent.

In fact, Perl is growing faster than ever. A simple look at how much work is going into CPAN will show that. The community is strong and Perl is everywhere.

Perl Is Hard to Read / Test / Maintain

Only if you’re doing it wrongly. We have Perl Best Practices, to use as the default documentation for coding standards, leaving developers with the need to only document when they deviate from the norm. There’s Perl::Tidy, to force any Perl code into one’s own personal style. Perl::Critic for ensuring that code is being well-written and follows best practices. And there’s no end to the Test::* modules and the work being done to make testing easy. There’s even a coverage analysis tool.

Perl 6 is Killing Perl 5

In fact, Perl 6 saved Perl 5, but one has to be close to the center of the community to see that. One should notice that Perl 5.8 and 5.10 have both been released in the time that Perl 6 has been in development.

There is a culture of testing around Perl. So many tests have been written for Perl 6, and the language is being defined by its test suite. This culture has leaked out to the community. In fact, I find there now exists a lot of peer pressure in the community to do proper testing.

Perl 6 Is Not Perl

Yes, and no. Unfortunately, I was so busy trying to catch up with the last section that I missed most of the points Tim made. In the end, I feel that this is fine. If Perl 6 was supposed to be Perl 5, why not just use the perfectly decent, already existing Perl 5? Which is still being actively developed.

Perl 6 Will Never Be Ready

It’s not on a schedule and, if it were on a schedule, it would be crap. It will be ready when it’s ready. Better to do it right than screw it up. The development model encourages a lot of experimentation, and it’s difficult to schedule experimentation.

There’s No Perl 6 Code

Sure there is. Thousands of lines of Perl 6 code exist in the test suite that came about from Pugs. These very same tests are being used in Perl 6 development today in the form of Rakudo, Perl 6 on Parrot.

The important thing to note is that Perl 6 refers to a specification. It does not refer to a particular implementation. Any implementation that passes the test suite may call itself Perl 6.

From an authority in the audience (who I don’t recognize, unfortunately), we have been told that there will be a useable Perl 6 by this Christmas. A round of applause ensued.

[tags]oscon, oscon08, oscon2008, Perl, Tim Bunce, myths[/tags]

First up this morning Allison introduced Benjamin Mako Hill of the MIT Center for Future Civic Media. He will be speaking about Advocating Software Freedom by Revealing Errors. He seems to be far too highly caffeinated for the room this morning, and is speaking very quickly, and the sound system is too loud, so I don’t entirely know what’s going on.

The gist of the talk is that, when errors become visible to the user, it exposes something about the underlying technology. He’s provided several obvious examples of ATMs crashing with Windows errors. He runs the Revealing Errors Blog, too.

Next up is Dawn Nafus of Intel, speaking about Three Challenges. Unlike most speakers at OSCON, she is an anthropologist. There is a notion, particularly in the mobile devices industry, is that adding more and more data is equivalent to adding context. This is phenomenally untrue. Data without context is, more often than not, useless.

Her second challenge is the global food crisis in food and water, particularly in the developing world. We Open Source folks are quite good at decentralizing power, just look at how so many of our projects are organized. Technology is fast going mobile, and as these devices become cheaper, they are more easily put into the hands of people in the Third World. There are many applications for this technology, we just need to be creative about how we go about taking advantage of this proliferation in technology.

The third challenge is to strengthen global growth in technology producers, not just consumers. We must better understand where growth is coming from.

Annoyingly, we have another speaker from Microsoft this year, Sam Ramji. He’s, apparently, here to tell us about Open Source Heroes. He’s telling us about platform trends, something we already know about. There’s some slide about applications moving into Internet moving into Web applications over the time frame 1995 through 2005.

Microsoft sees Open Source growing strong over the next decade, but it’s hard to take him seriously, given the company’s history. While he’s talking about Microsoft’s contributions to Open Source projects and the work they’ve done to improve their ability to work on Windows, I’m constantly on edge around Microsoft, wondering what they really have planned. In fact, I may have just answered my own question. Improving the use on Windows, thus attempting to ensure the continual use of Windows. They’re desperate to hold on to the market share they’ve so deceitfully gained.

This talk can be summed up as, Hey look, we’re not evil, look at this boringly enumerated list of Open Source stuff we’ve done.

He’s announced that Microsoft has become a “platinum” sponsor of the Apache Software Foundation. That doesn’t sound good to me. Do people forget the embrace-extend-extinguish history of the company? Should we really trust them so much?

Next up, refreshingly, is Tim Bray of Sun Microsystems, speaking to us about Language Inflection Point. There’s background music, and he’s speaking very quickly. He’s going over slides demonstrating various ways of measuring the popularity of programming languages. From search engines to book sales.

He took a survey of the room. A show of hands for who is using various languages and if we would still use it in an ideal world. Python and Ruby were the only two languages with a positive delta, more people raised their hands to show that they’d use it in an ideal world than those who currently use it.

From there, he launched into a discussion of each language and their benefits and drawback as he sees them. Obviously subjective, but they’re not entirely bad points. He never got to Perl, so I’m a bit disappointed.

Finally, we have Jeremy Ruston of BT Design, who created TiddlyWiki. He’s here to tell us about Learning from Airports.

At airports today, the actual actions of taking off and landing is more a side-show. There are more shops and things like security lines (and waiting), and the actual arrivals and departures are a very short part of anyone’s visit.

Airports do serve as an excellent analogy for technology standards. Single sign-on: passports. Access tokens: boarding passes. Standard documentation: universal signage.

The keynotes wrapped up with a question and answer session with each of the morning’s speakers. The first question, unsurprisingly, was about patents, and what will it take for Microsoft to commit to not using patents against Open Source. The speaker claims that developers should never have to worry about it, but it was unconvincing.

Unsurprisingly, the majority of the questions were directed to the Microsoft representative. They ranged from (and I’m paraphrasing), why Microsoft is evil and patent bashing thinly veiled as questions. Unfortunately, the presence of the Microsoft shill speaker on stage led to a completely wasted question and answer session.

But now it’s break time, so I’m off in search of more coffee. OSCON starts way too early in the morning.

[tags]oscon, oscon08, oscon2008[/tags]

SourceForge held a couple of parties for us last night. One was at the Jupiter Hotel and the other, branded BeerForge, was at a party venue down the block from the hotel. Obviously, we attended both—twice.

Josh and I started out at BeerForge. After a while we got hungry and found Brad, Alice, and Sam over at the SourceForge awards party. As things got too crowded, we all went over to BeerForge. As the venue grew too hot and loud, we ended up back at the SourceForge location, where we could be outside at least. After that venue closed down, Josh and I went back to my hotel room to polish off a growler—a half gallon—of beer I had picked up at Rogue the night before.

I’m now at breakfast, after a whole four hours of sleep, and extremely thankful for the coffee, fruit, and pastries that have been laid out for us. The fresh air and the walk to the convention center helped, too. This week’s festivities make me almost want to take a pass on the Oregon Brewers Festival. I said, almost.

Fortunately, there are only two sessions today, leaving me with only two decisions to make. However, after a more careful review of the schedule, the choices seem obvious.

First, Tim Bunce is giving a talk on Perl and Parrot: Baseless Myths and Startling Realities. I’m not as enthusiastic about Perl 6 as I once was, but I quite enjoy Tim’s sessions. Following Tim, in the same room, is Damian Conway. He’ll be presenting—oh, does it even matter?

I will be faced with a bit of a dilemma tonight. My flight home is scheduled for 6:40am tomorrow morning. However, the MAX light rail ends its service at midnight and doesn’t resume until 4:30am. Several years ago this may have been acceptable, but not in the airports of today. So my options are to get a couple hours of sleep followed by calling a town car, or check out of the hotel tonight and make my way to the airport before the MAX service terminates for the night. Quite honestly, arriving at the airport six and a half hours early is still shorter than some of the layovers I’ve had.

Well, I’m going to finish my breakfast and tag some photos. In just under an hour, the final day of keynotes—and thus of OSCON—get started.

If he had Perl to do all over again, what would he do different? Only two things, nothing, and everything. Perl 6 is the everything part of the answer.

In Perl 5, one of the problems that creeps up is that regular expressions (regexes) are strings. The best example of this is variable interpolation in regexes. In Perl 6, this has been fixed. They are now their own language.

Like cargo-cult programming, parsing has turned into its own cargo-cult. Perl 6 breaks the mold when it comes to copying languages (the old lex/yacc loop), and instead uses polymorphism in its sub-language design.

Both regexes, double quoted strings, and single quoted strings are examples of sub-languages in Perl 6. Each of these sub-languages has its own parsing rules and therefore parsing implementations. This allows is code reuse. Parsers can derive behavior from other parsers, but treat the tokens differently as necessary.

Fundamentally, Perl 6 is very simple. It has no CORE. It has no built-ins and no operators. What Perl 6 has given us (will give us?), in effect, is a just in time lexer. Tokens and their behavior can be defined on the fly, on a per-sub-language basis.

There are quite a few changes to the regularity of regular expressions. Mostly what this means is that Perl 6 regexes are incompatible with those used in Perl 5, and that Perl-compatible regular expressions (PCRE) aren’t (or won’t be).

All languages tend to fall into the One True Syntax trap. Perl 6 has aimed to break out of that trap. By giving the user enough power over the syntax (rope) to design the language that suits them (hang themselves).

I didn’t enjoy the State of the Onion as much as I have in the past. I suppose that’s to be expected. Larry did warn us at the top of the talk that it would be serious and contain only a single joke. For as great a writer as Larry is, his ability as a public speaker is lacking. That’s okay, though. I’d rather he not shift focus away from the design and development of Perl.

[tags]oscon, oscon08, oscon2008, Perl, State of the Onion, Larry Wall[/tags]

Sorry guys, these are five minute talks. If I start summarizing, I’ll fall way behind. You’re lucky I even take the time to write this.

If you really want to know what’s going on, there’s a schedule.

For those of you still reading, here’s a bit of stream-of-consciousness for you. Note, if trying to match these up to the schedule, they are in order, but I didn’t comment on all of them.

Testing databases with TAP is cool. You really can test anything with it.

Nice to see The Perl Foundation get some slots in Google’s Summer of Code this year.

It’s interesting to see how much Perl is used to compile USA Today every day. Without Perl, it would be a very empty paper. Though I’m not convinced the content would be much different.

Schwern tells us that, in thirty years, time will wrap.

$time = 2**31 - 1;
print scalar gmtime $time;

Tue Jan 19 03:14:07 2038

$time = 2**31;
print scalar gmtime $time;

Fri Dec 13 20:45:52 1901

Wait, that’s not good. But he’s fixed it.

Sweet, Perl on Google App Engine!

Use autodie instead of Fatal. It’s better.

Also, Paul Fenwick is one of the best speakers I’ve seen in ages. I hope he becomes an OSCON staple.

F*ck, the F*cking thing is F*cked had the best slides.

IPv6Experiment.com (warning: there may be porn).

[tags]oscon, oscon08, oscon2008, Perl, lightning talks[/tags]

Paul’s preferred title for this talk is Human Interfaces for Geeks. Most geeks think of things like keyboards, mice, and monitors when it comes to interfaces. But that’s not what this is about. Those are human-computer interfaces. We’re here to talk about human interfaces. Things like aural or visual communication.

Geeks can be quite awkward when it comes to interfacing with other people.

There are normal people out there who do make sense to geeks do make a lot of sense to geeks, Sims. They have wants, fears, and needs. These are easy to see, because they have status bars. Unfortunately, real people don’t have status bars.

One thing learned from the sims, if you want something done, ask a happy person to do it. They will be far more willing to do it and will end up being far more helpful. How do you make people happy? Coffee and chocolate will go a long way towards making people happy and giving a higher priority to your requests.

Even without this kind of base bribery, we can make people happy. By matching one of their goals to one of our needs. Humans, when they’re instantiated, have a set of default goals, and no one ever changes these. One of the best goals for this is a feeling of importance. How can you make someone feel important? Talk about them.

It’s easy to talk about someone. Practice active listening. Essentially, be an Eliza bot. Listen to what someone is saying, then repeat it back to them in the form of a question. If they’ve been on vacation, ask them about it. If they’ve accomplished something, ask them about it. This makes people very happy.

Another way to make someone happy is to make them feel important in front of their peers. If someone submits a patch, recognize that in front of the community. I did this once (because I’ve only ever received one patch for my one and only CPAN module). Someone from Australia submitted a patch and I put his name in the Changes file. I know I feel amazingly good when I’ve done a good job, so I do my best to point out when people have done a good job.

People, particularly in the United States, tend to look at situations in an adversarial way. When someone wants something and someone else is standing in their way, he will want to force his way past. This is rarely an effective method. Instead, those standing in the way are people, too. The best method is to take action to make that other person feel good about themselves. When they are happy and feel good about themselves, they are far more likely to go out of their way to help.

This was a good talk. Geeks rarely read books aimed at management types. A lot of these books place a lot emphasis on the concept of win-win and interpersonal communication. It’s nice to see a geek taking these lessons and putting them into terms other geeks can understand. We definitely need more geeks with people skills.

[tags]oscon, oscon08, oscon2008, people[/tags]

The Devel::DProf module is old and a waste of time and is broken. Stop using it. Take it out and shoot it.

The first obvious distinction between profilers is CPU time versus real time. CPU time tends to be highly granular, but doesn’t include I/O, context switching, or other kinds of blocking. That’s where real time comes in. It’s far more useful in the real world.

Tim, as with many of us, is interested in line-based profiling. It provides a high level of granularity The total subroutine time is not always useful, particularly in larger subroutines.

The NYTProf module is exremely fast, discounting the time taken by profiling overhead, making it quite a bit more useful for real world analysis. It also allows profile times per block, and can be aggregated up to the subroutine level. It’s a module with dual profilers: line-based and subroutine-based.

It gets better, every location that calls the subroutine keeps separate track of the subroutine time. This allows us to determine where the majority of the subroutine calls are coming from. For control flow statements, the decision expression is not taken into account when profiling the block that is executed. This is useful if the loop control itself takes time that should be discounted.

And that’s it for the description. Now we have half an hour to play with it.

The HTML-based reporting is inspired by Devel::Cover‘s reporting. Reported for each file are the number of statements executed, the time spent in the source file and the line, block, and subroutine reports. The subroutine reports include the amount of time spent within the subroutine and the amount of time spent in other called subroutines. The coloring of each line of the report—red, orange, yellow, and green—give a relative measure of deviation from the norm. Very impressive.

Even more impressive, Devel::NYTProf is capable of reporting exactly what a subroutine reference is called, even when it’s an anonymous subroutine compiled within an eval. With a handy link also provided, the called code can be easily inspected.

In summary, Devel::NYTProf is awesome. Use it. I know I will.

Tim Bunce is even more impressive than most people think he is. He is the only presenter I’ve seen so far who has managed to use IRC while giving his talk. Well, he didn’t actually type on IRC, but he had Colloquy running in the background. This particular IRC client uses Apple’s Growl feature to display notifications when you are mentioned in a channel. After he’s opened up the session to questions, one of those notifications pops up on the projected display:

<sirhc> Adam Kennedy (to Tim Bunce): Why are you so awesome?

It got a laugh, and Tim seemed to take it all in stride, even joking that he was not looking very professional on his screen cast. Important safety tip for session presenters, don’t leave your IRC client open.

[tags]oscon, oscon08, oscon2008, Perl, programming, profiling[/tags]

Pudge is, quite famously, a Republican, so he wants poor people to die, he asserts his right to shoot people who jaywalk, and he hates puppies. Now that we have that out of the way, this will not be a political talk. Instead, it will be a talk that just happens to use politics as the problem domain for which Perl was the solution (but isn’t it always?). Pudge happens to volunteer for the Republican party in Snohomish county, Washington. I actually know the area fairly well, as my grandmother happens to live there.

Winning elections is all about knowledge. And blackmail. But, mostly knowledge.

This session is essentially about data mining. There are a number of disparate data sources available with information about voters. From registration and voting history to contact information and preferences—can or can they not be contacted. This data is not always easy to access. For example, there is something called the Voter Vault, which is a super secret database of voter information controlled by the Republican party (there’s an NDA involved, so we won’t see any of it).

Essentially, Voter Vault is a really crummy Web application that only works for IE (hence the crummy part). That’s where WWW::Mechanize comes in. Using this brilliant module, data on any Web site can be retrieved, even if it requires a certain amount of user interaction to access. This, along with other sites, like the Washington State Public Disclosure Commission, provide all the raw data Pudge needs.

However, raw data is, by itself, not useful to anyone. This is the reason behind Pudge’s efforts. He uses Perl (and some JavaScript) to collect and aggregate all of this data. Then, once it’s all compiled, he can use a bit of Perl glue to use the data in Apple’s Address Book and Mail applications. But, more importantly, he can visualize it.

For the visualization, Pudge uses everyone’s favorite new tool, Google Maps. Using the Ajax API provided by Google, he can embed a map in his own Web application and, next to it, provide controls to enable and disable different views of the data on the map. For example, candidate donations by city and how much each candidate received.

It gets better. With the Google Earth APIs available to Google Maps, KML files can be generated (again, with Perl) to provide even better data visualizations. For example, precinct boundaries can be imported and colored based on voting history.

Initially, I wasn’t sure how I’d feel about this talk, but I ended up enjoying it. It was an excellent presentation on how to take data and display it to users in a useful manner.

[tags]oscon, oscon08, oscon2008, Perl, politics, visualization[/tags]

A computer once referred to a human worker who would perform calculations. This was a fairly easy thing to cluster and “run” several computers in parallel. As time progressed, more and faster work was desired. Enter the electronic computer, and specifically for this talk, the Cray. As with anything, the inner workings of the Crays of old can be recreated in Perl. Just use the Cray module, no problem (if only it existed).

After the history lesson, we move into high level overviews of parallelism and pipelineing, and a note about Amdahl’s Law. This was followed up with an example for detecting prime numbers by partitioning the work.

The slide presentation was over in under 20 minutes. Instead, we’re jumping straight into code examples. Awesome.

Or so I thought. Unfortunately, he’s been interrupted by multiple people in the audience, who keep wanting to move off into tangential conversations. Eric is having difficulty bringing the talk under his own control—it’s no longer his talk, but that of the somewhat rude fellow in the front row. Neither is Eric as eloquent when he switches from a prepared talk to demonstrating and explaining real code. It’s become far more difficult to pay attention to this session, and I find myself looking at the clock to see how much time we have until the next session.

For real fun, be sure to check out Brad’s post on Schwern’s session about skimmable code.

[tags]oscon, oscon08, oscon2008, Perl, programming[/tags]

Our first speaker this morning is Keith Bergelt of the Open Invention Network, speaking about Open Invention Network and Its Role in Open Source and Linux. He’s speaking about patents and intellectual property in Open Source, the realities of it today and where he sees it going tomorrow. He’s big on the buzzwords, and this is not the right audience for it. In fact, a game of Buzzword Bingo has already broken out in the IRC channel.

In summary, “Blah blah patent blah blah buzzword blah blah we care blah blah.”

Oh wait, he droned his way to a point. One of the things the Open Invention Network does, and I should have known because I’ve seen this before, is to buy up patents and keep Open Source safe from them. At least, until their funding dries up and they turn to their patent portfolios to squeeze money out of everyone.

I seem cynical this morning. Maybe I didn’t get enough sleep. Or maybe the first keynote today is boring. The back-channel conversation on IRC is actually quite entertaining, though. I need to whip up a quick IRC log file analyzer to correlate IRC traffic to keynote speaker. Then I can use it as a tool to rate speakers.

The pain is finally over, and the program chair has caught buzzworditis from the last speaker. Next up is Peter H. Salus to speak to us about Anniversaries. I’m told by Nat Torkington that Peter is an Unix historian. He’s started off by showing us a picture of the first transistor, which is about 20cm and a bit more than that around. It’s amazing to see how far we’ve come in 60 years—how many iPhones can fit in the same volume?

Anniversaries, in this case, are major milestones in computer history. The first electronic computer; the first time-sharing system; the first Unix paper by Ritchie and Thompson; the GNU project. One of the interesting things to learn is that history repeats itself. Back in the days of ARPANET, there was an issue involving the exhaustion of address space on the network. Short-sighted problems like that would never happen today, right?

I enjoyed this keynote speech, but probably because I really enjoy history.

Next up, Supporting the Open Web with David Recordon of Six Apart. It’s not just the open nature of the software or the platform that matters, but the openness of the data. Without open data, the Open Web can’t work. Interoperability and open specifications are vital to moving forward with the technology. The Web must be accessible, not just available on one device or another.

The majority of the talk is dedicated to talking about the various organizations doing work to keep everything free and open, including the Open Source Initiative, Creative Commons, and the Apache Foundation. There are also quite a few people donating a lot of their time to help.

He’s announcing the formation of the Open Web Foundation. They don’t necessarily want to form their own foundation, but they have had little luck finding an existing one to do what they’ve asked.

The Open Web Foundation will focus on four areas: incubation, licensing, copyright, and community. Many companies, such as Google and Yahoo have already shown support for this new foundation.

Following David is Danese Cooper of the Open Source Initiative and Intel Corporation to speak about Why Whinging Doesn’t Work. A catchy title, and she introduced her talk with a funny video of a choir of Finnish women singing about all of the complaints they have (search YouTube for “complaints choir“).

She’s making a very good point. There are so few women in Open Source. Geek are often intimidated by women and women are so often objectified. It’s true, there is a huge gender imbalance in the geek community. Of all the geeks I know, I can name very few women. I’m having a daughter soon, and you know what, she’s going to learn to code.

However, the feminist angle is merely a way of personally relating to the main point of her talk. People complain. I do it, you do it, the guy sitting next to you does it. But whinging doesn’t help. Mostly, all whinging does is beget more whinging. That energy used to complain needs to be channeled into something constructive.

For seven years, Danese was the only female member of the Open Source Initiative’s board. Now 30% of the board members are female. Progress.

Finally, Nathan Torkington, former OSCON program chair and recently of He Hononga Software, Limited and his keynote, fork() && exec(): Spawning the Next Generation of Hackers. Thank goodness, this talk is not about geeks having sex.

I’ve been looking forward to this keynote for a couple of reasons. First, I’ve missed hearing Nat speak this year. Second, I’m expecting my first child in a couple of months. Not only that, two other members of my local Linux User Group are either recent or expecting fathers. Suddenly, topics involving children are much more interesting to me.

Nat recently moved his family back to New Zealand. One of the things he does now is to help teach children about computing. In his school district, the computing infrastructure was awful—and used Windows. So he got a handful of Macs and became the Bastard Operator from Hell for his kids’ school. Then he started teaching the schoolchildren. Quickly, he discovered that the teachers needed teaching as well.

One more thing he wanted to do was to teach programming. He feels it’s a very important skill. But it has to be done right. Avoid the frustration that so many of us experience with computing and programming, but something consistent, easy-to-learn, but still powerful. Nat’s introduced Scratch. The kids loved it.

Lessons learned:

• Lectures suck (you have two minutes to say what you want)
• The gender gap is not what you think (girls are smarter and more focused than boys)
• Keyboards are a challenge
• Not a lot of experience with math
• Robots are lame

So please, volunteer in schools. Perhaps remove Windows and bring the joy of Linux to their lives. Find, or create, good courseware, such as Scratch. Post it on your blog, so everyone can find it. Finally, don’t profit. Do this for the good of the children, our future generation of geeks.

With that, we’re off to the expo hall for the break.

[tags]oscon, oscon08, oscon2008[/tags]

Sadly, yesterday during the morning keynotes, Al was called back home abruptly. Hopefully, he made it back to the UK quickly and safely.

After all the sessions were said and done for the day, we found our way to the expo hall, where beer and appetizers were being served. Alas, we did not stay long. We caught wind that Google would be hosting pizza across the river at Old Town Pizza, an event we never made it to. It turned out to be a pizza dinner for Summer of Code participants. We finally ended up at Rogue for dinner, and I finally got myself a growler for my collection—currently being held (safely?) in Brad’s hotel room refrigerator.

After dinner, we swung by the supposed Amazon party. Only, there wasn’t one. It was only held between 8:00pm and 9:00pm. Seriously? This is how Amazon throws a party?

Fortunately, the Sun party was a better this year. First of all, they had no stupid lolspeak flyers. Second, bottled beer instead of kegs, which is difficult for incompetent bartenders to over-prime and serve nothing but head. Third, sumo wrestling! Brad and I also participated; those photos are coming soon, I promise.

However, as I actually enjoy attending the keynote sessions—scheduled far too early in the morning—I was back in my hotel just after 11:00pm. I ran into Dan and his fellow TierraNet colleagues in the hotel bar. Unfortunately, I had missed last call, but I sat down for a bit anyway. We had some laughs with Margaret, the bartender. I tried to get her to slap Tyler, but sadly it never happened.

Today’s session tracks begin with a dilemma. Unfortunately, I’d like to be in three places, simultaneously.

• Skimmable Code: Fast to Read, Safe to Change (Michael Schwern)
• Open Source Microblogging (Evan Prodromou)
• Stick a fork() in It: Parallel and Distributed Perl (Eric Wilhelm)

Fortunately, Brad wants to go to Michael Schwern’s talk, so I’ve agreed to attend Eric Wilhelm’s talk. We’ll write summaries and both be happy. The microblogging session was just a curiosity for me anyway.

The rest of the day won’t require quite as much rolling of dice.

• Perl for Political Campaigns (Chris Nandor)
• Ultimate Perl Code Profiling (Tim Bunce)
• Hacking Wetware for Fun and Profit (Paul Fenwick)
• Perl Lightning Talks
• State of the Onion Address

The only potential conflict is during the second half of the Perl lightning talks, A Tasting Tour of Haskell (Bryan O’Sullivan).

Just about time for the morning keynotes, and I’m looking forward to seeing Nat Torkington speak. If I can reconnect to the wifi network, I can even post this entry.

Paul has started out by describing the world’s oldest computer in terms of modern computing.

From there, he’s providing examples of major computing and engineering failures throughout modern history. It’s amazingly entertaining. I can’t summarize it. If you’re not here, you fail. I’m just going to sit back and enjoy it.

[tags]oscon, oscon08, oscon2008, history, failure[/tags]

I work for a small telecommunications design company, so this venture into Linux on mobile platforms holds quite a bit of interest for me. Granted, I work in a support capacity for the folks who do real work, but knowledge is always a good thing, right?

Intel has chosen a Fedora- and GNOME-based platform for Moblin. I’ve contributed a couple of packages to Fedora, which means users of these Intel mobile systems can play Zork.

Dirk wasn’t able to have any sample devices with him, so he was left to describe what a “net book” is. Fortunately, in a room full of geeks in a mobile computing presentation, several people had ASUS EEE PCs, which he could show off to the audience. There were also a Nokia N800, N810, and of course several iPhones in the crowd. Obviously I mobile-savvy audience.

Linux is often touted as the obvious first choice for these mobile devices because of its price. One of the more important reasons is the ability to strip down Linux so much to fit on these devices, but still be incredibly usable.

This session ended up being exactly what I thought. It’s essentially a marketing spiel masquerading as a technical talk. The slides are far too slick, and the only reason any technical details are being given at all is because of the last-minute speaker substitution. Our new speaker is a technical guy who has been promoted to a managerial role. The presentation was apparently designed by a marketing guy with enough technical knowledge to be dangerous. I hope Brad is having more fun in the Moose talk.

I’m really regretting where I’ve chosen to sit. Someone in front of me is wearing way too much pungent cologne. I may be sick.

[tags]oscon, oscon08, oscon2008, Intel, Moblin, mobile, Linux[/tags]

There are a multitude of troubles with using a proprietary operating system, as anyone attending OSCON is familiar. From cost to forced upgrades to vendor lock-in. Suddenly, companies are at the mercy of the vendor, and have lost so much of their own self-direction.

Not only has John’s company benefited from the Open Source community, they’ve contributed back to the community. That’s key, I feel. I’d like to see my own company contribute much more than they do.

I’m not sure who this talk was targeted for. It wasn’t really a good sales pitch to business-type people, and it wasn’t very high level for IT-type people. I don’t know what I expected from it, but I don’t think I got what I wanted out of it. Most of the challenges they faced, we’ve already solved. We’ve already created a standard image and can already deploy it on standard hardware. We already have Windows virtual machines for anyone who still needs to run Windows applications. We already have enough management buy-in for the project, too.

I do, however, like the sound of this “seamless RDP” he talked about. I will need to investigate it further. Also, it’s refreshing to hear from someone who has successfully (mostly) removed Windows from their enterprise.

[tags]oscon, oscon08, oscon2008, Linux[/tags]

my $code = qq{
    print 1+1 . "\n";
    $code =~ m/(\d+)\+(\d+)/;
    $new = $1 + $2;
    $code =~ s/\d+\+(\d+)/$2+$new/;
};

for ( 1 .. 10 ) {
    eval($code);
}

What’s the first bug? Yes, it should use q{}, or the variables will interpolate on the initial assignment to $code. To their credit, they initially used single quotes, but people said it was too hard to read.

I wasn’t content with just figuring out what the code did and fixing a small bug. I think it can be written better.

eval($code = q{
    print 1+1 . "\n";
    $code =~ s/(\d+)(\+)(\d+)/"$3$2" . ($1 + $3)/e;
    eval $code;
});

Much better. Not only is it more concise, I was able to remove that pesky loop, so I wouldn’t be bothered by any silly upper bounds.

So what does it do? Should be obvious. Head over to the Amazon booth and let them know.

Nearly everyone agrees that code reviews are a good idea, so why aren’t they done more often? In fact, this is the very same problem we’ve had at work. We’ve been talking about code reviews for two years, but we’ve never had one.

There are some barriers to entry to doing code reviews. If revision control is not in use or automated tests aren’t being run, tackle those problems first. Also, the need for a team process is necessary, from ticket tracking to release plans.

Pair programming, that tenet of XP, is a poor substitute for code reviews. Two people working together will not magically turn one or the other into what is essentially a disinterested third party, who may catch bugs simply because they weren’t there when it was written.

Test-driven development is also a great way of coding, but not a substitute for reviews. Often for the same reasons. Tests are often just more code and the code tested is only when someone thinks to test it.

Even during a code review, a reverence for authority can get in the way of getting things done. A poor, intimidated programmer may not have the courage to criticize a more senior programmer. Instead, this can be turned around with something I use a lot myself. I like to call it, “playing dumb.” Instead of saying, “this won’t work,” ask what will happen for a suspicious case.

Socially, the only way for code reviews to work is universal buy-in. Everyone is subjected to code reviews by everyone else. No exceptions. Make them a habit, a regularly-scheduled meeting. At work, I’ve even suggested bi-weekly, or perhaps monthly, catered, lunch time code reviews. Just to get us into the habit of doing it.

Code review time should not be wasted on things such as code formatting, best practices, or test coverage. This is stupid. These are objective tasks that can be automated.

Instead, look for subjective things, which can’t be automatically found. Such as code readability, algorithmic clarity, and consistent identifier naming. Other targets for code reviews are the usual things we here over and over again as development best practices: consistent documentation that follows the internal standard, that kind of thing.

The remainder of the talk is essentially an enumeration of all the things to look for in code reviews. All of them are, at least to me, common sense. So I’m not going to spend any time writing them down. If you don’t already know them, well go find some common sense.

One thing that he recommends that I like is code reviews by e-mail. It’s an old, well-understood, and (usually) reliable tool. So why not combine e-mail with a version control system—particularly one of the newer distributed version control systems—to perform out-of-band code reviews. It actually sounds like a good idea to me, and I’ve done it at work a couple of times with code written by an intern.

What I’m starting to notice is that many of the later the recommendations for reviewing code are personal opinions of the presenter. I think the way in which code reviews are performed are highly dependent on what works best for the group reviewing code. It’s like so many things, from cameras to backup solutions: the best one is not the shiniest or the one with the most bells and whistles, it’s the one that’s actually used.

[tags]oscon, oscon08, oscon2008, programming[/tags]

Erlang is a pure functional language (and thus no side-effects) with strong dynamic typing and syntax similar to Prolog and ML. Most notably, it contains concurrency primitives, which is what we’re here to hear about today.

Erlang concurrency primitives include spawn, to create a process, !, to send a message to a process, and receive, to listen for a message. These are not system level processes, but other Erlang processes. It’s a lot like using fork in imperative languages, but less messy.

Erlang, like many functional languages, can implement quick sort in three lines of code. I was having a discussion with a friend of mine about this topic yesterday. It’s very nice, and demonstrates the power of functional languages to trivially solve an already solved set of problems, but is it any use in the real world? Maybe. While I’ve not seen any non-trivial examples, I’m reserving judgment.

The first example is a demonstration on how simple it is to parallelize the quick sort algorithm. It’s not a worthwhile example, in fact, it’s a particularly bad idea, but it serves as a reasonable example of the ease of use of the concurrent features in Erlang. So far, it seems like changing a map call—something I love from Perl—to pmap.

The pmap function is not a built in function (BIF), but a library function built on top of the built in concurrency primitives. The code implementing the function is actually quite simple, and should be available in the slides available at the end of the conference. Conceptually, it spawns as many processes as necessary and uses them to call the function being mapped. It then gathers the results, waiting for each process to complete. It’s quite similar to code I’ve written to do scientific processing using MPI, but I’ve always thought functionally when coding.

After explaining concurrency, we make the jump to distributed systems. What’s everyone’s favorite distributed system? Twitter! Twitter, while not designed as such, is essentially a messaging system. Erlang does message passing very well, and almost all programs are designed using this paradigm. So Kevin took a stab at implementing a Twitter-like system in Erlang, the key ideas of which he will present to us.

The lightweight and convenient process architecture of Erlang lends itself to the problem. Every user can be represented as a process. Each process can then send and receive messages. In effect, the problem—the messaging part anyway—is now solved. But, what about scaling to multiple machines?

It turns out to easy (but you knew it would, right?). All we need to do is pull in the global module and we can bind our users not only to a process identifier, but combine that with a given machine as well.

However, we still don’t have a reliable system. If a process dies, that user is no longer in the system. So it really is a lot like Twitter.

OTP, the Open Telecom Platform (a legacy name from Erlang’s history at Ericcson), provides a set of common behaviors and patterns for writing reliable and distributed system. The programmer simply declares what interface they would like to use, then implement a set of callbacks defined for that behavior. Reminds me a bit of roles (because I have an unhealthy need to relate everything back to Perl).

As with everything in Erlang, it is almost impossibly easy to set up this reliability. I still can’t get over how well the syntax maps to how I actually think about code.

A question was raised about how to go about setting up the necessary cluster of hosts used in Erlang’s mesh network. Kevin went into it briefly, but it’s unfortunately out of scope for this session.

And, with that, it’s time for lunch. Thanks, Kevin!

[tags]oscon, oscon08, oscon2008, Erlang, concurrency, programming[/tags]

Recently, Adam has been funded by The Perl Foundation, Perl in Israel, and Stonehenge to use Perl from nothing but his flash drive. This provides an excellent motivation to get Strawberry Perl working in a highly portable way.

Originally, Perl was awesome and worked everywhere—except Windows. That was okay, because Windows didn’t matter. No one did any real work on Windows. Then, around 1995, Windows started to matter. A brief history of Perl on Windows followed, resulting in what is today ActiveState.

Much of what Adam wrote for PPI does not work in ActivePerl, which makes it a non-starter for him, as he tends to work on Windows. Anything depending on Scalar::Util or List::MoreUtils modules will not work with the ActivePerl build system. This led to an embarrassing problem for Adam when he gave a talk three years ago at OSCON. He couldn’t give his demo, because PPI would not build in ActivePerl. In fact, ActiveState’s package manager has gotten so much worse that almost any module that is at all useful does not exist—and thus nothing useful can be done on Windows (big surprise).

Moving away from ActiveState, this talk is essentially about Adam trying to get his own laptop to work. That’s really all he wants. It’s a modest desire. More importantly, the CPAN module has to work. Without that, what’s the use of Perl?

So Adam offered a prize: a yard-high stack of cases of any beer desired by the first person who could provide a fully-installable and working (by the above definition of working) version of Perl for Windows. After six months and no sign of a winner, he changed the prize to “craploads” of beer. In 24 hours, he received two entries. The winner cheated a lot, but the loser was Vanilla Perl, which has become a testing ground for experimentation.

Strawberry Perl is the Perl for Windows designed for people who don’t use Windows. That is, the people who do all of their work on Unix or Unix-like systems—Linux, Solaris, and Mac OS X. The main goal of the project is to make it easy—it is Perl, after all.

In the future will come Chocolate Perl—completing the holy trinity of neopolitan flavors—for people who know Windows, but don’t know Perl, and thus the Unix-like characteristics of Perl.

The target of Adam’s financial support is Portable Perl: Perl for flash drives. Carry it around, install CPAN modules onto, or from, the flash drive. It’s network-aware, does the right thing, and juliennes fries. An excellent standard being developed for portable apps is, in fact, PortableApps.com, where applications such as Firefox or Putty can be downloaded and installed to those ever-growing flash drives.

Available Thursday at the Perl Foundation‘s booth in the expo hall will be branded flash drives with Portable Perl on them. At least, I think I heard that correctly.

I really like the work Adam is doing. He’s accomplished so much to get Perl everywhere. That’s a cause I can get behind.

“The main problem today is Vista.”
— Adam Kennedy

Okay, I took that out of context, but I couldn’t resist capturing the quote. What he really means is that changes made to Windows in Vista have made things not work, in particular the access control. It’s not an unusual problem when upgrading to new systems, but it is more difficult with proprietary platforms, which Open Source authors have very little access to.

Allison is back to tell us that the morning break will be sponsored by Intel, and lunch is sponsored by Google. That gives me some hope for a decent lunch, at least. Don’t let me down, Google.

Next up, Tim O’Reilly with an update on Open Source on the O’Reilly Radar. He started out with an overview of the history of this conference, in particular the predecessors: the Freeware conference, and the Perl conference.

He offers an important safety tip: keep your history. Be an e-pack-rat. Some day you’ll look back and appreciate that you have it. It’s like the photo album on the coffee table. It’s the story of us and how we became who we are today. So keep everything. Please. Even if it’s embarrassing. Those are always the best memories, the ones that make us laugh.

The big point he’s here to make today is how big Open Source has come in the last decade. But, don’t become complacent. There are three big challenges and opportunities coming up: cloud computing, the (open) programmable Web, and open mobile.

Cloud computing is on the tip of everyone’s tongue today. From Amazon Web Services to Google’s App Engine. Individuals and start-ups now have the ability to build applications on top of these wonderful, decentralized, and most importantly cheap platforms.

Web does not mean “http.” It is, in fact, the entire Internet, the “web” of systems that communicate and inter-operate. There are Web applications that provide platform-agnostic solutions, but there is also XMPP, mobile devices, and even non-Web APIs for those very Web applications that are often so impressive.

“The Web is 72 subsystems in search of an Operating System.”
— Tim O’Reilly

Data is the value-add by so many of the so-called open web companies. While the APIs are open and the data can be queried, the data itself is owned by the provider, to do with as they please. We need a truly Open Web Platform. Apple, as popular as the iPhone is, has created an essentially closed platform. Google, with Android, understands this. Without a truly open mobile platform, all of Google’s market share could potentially disappear overnight.

Back to Allison who introduced our next speaker, Christine Peterson. She takes the stage to tell us about Open Source Physical Security: Can We Have Both Privacy and Safety?

We passed up an opportunity with “e-voting.” The Open Source community should have been able to rise up and solve that problem. I’m not sure how or in what way. I’ve had many discussions with friends on the subject, and we’re still not convinced that computers are even a good idea when it comes to voting.

This is the political activism segment of the conference. That said, she brings up very real concerns. There are very real reasons to care about detecting weapons or other hazards. But, the very same technologies, in particular surveillance, that are used to defend against very real dangers can be used—abused—to monitor law-abiding citizens.

Terrorism is a “bottom-up” problem, which the state is attempting to solve with “top-down” solutions. We need so-called bottom-up solutions. The solutions that involve the very same openness, security and privacy that the Open Source community is already so concerned about and already so vocal about.

The take home message, if there is one, is that all this public sensing data and the information they gather should be open. Our elected officials (this is a very US-centric talk) are well-meaning, but do not have the tools or the knowledge or the experience to really understand the need for all of this to be open.

“No secret software for sensing public data.”
— Christine Peterson

Allison came back on stage to introduce our last, but certainly not least, speaker, Dirk Hohndel, Intel’s Chief Linux and Open Source Technologist. He’s here to talk about Moblin, Linux for Next Generation Mobile Internet. Given that I work for Qualcomm, this is, or at least should be, a very interesting topic for me (I work in support of the engineers, who do the actual work).

Intel is putting their money where their mouth is with Moblin (Mobile Linux, get it?). There is a new class of computers on the market, which have become affordable for the mass market: ultra portable notebooks, hand-held tablet computers, and “smart” phones. The driving force making these devices so successful is the Internet. They are connected and our data is accessible from anywhere.

But what about vendor lock-in of the platform and the data. Intel believes that the platform should be open. This is where Moblin comes in. It’s Intel’s idea of an open platform and an open software stack, allowing the community to develop applications and create new systems and services.

It’s excellent preaching to the choir, but I suspect that from a business perspective, it’s also a way of getting other people to do work for free and really get entrenched in the mobile market. After all, Intel is not the giant in the mobile space the same way that they are in the server, desktop, or notebook spaces. In fact, Qualcomm has a very impressive microprocessor, called Snapdragon, targeting the mobile market (shameless plug).

Allison is back, once again introducing Tim O’Reilly, who will be talking to Monty Widenius and Brian Aker about their work with MySQL and the acquisition by Sun Microsystems. This is a Q&A session, and I always find these difficult to blog. With any luck, a summary or transcript will be posted to the O’Reilly Radar site.

That brings us to the end of this morning’s keynotes. I’ll drop by the expo hall for a few minutes before my first session. But first, I really need to find a restroom.

Oh, Brad also wrote a few words about the keynote.

The morning keynotes begin in approximately 45 minutes. After that, I have only a vague idea of which sessions I’d like to attend. My current line up looks a little like this,

• Strawberry Perl: Achieving Win32 Platform Equality
• Beautiful Concurrency with Erlang
• Perl 6 Update
• Rakudo: Perl 6 on Parrot
• Moose: A Postmodern Object System for Perl 5
• An Illustrated History of Failure

Of course, any of this is subject to change without notice.

Originally, I hadn’t planned on arriving at the keynote until 9:00pm, when Damian Conway is schedule to speak on Temporally Quaquaversal Virtual Nanomachine Programming In Multiple Topologically Connected Quantum-Relativistic Parallel Timespaces…Made Easy!. I mean, granted, I’m sure I already know all there is to know about it, but it still might be a little interesting.

Anyway, the keynotes got started with Mark Shuttleworth, the founder of the Ubuntu project. He’s here to speak to us about “Free software and the art of software engineering.” It (whatever “it” is) boils down to three things: innovation, methodologies, and economics.

Innovation. Society has a responsibility to stimulate it. Innovation is extremely non-linear and the key to this is disclosure, as is done in (or was once done in) academia. Free Software is the scaffolding for innovation. The real successes are accessible. The Mozilla products are examples of wildly successful open platforms, with the extension architecture they have provided.

Methodologies. The purpose of methodologies is to organize talent. How is Free software changing the direction of these methodologies. The Free Software people, that is us, are organized and motivated by interest. A second driving factor is that developers are almost never located near each other, so things like pair programming completely fall apart. Creating architecture for collaboration and participation is essential to the success of any Free Software process. While a common set of tools can never be forced upon the community, the ability for a diverse set of tools to communicate with each other is vital.

Economics. It is the combination of the technical change and innovation in economics that really moves the world forward. For example, we had the Web for years before the business models started to spring up around it and really drove us forward, both technologically and economically. Today, there is an increasing use of online services, which both drive technology forward and allow platforms to work together, and more often than not, these services are built on Free Software.

Our great task over the next two years is to lift the Linux desktop from something that is stable and works and is not-so-pretty, to something that is art. At this point, someone started clapping, and a couple of people joined in. As Jaime Zawinsky once said, “We should design software that helps our users get laid.” But really, we need to make software that is phenomenally useable, beautiful, and functional.

Next up, Chris DiBona, the Open Source program manager at Google, joined Allison on stage to present the Google O’Reilly Open Source Awards.

Next up, with Exceptional Software Explained: Embrace Error is Robert “r0ml” Lefkowitz. He is fast becoming one of my favorite speakers. He’s here to talk about software development methodologies in Open Source. This talk is almost a sequel to one he gave last year, An Open Source Lexicon. He has a real penchant for language, particularly classical language, and how to apply it to themes in the Open Source community. Unfortunately, because of this very quality, it’s extremely difficult to write about it as he speaks. It’s hard to summarize as he speaks, and he’s far too entertaining to chance missing what he’ll say next.

Josh McAdams then took the stage to continue the long standing tradition—10 years now—of the White Camel Awards. So here’s something I don’t understand. What is it that drives people to design award trophies that have a high potential for lethality? Honestly, don’t run with them. They’re worse than scissors.

Finally, it’s time for Damian’s keynote. But you know what? I’m not going to miss any of it to write about it here. If you missed it, well, you should have been here.

Over 90 people registered for this tutorial, and the room is almost full. Save for the handful of available chairs, I’d feel guilty about auditing it instead of attending the Real Time 3D on the Web with Open Source I had originally registered for. This will be a two and a half day course compressed into three hours. Should be fun, and useful for Kevin’s session tomorrow, Beautiful Concurrency with Erlang. After seriously considering the relative merits and general usefulness of the tutorials, I decided Erlang would be much more interesting. I had made my original choice with the equivalent of a dart board, so I don’t feel too bad about changing my mind.

The tutorial started with a quick tour of Erlang’s syntax. It looks odd, but I’ve used Lisp and ML in the past, and I’m a rather good Perl hacker, so it isn’t proving too difficult to pick up. The concept of pattern matching intrigues me. It appears to use equivalency, in the mathematical sense to handle both boolean and assignment operations with the same syntax. For example,

[A,B,C] = [1,2,3]    % A is 1, B is 2, C is 3
[A,B,C] = [1,2]      % error, size mismatch
[A,B,A] = [1,2,3]    % error, A already bound to 1
[A,B,A] = [1,2,1]    % okay, A bound to 1, then equivalent to 1

Shortly into the discussion of syntax, Francesco asked that anyone who hasn’t yet installed Erlang do so. I executed yum install erlang, which pulled in unixODBC, tcl, and tk as dependencies. Well, 45 megabytes and 45 minutes later—an impressive speed of 1 MBpm—I now have Erlang installed and ready to run. Just in time for a 10 minute break.

During this first break, we were asked to do a simple exercise in Erlang: write a module, boolean.erl, that implements b_not(), b_and(), b_or(), and b_nand(), without using the built in logical operators. I’ve been able to define the structure of the module, but I don’t know how boolean values are represented in Erlang, so I may have to wait until he gives us the answer. Vim’s syntax highlighting tells me that true and false are reserved words, so I can use those.

The solution for this involves writing a simple truth table. In Erlang, functions are subject to pattern matching in the same way that many programming languages allow for function overloading. For the logical or, we start with the basic truth table:

b_or(true,true)   -> true;
b_or(true,false)  -> true;
b_or(false,true)  -> true;
b_or(false,false) -> false.

That’s downright simple and extremely easy to grasp on a conceptual level, particularly for anyone with any background in mathematics. However, and this appeals to me as Perl hacker, Erlang allows the programmer to be lazy, but in a good way. The null variable—as I’m calling it due to the analogy with /dev/null on Unix-like systems (or undef in Perl)—_, allows a kind of lazy matching:

b_or(false,false) -> false;    % the only false case with OR
b_or(_,_)         -> true.     % any other case is true

The other functions can be written in a similar way.

Back from the break, and the population of the room has thinned very slightly. Francesco immediately jumped into conditional evaluation, starting with the case clause. I suspect this may be one of the answers to the exercise. He followed that with the if clause. I find it interesting that he’s done it in that order. In most languages, the if statement is a much simpler case (no pun intended) and is covered first, before moving into more complex territory. I think I understand why, the two clauses are implemented in a very similar fashion. I’m not sure how equivalent they are, I’d have to play with them a bit.

As with any functional language, Erlang has strong support for recursion as well as a handful of built in functions (BIFs) implemented in C to accomplish things that are difficult or impossible to do directly in Erlang. After all, at a certain point, things like date and time require system calls. Also available are convenience functions to do things like convert tuples to lists or back.

At the second, official, break—taken after an official entered the room to scold Francesco for being 15 minutes late—we were presented with two more exercises. First, to write a function, sum/1, which, given a positive integer N, will return the sum of all the integers between 1 and N. As an extension, write a function, sum/2, which, given two integers N and M, return the sum of the interval between them, first ensuring N <= M. Second, write a function, create/1, which will return the list 1 through N given N as its argument. As an extension, write a function, reverse_create/1, which does the same in reverse.

As I suspected, both exercises are perfect candidates for recursion, which is quite simple to do in Erlang:

sum(N) when N > 0 ->
    N + sum(N-1);
sum(0) ->
    0.

The simpler list creation function is actually the second, and is solved similarly, but by accumulating a list instead of adding to a sum (which is, actually, also a method of accumulation):

reverse_create(0) ->
    [];
reverse_create(N) ->
    [N|reverse_create(N-1)].

The first thing I notice is, again, how mathematical Erlang is. The solution is written in exactly the same way I do it when I’m jotting down notes while thinking about how to solve the problem. To me, the syntax is quite elegant.

After going over the solutions to the exercises, we moved into concurrency. As with most languages worth using, Erlang has a spawn() BIF, used to create processes. What’s interesting about spawning processes in Erlang is that the function to do it does not take a system command. Rather, it takes another Erlang function to run. It’s quite a bit more elegant (there’s that word again) than the equivalent fork() dance done in most imperative languages.

Communication between Erlang processes is done via message passing; data is never shared. As with everything else, the method for doing so is quite elegant: Pid2 ! {self(), foo}. Okay, maybe someone has to be me to find that elegant.

The whole process concept in Erlang is quite nice and, again, elegant. It’s plain that it is the primary method by which systems in Erlang are designed. So far, though, we’ve only seen trivial examples. That’s okay, because this is only a three hour tutorial. However, as Larry Wall once said about Perl: It makes the easy things easy and the hard things possible. It’s a good litmus test for any language. It’s far too early for me to pass any judgment on Erlang. I’d like to use it in anger sometime, to see how it performs for me. Perhaps I can get my local Perl Mongers interested in chatting about it.

Unfortunately, the first appointment Dan could get at the Genius Bar is for 8:00 AM Wednesday morning. The girl who entered his appointment asked about the problem and, while he was describing it, I noticed that the computer wasn’t turning off. I flipped it over, took out the battery, replaced the battery, flipped it right, and turned it on. We were hopeful at first, as the login screen came up, but the screen went dark again.

Or did it?

Upon closer inspection, the display was on, but the back light wasn’t. Al stepped up to squint at the display and attempt to reboot the machine so he could reset the NVRAM. In what I expected was a futile move, I pulled out a flash light and aimed it at the Apple logo behind the screen. It illuminated just enough for Al to locate the cursor and get the system to reboot.

After the reset and the reboot, Dan’s computer is working again. I asked for a genius badge, but they didn’t seem interested in letting me have one.

Most of us are, of course, aware of the concept of best practice when coding. Writing code that’s maintainable, predictable, and follows the rules. Oh, and uses Java.

Worst practice is, by contrast, code that is obfuscated, unmaintainable, and breaks all of the rules. Today, we will be studying code that Damian has submitted to the Obfuscated Perl contest. This promises to be very, very scary.

Damian’s entry to this contest was SelfGOL, a program capable of self-replication, rewriting other Perl programs to themselves self-replicate, detecting un-rewritable programs, playing Conway’s “Game of Life,” and, as if that wasn’t enough, animating any text as a cycling marquee banner. The main constraint of the contest is that the entry must be under 1,000 bytes of code, so it shouldn’t be too difficult to understand. Obviously it doesn’t use any modules, because that would be too easy. Not only that, but it doesn’t use a single control structure. This is going to be great.

Following an amusing demonstration of SelfGOL, we moved into treating it as a case study for a set of principles. Principles that will focus on the very practices SelfGOL embodies, and why they should never, ever be used. As I intend to enjoy the discussion, I won’t spend much time writing about the discussion and examples accompanying these principles, but rather simply note the principles for my own benefit (documentation for the win). After all, sharing all my new tips and tricks would suck all the fun out of it.

Principle 1: Sane and consistent layout makes code more maintainable (but it isn’t a magic bullet if the code itself is beyond help).

Principle 2: Using built-in features isn’t necessarily smarter or cleaner (even though fellow developers’ futile struggles to recall those features can be highly amusing).

Principle 3: Obscure obsolete features are obscure and obsolete for a reason (and restasking them for even more obscure purposes is not helping).

Principle 4: Each statement should do one thing only (since that’s the upper limit most brains can comprehend).

Principle 5: Relying on default behavior makes code very slightly easier to write and vastly harder to read (because most readers can see better than they can think).

Principle 6: Randomly placed subroutine definitionss are static (in the radio interference sense).

Principle 7: Choose data structures that simplify your task (even if the task is to make those data structures incomprehensible).

Principle 8: Just because you use some operation frequently doesn’t mean it should be in a utility function (especially if it’s in a function merely to abbreviate its name).

Principle 9: Encapsulating the familiar can decrease maintainability (refactoring isn’t a substitute for sanity).

Principle 10: Treat any clever one-line solution as an alarm bell (or as an antipersonnel mine with a six-month delay fuse).

Principle 11: Familiarity breeds comprehension (it breeds contempt (but hey, what’ doesn’t?)).

Principle 12: Table-driven solutions are clean, efficient, and extensible (as long as you don’t mind losing a little comprehensibility).

Principle 13: Building a messy data structure and then cleaning it up is often easier than building it cleanly in the first place (and to hell with the purists).

Principle 14: Some code is better compiled at run-time (but the urge to use eval is Nature’s way of letting you know there’s not yet enough pain or misey in your life).

Principle 15: Parentheses are our friends (cos, if you can remember all 24 levels of Perl’s precedence, you gotta get a life, dude!).

Principle 16: Edge cases suck (and edge cases of familiar constructs suck worst of all).

Principle 17: Code should do what it seems to be doing (especially when it seems to be doing something subtle).

Principle 18: Conceptual elegance is no guarantee of actual maintainability (nor a good substitute for it).

Principle 19: If you’re going to have default values, define them near the place they may actually be used (or, at least, somewhere they have a slim chance of being discovered).

Principle 20: No matter how good you think your error messages are, they’re still too brief, too obscure, and too hard to decipher (even if you’ve already taken Principle 20 into account).

Principle 21: Avoid using obsolete and arcane magic punctuation variables with unfamiliar default values and unexpected global effects (even if you happen to enjoy a little self-inflicted pain in other recreational activities).

Principle 22: The fundamental complexity of any problem is irreducible (optimizations merely redistribute the pain differently).

Principle 23: Code that breaks when it’s reformatted is already broken (though on a much more profound and interesting level).

Principle 24: If it’s impossible to understand, it’ll be impossible to maintain (on the bright side, of course, such code is highly stable).

This last one should, but often doesn’t, go without saying.

Principle 25: Phenomimetic retrodeterministic nominativism generally does not improve code comprehension (then again, did it sound like it would?).

Principle 26: Don’t allow dynamic behavior to violate static expectations (and the easiest way to do that is reusing over-scoped variables for unrelated purposes).

Principle 27: Explicit behaviors are better than implicit behaviors (especially when the specification of the implicit behavior is syntactically baroque and hard-to-spot, and the behavior itself is unknown to the majority of developers).

At this late point of the tutorial, Brad pointed out to me that all of these principles are in the included materials. Now that I’ve already transcribed so much from the slides, I don’t have the heart to delete it all. Of course, since I haven’t been commenting on all of the black magic to this point, there would then be very little in the end to post. Brad also has a much better post about this tutorial, since he actually took real notes.

Principle 28: Code that pre-caches or precomputes its data is much easier to maintain than code that caches or computes on-the-fly (when you’re running at multiple gigahertz, acquiring your data a few thousand operations early is still plenty JIT enough).

Principle 29: Coding is an art, but code shouldn’t be art (evolution made programmers boring, pedestrian, and aesthetically challenged for good reasons).

It’s mesmerizing to listen to the thought process behind Damian’s obfuscated code. I can’t help but wonder if this well-organized, well-thought-out explanation is anything close to how Damian designed this program. Or, rather, if there are extremely convoluted, scary, and most importantly, evil gears grinding away inside his head. In fact, I suspect this entire tutorial may have been designed purely as a way of documenting SelfGOL so Damian himself can remember how it works. Clever.

This kind of programming is silly and fun, but it serves a real purpose. Pushing the limits of a language teaches about its dark places. The understanding that comes from it vastly improves the skills of the programmer, even if—especially if—the bad things are never, ever used. Perl, even more than other languages, encourages this kind of play, thanks to its rich diversity and culture.

Important safety tip: keep these tricks and contrivances for recreational purposes only.

I don’t know what’s more disturbing, how much of the tutorial I understood, or how much I already knew coming in.

[tags]oscon, oscon08, Perl, Damian Conway[/tags]

I have a fun day lined up. This morning I will attend Perl Worst Practices in Portland 252. I’m looking forward to this tutorial, particularly because it’s being taught by Damian Conway. I—as well as my boss, I’m sure—am excited about the prospect of putting these practices to work when I return to my job next week.

After the lunch break, which will probably be spent across the river again, I am signed up for Real Time 3D on the Web with Open Source in E143/144, being taught by Matthew Edwards. I’m not sure what to expect from this session. A week prior to the conference, I received an e-mail instructing me to download a set of programs, including Blender and Inkscape. This is well out of the ordinary for me, so I’m not sure what to expect. I hope it will be fun, but if not, I may duck out and into the Practical Erlang Programming in Portland 256, which Al is attending.

A half hour now until my first tutorial. Time enough for more coffee.

We started the night at Kells Irish Restaurant and Pub on the other side of the Willamette. The hostess there was extremely attractive, even if some in our party made note of how young she appeared. As it’s rude to ask a woman her age, I refrained from doing so. After a few beers and sweet potato fries, we needed to find food. So we decided on Italian, and Mama Mia Trattoria fit the bill. Near the end of dinner, I received a text message from Dan. He and his fellow Tierranet attendees were at Paddy’s Bar and Grill. So we made our way over there for a few more pints.

We called it a night before the MAX stopped running, and made our ways back to our respective hotels. Dan and I happen to both be staying at the Marriott and, as we passed by the bar, we saw his fellow coworkers. Not only that, but the barmaid, at that very moment, announced last call. Not wanting to pass up such a coincidence, Dan and I sat down for another pint.

Not satisfied with the early hour, Dan and I decided to walk down to American Cowgirls, a bar across the street from the Oregon Convention Center. Unfortunately, the bar is closed on Sunday and Monday, so we ended up calling it a night and heading back to our rooms.

Ah, but it’s only Monday night, and OSCON runs through Friday. It will be a good week.

“A computer is secure if you can depend on it and its software to behave as you expect.”
—Simson Garfinkel and Gene Spafford in Practical UNIX & Internet Security

In a nutshell, that’s what security is. If a computer behaves as expected, it is secure. That is, unless it’s expected to be insecure, I suppose. I’m not sure I’d enjoy that situation, so I’ll assume the assumption of expected behavior is both expected and secure.

Most security boils down to common sense. Unfortunately, this mythical state of being is far less common than its name would imply. Sad, but true. People are often lazy or distracted, and these usually lead to really stupid mistakes.

There is a key acronym when thinking about security: CIA. No, not that CIA. Yes, I thought so, too, at first. What it really means is, Confidentiality, Integrity, and Accessibility. Confidentiality, because information will not remain secure if it does not remain confidential. Integrity, because information must remain known and trusted to remain secure. Accessibility, because denial of access to information may result in insecurity. I may not have done justice to this acronym, because the tutorial moved on quickly after this point. I’m sure there are web sites dedicated to security that can better define the term.

Perhaps the most important piece of advice for the unwitting Perl programmer is to always perform data validation. Never, ever trust input, regardless of where it came from. Fortunately, Perl provides Taint Mode, which forces the program to mistrust input.

Paul shared with us a variety of examples to demonstrate why input should not be trusted, as well as a number of examples of how to properly untaint data. As with anything, it’s easy to become lazy when untainting data, which can sometimes be as bad as not using Taint Mode at all.

The tutorial continued into what is essentially a list of best practices to follow when programming securely with files.

• Do: Use the three argument version of open(), to prevent attacks using file names with magic characters in them.
• Do: Use sysopen() instead of open(), which provides ways to avoid overwriting a file, thus helping to prevent symlink attacks often as a result of race conditions.

The common attack vector in so many of the examples given so far has been via file names. Wouldn’t it be great if we could write programs without file names at all? Well, when working in a Unix-like environment, we can. Perl has the ability to use anonymous files by passing undef as the third argument to open(). He was even kind enough to provide us with a way of passing these anonymous file handles to child processes, by disabling the close-on-exec flag prior to calling system(). Sorry, the slide went by too quickly for me to transcribe the method. It, along with all the other examples, are available online.

Calling system() and using backticks make Paul really, really angry. Why? Because doing it right is hard. In fact, just correctly checking the result in $? requires 10 lines of code, according to the documentation for system() in the perlfunc manual page. So, 10 lines just to verify that a single line of code executed successfully.

I briefly became distracted by news of a fire back home. However, what I was able to get is that Paul has written a module, IPC::System::Simple, which, as the name implies, makes the process of calling system commands quite simple.

After the mid-afternoon break, we ventured into setuid and setgid programs. Perl provides ways to determine who is really running the program ($<, $() and who is effectively running the program ($>, $)). Perl is, however, ignorant of the saved UID, which is the third UID in Unix, along with real and effective. Unfortunately, the standard for setuid scripts is confusing and implemented differently on various systems, so don’t use it. Really.

Even worse, the $< and $> variables are cached by Perl, so they may lie to the program, especially when using the setresuid() system call to properly drop privileges, as recommended. Fortunately, another useful module from Paul, Proc::UID provides a solution to this caching problem.

Now we move into DBI security. SQL injection attacks are very similar to the file name or shell attacks covered previously. Any database programmer worth his salt should be aware of the hazards of composing SQL, so I won’t go into the examples here. Programmers should, of course, use placeholders if they’re available. The DBI module itself provides its own Taint Mode, both for input and output, adding all the benefits of Perl Taint Mode to database interface code. Even better, it can be controlled on a per-statement basis.

All of this careful taint checking we’ve done and Perl may end up sabotaging us anyway. When presented with files on the command line, Perl is happy to just open them using the simplistic, dangerous, single argument open() call. Typically, this is done when using the <> operator in a while loop. Also, everyone forgets to use Taint Mode in cron jobs. Don’t do that. Really.

Because Perl is written in C, the null byte becomes very interesting. While it is a perfectly valid character in Perl strings, it marks the end of a C string. In most circumstances, this is not a problem. However, it can mean bad things when making systems calls, which are written in C. Normally, at a terminal, null bytes don’t occur in user input, unless that input comes from the Web. Null bytes can be trivially represented by the %00 escape sequence.

I need to go through the list of Paul’s modules, since they appear to be ideal for the type of programming I tend to do, as an IT developer. In fact, he’d like to see some Solaris patches for Proc::UID, so I can probably help him with that.

I noticed during the tutorial that Paul must read the Fail Blog and I Can Has Cheezburger, or at least knows someone who does. Quite a few of the images that have appeared on his slides have graced the pages of those web sites.

As an added bonus, the tutorial ended 40 minutes early, and Paul had bonus material. What a guy.

The tutorial, and with it the day, is now over. It’s time for dinner, then maybe a BOF session or maybe just a trip to a pub.

[tags]oscon, oscon08, perl, security[/tags]

The idea behind Mastering Perl is not to talk about Perl to a group of Perl masters. Instead, it’s about mastering Perl in the guild sense (and not of the SCA variety). Back in the day, and still existing in some professions today, there was an apprentice system. A neophyte—in today’s nomenclature, a noob—would begin acquiring skills under a master of the art. As he progressed, he would be entrusted with more and more responsibility, until finally he became a master himself and took people under his own wings.

This apprenticeship system, somewhat unfortunately, does not exist in the computing world. That’s where brian d foy feels that Mastering Perl fits. Lacking true masters, the book acts as a substitute. Someday, we may even create a guild system. But then we’d probably have to pay dues and follow rules, and that’s not very attractive. That said, it’s the model I’m hoping to use at my own place of work. I’d like to hire one or two developers who I can take under my own wing and mentor them in the ways of Perl and the grid.

The first two topics covered are tools for optimization, profiling and benchmarking. Often mis-attributed to Donald Knuth, Tony Hoare once said, “Premature optimization is the root of all evil.” What this means is that one should never assume what requires optimization. Let the testing be the guide.

While profiling is objective, benchmarks, like statistics, are not always objective. Everyone has an agenda and benchmarks are subjective. Often, benchmarks are short-sighted. For example, benchmarking code run time and attempting to optimize for it may not be worth the expense of the developer time required to make the requisite changes. It’s worth analysing what is important before blindly following benchmarks.

I’ve been on the receiving end of misplaced premature optimization. I worked with a development group that put far too much emphasis on achieving perfect results on their Devel::Cover reports. This led to strange bugs in their code, and a strong belief that “new() doesn’t work that way.” As it turns out, their test suite was calling new() in two ways. I forget what the second method was, but it was not used anywhere else in their code. However, in order to get this test code to run, and get 100% coverage, they added code to the constructor for every class. Code that prevented inheritance of the method. The team then convinced themselves that constructors could not be inherited in Perl, rather than realizing that their own habits were the problem.

After the mid-morning break, we wrapped up the discussion on profiling and benchmarking, and moved into configuration. This is a vital topic for anyone who desires the ability to pass a program off to users without being bothered to modify it later in response to users’ desire to customize the program for a slightly different use.

External configuration, particularly via the command line, is something I depend on heavily, even in very simple Perl or Bourne shell scripts. I almost always create command line options for performing a dry run or output debugging information. Not only are these useful for development, they can live on in the final program, providing help to the final user, who more often than not is me. Sometimes I will even add configuration to values that never change, just for when they eventually do.

Jumping past configuration, we move on to logging. It’s really easy to add to a program, and it’s really useful to leave in a program when it’s released. The ability to enable logging on the fly sure beats adding a bunch of print() calls in the code when it inevitably breaks at three in the morning. The Log::Log4perl module is a particularly powerful method of adding logging to programs. It’s well worth investigating for anyone who wants to easily add logging functionality to their code.

The final topic of the day is lightweight persistence. It’s always nice to have data stick around between program invocations. The easy way (and everything in the second half of the tutorial is easy) to add persistence to code is to not use DBI. While DBI is powerful, it also tends to require a database server (ignoring SQLite for the moment). Modules such as Data::Dumper, YAML or Storable are ideal for easily storing and retrieving data in code.

After the tutorial, brian will be available at the Powell’s Books mini store, located near the registration desk, to sign copies of Mastering Perl. I already have a copy, thanks to my local Perl Mongers group, but it’s all marked up with the group name, and I wouldn’t mind having a signed copy.

Now it’s time for lunch, which is good, because I’m quite hungry. I hope the conference-provided lunch is decent during the tutorials, as it was last year.

[tags]oscon, oscon08, perl[/tags]

As is my habit, I arrived at the San Diego airport extra early—two and a half hours in this case. I was extremely pleased to see no lines, at the check-in counter or security, when I entered the terminal. Unfortunately, I was immediately told by a customer service agent that there are air traffic control delays for flights in and out of San Francisco today. As a reward for my promptness, I was rebooked on an earlier flight, which was supposed to depart at 10:21 in the morning—approximately half an hour before I arrived at the counter. Once I got through to the gate, which was pleasant with only one person in front of me in the security line, I discovered that it had been scheduled for 11:45. As I wrote these words, it was announced that the flight had been released and boarding would being immediately, at 11:25.

The flight itself was pleasant, if boring. The plane was not full and I was fortunate to receive an aisle seat with a small Asian girl next to me. While complimentary soft drinks were provided, I couldn’t help but notice that the snacks, so common on domestic flights, were nowhere to be found. Another example of airline cost savings, no doubt.

We touched down in San Francisco about 10 minutes after one in the afternoon. My connecting flight to Portland won’t depart until approximately 5:30 in the evening. That leaves me with some four hours to kill in an airport without free wifi. I need to compile a list of airports that offer free access to the Internet, so I can be sure to book trips only through those.

It’s still too early for my connecting flight to be displayed on United’s monitors, so I’ve sat down in an uncrowded restaurant, the Buena Vista, where I’m writing this. I’ve ordered a Gordon Biersch Marzen and a reuben with cole slaw. It’s actually quite good.

I had considered attempting to stand by on an earlier flight to Portland, but the lines are long, and I have baggage checked through. I’ll just enjoy the time I have available to me to both relax and jot down whatever comes to mind my my new Moleskine notebook. Hopefully, the monitors will display my flight’s gate soon, so I’ll know the best place to find a seat.

I’m writing this now from my seat on the MAX light rail, heading to the Oregon Convention Center stop. I’m staying in the Courtyard by Marriott, a couple blocks north of the OCC. The flight out of San Francisco was delayed, but only by about 20 minutes. I managed to sleep for most of the time we were in the air, so I’m feeling pretty good right now. I’m looking forward to checking into my room and finding something for dinner.

As I was composing this final piece of my entry, I received a call from the fraud prevention department of my bank. At least now I know why the MAX ticket kiosk wouldn’t accept my credit card. How annoying.

Tomorrow, OSCON.

Though I don’t do it very often, I really do enjoy visiting places away from home. Unfortunately, I don’t often enjoy the act of getting there. It seems that the sole purpose of the US airline industry is to make things as inconvenient as possible for travelers. They’re not alone, however. When they’re not up to the task, the US government, in the form of the TSA, steps in to take up the slack.

Most of the time, my trips are uneventful and I end up getting worked up for nothing. Last year, though, my checked luggage ended up on a different flight than I did. Fortunately, both of those flights were bound for Portland, so my suitcase was delivered to the hotel later that same evening. Here’s hoping my trip tomorrow is uneventful.

One thing I’ve learned is that I get the same mail week after week. Before this experiment, I’d never paid much attention to my mail. If it looked like junk, it got dropped into the recycle bin without so much as a second thought. Now that I’ve been paying attention, I’ve seen the patterns. On Monday I get such-and-such advertising circular, on Tuesday I get another. About every four weeks, I’ll get a solicitation for the same business. It’s awfully redundant. Though I understand the need for repetition when attempting to sell a product no one actually wants.

So I won’t be bothering to post the fascinating week-by-week updates. I have continued to collect all of the data, and I will still present a result after the third month. So far, though, it’s not looking good. In fact, for some things, I may switch back to paper—the electronic alternatives aren’t quite as useful.

A couple of things resulted from this change. First and foremost, we have a lot of slack to take up, so the rest of the year will be very busy for us. Second, I am now the de facto lead developer in the group. A group for which we need to hire two more developers (we had an open position before the loss of our comrade).

Two fresh, new, dreamy eyed developers. For me to lead, to teach, to mold. I like to think of these potential developers as my minions, willing to do my bidding.

For a while, we filled our open developer position with a temporary employee. We tasked this person with the creation of a process work flow for our development efforts. Something we could use to identify tasks, categorize them, prioritize them, assign them, and sometimes even work on them. The final result of this effort looks something like this:

No, no, no. This will never do. I can’t use this. Look at how many boxes there are. Not only that, look the sheer complexity introduced by all those decision branches! I could never trust my minions with so much independent thought. Also, I have no desire to confuse my minions any more than they already are. So I designed a new process flow, which I believe is far simpler and easier to remember.

Yes, this is more like it. I suspect even the simplest of minions can effectively follow this process. And if they can’t, well, we have ways of dealing with them.

So I need minions. There are a few requirements, however.

• Familiarity with Perl (other programming languages are acceptable—except Python)
• Experience administering Linux (or another Unix-like system, I guess)
• Fascination for grid computing
• Misplaced enthusiasm for supporting users
• Blind devotion to me

Not necessarily in that order.

My task this week was to compensate for one of these bugs. Basically, the request was to somehow lie to License Scheduler’s data collection process, convincing it that the license counts are different than the reality. The collection process uses Macrovision‘s lmstat(1) command to gather license counts. Okay, no problem. Twenty lines of Perl later, and I have my own lmstat command, which behaves identically to the real version (which I simply execute) except the license counts have been altered.

In my group, we’re supposed to be working primarily on projects. All of these projects are assigned awkward, forgettable acronyms. So I decided that this project needed an acronym, too. Not just any old acronym, either, but something memorable. After a bit of searching through /usr/share/dict/words, I finally settled on Project FALSE: Falsifying Answers in the License Scheduler Environment.

So with my quick hack, I’ve both defeated an expensive piece of software and won the prize for the best project name so far.

Periodically, I will run a speed test, just to gather data points. I’ve consistently seen a sustained downstream rate of 1.6 Mbps. Recently, the service has felt slower—sometimes unbearably so. I ran another test this afternoon:

Download Speed: 1520 kbps (190 KB/sec transfer rate)
Upload Speed: 276 kbps (34.5 KB/sec transfer rate)

Seriously? This is high speed?

Somewhere I’ve seen Cox advertise rates of 3 Mbps, but I don’t have a reference to this handy. Searching Cox’s web site, I’ve found reference to 15 Mbps. I’m receiving one tenth the advertised rate, yet I’m paying 100% of the price.

Gee, thanks Cox. For nothing.

View Larger Map

I’m sure I’ll add more to this map later. Such as the locations of all the good (and not so good) bars, not to mention the Oregon Brewers Festival.

Monday

Memorial Day in the United States, so no mail delivery.

Tuesday

Mail

None.

Junk

• National Geographic Society renewal offer. As nice as the magazine is, I’ve let my subscription lapse, and I never read it enough to justify receiving it. I can always look through it when I’m enjoying some coffee at Barnes & Noble.
• PennySaver advertisements.
• Valpak coupons. I’m pretty sure I’ve never used one of these.

Wednesday

Mail

• Home owner association account statement and newsletter. I’d prefer receiving this via e-mail. The newsletter isn’t worth the paper it’s printed on.

Junk

• RedPlum advertisements.
• Renewal statement for Martha Stewart Living, which Mrs. sirhc used to receive. We’ve let the subscription lapse, along with most others. Who has time to read all of this?

Thursday

Mail

None.

Junk

• Advertisement for the 17th USENIX Security Symposium. I suppose this could technically be considered mail, because I’m a member, but I’d rather they just sent me catalogs like this via e-mail.
• Advertising circular for Dixieline Home Centers.

Friday

Mail

• Proxy voting materials for one of the companies in my stock portfolio. As I cast my vote online, there’s also an option to receive these materials online, but it wasn’t working when I tried it.

Junk

• AAA travel guide. I’d prefer if this was sent on request. We aren’t likely to be taking a vacation for a while. Not only that, but as stated in the guide, all of these offers and more are available on their web site.
• United Mileage Plus credit card offer.
• Local advertisements from the San Diego Union Tribuine.

Saturday

Mail

• June 2008 issue of ;login:, the USENIX magazine.
• July & August 2008 issue of Cook’s Illustrated magazine.
• June 9, 2008 issue of Time magazine.
• Membership packet from the Zoological Society of San Diego.
• Water bill. Now I can see if they have an online delivery option, too.

Junk

• Solicitation from a dentist in Solana Beach. Technically junk, but it’s one of the more creative solicitations I’ve seen. It’s a kind of welcome-to-the-neighborhood card with suggestions for things to do in the Solana Beach/Encinitas area and includes a coupon for a drink at Java Depot. So I felt he was at least worth linking, even though my dental work can be done at a mobile dentist who comes to my office.

I do feel like I’m receiving less mail overall. This week’s score of mail 7, junk 11, for a total of 18 pieces of postal mail, seems to support that feeling. Real mail this week made up 39% of what we found in the mail box. That’s still quite a bit of junk.

One of the reasons I’m so late in publishing this entry is my desire to create a pie chart that would visually document the ratios of mail and junk I’ve received during the past month. I finally got around to entering the data into a Google Docs spreadsheet. Unfortunately, I didn’t weight the results by true volume, so the resulting chart is slightly misleading, at least depending on how one wants to interpret the data. While real mail did make up a plurality of the total, the circulars were physically quite a bit more weighty (literally).

This experiment has caused me to become more aware of the pointlessness of so much of the mail I receive, even from entities with which I have a relationship. Ideally, there should be a box I can mark when joining to receive everything electronically.

I was chatting with a friend of mine about this experiment, and he gave me one good reason why he prefers paper mail. Accountability. Should he ever need to dispute something with his bank or a creditor, he has records at his disposal. Records that are not easily tampered with. I find this to be a compelling argument. Unfortunately, I lack the storage space in my house for such record keeping (let’s hear it for modern development in Southern California). Also, as a side-effect of living in San Diego County, my electronic records will better survive wildfires, should one ever hit us (we’re actually in a fairly well-protected area).

Retroactively intuitive.

It’s when something, say a computer interface, is completely confusing at first, but is so obvious in hindsight.

I hope it catches on.

[tag]computing, intuitive, interface[/tag]

Not Junk

• Letter from the IRS explaining that I should expect my economic stimulus payment last week. It was direct deposited into my account on Thursday.
• Letter from the Toyota dealer informing me that my Avalon is likely due for its 125,000 mile minor service. They include a coupon, which is nice of them. Cheaper than Jiffy Lube.
• Urgent notice from Time magazine that my subscription requires renewal. This one is borderline. I deliberately cancelled my subscription, but I was a paying customer for several years.

Junk

• My non-partisan voter information guide, which recommends a full slate of Republicans. Strange.
• Store circulars from RedPlum. 35 pages. The grocery circulars are actually folded sideways, so they’re only half the number of real pages; however, they’re big enough to count double.

Tuesday

Mail

• 2008 summer schedule for REI’s Outdoor School.

Wednesday

Mail

• Confirmation letter from my credit union that one of my CDs has been automatically renewed.
• June issue of ZooNooz from the San Diego Zoological Society.

Junk

• One week pass to LA Fitness, with an offer to join for “less than $7 per week.” That’s not quite as good as the $24 per year I pay to 24 Hour Fitness.

Thursday

No mail!

Friday

Mail

• Membership renewal notice from KPBS, the local public radio station. I suspect if I were more diligent about renewing, I wouldn’t receive reminders in the mail.

Junk

• Local advertisements brought to me by the San Diego Union-Tribune. 37 pages. I may not take their newspaper, but they still find a way to send me their advertising.

Saturday

Mail

• Time magazine.
• June 2008 issue of The Costco Connection.
• Summer coupon book for Costco. Not a lot I’m interested in this time.

Junk

• Another vote recommendation guide.
• Advertisement for Cox digital cable. Their internet service is so bad I’m considering looking for an alternative. I’m certainly not about to pay them for digital cable, with an interface much, much worse than my TiVo systems.

That leaves me with 10 pieces of mail and 6 pieces of junk. I notice that not one piece of junk mail was a credit card offer. Maybe this experiment is working?

What’s in the box.

• Netflix Player
• Remote control
• Power supply
• Composite A/V cable
• 2 AAA batteries
• License Agreement and Warranty Statement
• 7 step Getting Started manual

Reading through the simple Getting Started manual, I noticed that Roku has only rated a single star for the quality of my video and three for the quality of my audio. I know, I know, I have a 10 year old 27 inch CRT and I really haven’t kept up-to-date in the A/V arena.

Connections on the back of the box include power, S-video, composite, component, and RJ-45. It supports wireless networking, but since I have a network switch next to the TV for the TiVo anyway, I went ahead and plugged it into the network.

Once hooked up and turned on, the system automatically downloaded an update, restarted, and connected to the Netflix service. Activating the box on my account was as simple as logging into my Netflix account and entering an activation code.

As quickly as that, I was able to start browsing what Netflix calls my Instant Queue. Since Indiana Jones and the Kingdom of the Crystal Skull was released today, I searched for Raiders of the Lost Ark for my first Roku movie. Unfortunately, that title was not available for instant viewing.

In fact, I found very little selection in the Instant Viewing area. For the moment, I’m willing to write this off to the recent introduction of the service. As more people adopt it, I expect more DVDs will be available for streaming.

My mom has been watching the British series MI-5 on BBC America. I don’t receive that channel, so I went ahead and added MI-5: Volume 1 to my Instant Queue. As advertised, it was immediately available on my Netflix Player.

The Netflix Player appears to buffer individual DVD chapters at a time to the player. The buffering went quickly, and the quality of the video was okay. No better or worse than what I usually record on my TiVo. I expect that if Cox was actually delivering Internet to me at the speeds they advertise, I would receive higher quality video. Either that, or the player detects which video cable is plugged in and downloads the appropriate quality stream.

Overall, I really like the Netflix Player and would recommend it to anyone with a Netflix account. However, it may be an impatient wait until more DVD selections are available. I would love to use the Netflix Player as an excuse to cancel my cable television service. Everything I watch is eventually released on DVD, so I’d be able to watch it when I want and without commercials. The one-time purchase price is just right, too, since I already have a Netflix account. Not paying for individual programs is a definite plus.

My entire Netflix Player Set on Flickr.

Monday and Tuesday

Mail

• Stages magazine from Fidelity. Right on the cover, they advertise going paperless. I hope this applies to the magazine as well as their statements.
• @UCSD, a magazine for alumni.

Junk

• Solicitation for some token amount of life insurance for Mrs. sirhc, through our credit union.
• Solicitation from AMVETS to leave donations on the doorstep for them to pick up. I’m pretty sure I get one of these every month, but this is the first time I’ve ever taken the time to determine what it is.
• Solicitation from a junk removal service. They even direct me to their web site. Gee, thanks.
• PennySaver and associated circulars (15 pages, not including the PennySaver and included CouponSaver).
• Local business circulars, from RedPlum, which is apparently a company that specializes in sending circulars. 41 pages.
• LEGO catalog. As awesome as this is to flip through, I can browse their web site just as easily.
• REI catalog. Same as the LEGO catalog.

The RedPlum circulars do include the weekly specials for Sprouts and Vons, which we do frequent (we also shop at my favorite store, Trader Joe’s). Both stores have their weekly specials on their web site, so there’s no problem losing the RedPlum circulars.

Wednesday and Thursday

Mail

• Results for Mrs. sirhc’s last ultrasound. It’s a girl!
• The June issue of San Diego Westways. Part of our AAA membership.
• The June issue of Parenting. Part of a free two issue trial, which Mrs. sirhc has already canceled.

Junk

• Invitation to join the IEEE Computer Society. I’m already a member of USENIX, SAGE, and LOPSA. I suppose I could throw in IEEE and ACM as well, but I’ll first see if work will pay for it. Of all the junk mail I get, I expect the computer societies to be paperless.
• Solicitation for AT&T’s internet, phone, and TV services. Junk, but with the quality of Cox’s internet service, I’m almost tempted.
• Another voting guide to instruct me which way I should vote on the issues. With a little more than two weeks until the election, I expect a lot more of this. My mistake, apparently, was not registering as a decline-to-state voter. I’ll remedy this after the election.
• Solicitation for a United Airlines credit card. I get this about once a month, both at home and at work. I guess they think I’ll eventually break down.
• Solicitation from UCSD’s Computer Science and Engineering department to support their tutoring program. This is what I get for registering for the tutor reunion (and then not going anyway).
• Catalog for Basset, which apparently sells furniture.

Friday

Mail

• Rebate check for my cell phone.
• Rebate check for Mrs. sirhc’s cell phone.

Junk

• Pre-approval notice from our credit union that I’m eligible for an auto loan.
• Pre-approval notice from our credit union that Mrs. sirhc is eligible for an auto loan.
• Local business circulars, consisting of 45 pages.

Normally, the pre-screened offers would bother me. However, we’re actually in the market for a new car right now. Not very green of me, I know.

Saturday

Mail

• Time magazine. Including the warning about my subscription expiring. Darn.

Junk

• Something called NC Magazine. There sure are a lot of community-oriented publications where we live now.
• Get1Free magazine. A coupon book that rarely contains anything I want.
• An informative reminder that I can save on Alamo car rentals because I’m a Costco member. Um, thanks.

Ratio of mail to junk for week 2 is 8:19. More than twice as much junk than mail. It’s a good thing I recycle.

Monday and Tuesday

We never got around to checking the mail on Monday, so the first two days of this week have been combined.

• New home survey from CIDR Systems. This is actually the second copy we’ve received, since I couldn’t be bothered to fill out the first one (they’re kind of annoying).
• Credit card offer from Southwest Airlines. Incidentally, I received this same offer at work. Two pieces of junk mail for the price of one.
• Credit card offer from Chase, advertising their “card factory,” whatever that is.
• Bill from American Express. This was mailed before I opted for paperless billing.
• Greeting card for Mrs. sirhc.
• Several grocery store circulars. I did, however, pull out the advertisements for Sprouts and Vons.
• PennySaver and associated circulars.
• California primary election sample ballots. Yes, we’re having another one this year. No, I don’t know why they couldn’t be combined into one.
• Costco coupon book.
• Postcard reminding me to spend my Costco credit card rebate. Of course, I have already done this, so the reminder is pointless.
• Advertisement for a local tanning salon.
• June 2008 issue of Linux Journal. I don’t intend to renew my subscription. I never get around to reading it anymore, and most of the articles end up on their web site anyway.
• Brochure for the 2008 USENIX Annual Technical Conference. Did I really need a hard copy of this?
• AAA offer to upgrade my membership. Just like last year, and the year before that, I’m not interested.

Wednesday

• Another greeting card for Mrs. sirhc. Well, we are expecting a baby, and Mother’s Day is this weekend.
• Our absentee ballots for that superfluous California primary election.
• Terms and conditions for my wireless phone protection plan.
• A neighbor’s advertisement for Ocean Enterprises. I wonder how much of my own mail ends up in my neighbors’ hands. Good thing I’m going paperless.
• Brochure for this year’s LinuxWorld conference. Yet another advertisement that could have been sent via e-mail. I expect better of technical conferences.

Thursday

• Workforce and community development course catalog from Palomar College.

Friday

• Circulars for local chain stores (Target, Rite-Aid, etc.).
• Advertisement for Discount Tires.
• Our “voting guide” for California’s upcoming primary election. I don’t know what I’d do without people sending me mail to tell me how I should vote.
• Solicitation to alumni to pledge money for UCSD’s Jacobs School of Engineering. This was sent because I refused to pledge money to someone who cold-called me soliciting money.

Saturday

• Time magazine. I won’t be renewing my subscription after next month. It’s another magazine I no longer have time (ha ha) to read, and the articles all end up on the web site anyway.
• City news and recreation guide for the city of San Marcos. I’ll have to read through this to see if it’s something I want.
• Invitation to the Zoological Society of San Diego’s Member Appreciation Evening. I’ve been a member for a number of years, so I expect these things.
• Solicitation to become a member of the Birch Aquarium. Nice, but I’ll pass for now.

The first thing I’ve learned from this experiment is that it’s not as easy as I expected to distinguish the signal from the noise. Some pieces of mail—the credit card offers—are obviously junk. Some pieces of mail—the greeting cards—are obviously not junk. Others, such as the San Marcos recreation guide or the circulars for stores we actually shop at, are not so easy to classify. For the purposes of this experiment, I will classify them as junk, because they were unsolicited commercial mail. This, as some may recognize, is similar to the official definition of spam e-mail. That said, what was my signal to noise ratio?

We received 13 pieces of desired (or not so desired in the case of bills and ballots) mail and 15 pieces of junk mail. While these numbers may look close to equal, much of the junk mail was composed of circulars and brochures, which consist of much more paper than the typical desired piece of mail. Next week I may need to refine my measurement criteria by counting the number of unique advertisements in each circular.

I’d like to thank jaqque for pressuring me into doing this. I expect it to be a lot of fun. Really.

Well, now I’m paying over $4 per gallon on fuel for said car. It is time again to evaluate the Coaster. I would need a “2 zone” pass, which costs $126 per month. At $4 per gallon, that’s 31.5 gallons of gasoline. I burn approximately two gallons of gasoline per day on my commute, or 10 gallons per week, or approximately 40 gallons per month. The Coaster is becoming more attractive every day.

I live 7.8 miles from the Carlsbad Poinsettia Coaster station, a distance I could cycle to save even more fuel (and get some exercise). Regardless, even parking my car at the station, I would be reducing my commute by over 28 miles per day. I’d still need to drive for game nights and user group meetings, but the majority of my time would be spent on the train.

I don’t usually drive my morning commute in heavy traffic, opting to leave the house early to avoid it. However, it’s difficult to find a time of day to return home that will avoid traffic (except for really late after game night). While the train will likely add to the overall time of my commute, the lower mileage on my car and the benefit to my sanity will probably make up for it.

Qualcomm makes the deal even sweeter. The company subsidizes 25% of the Coaster pass, bringing the cost down to $94.50, and allows me to pay for it with pre-tax money from my paycheck. The only catch is, to receive a pass I need to apply for it by the first day of the month prior to the month the pass is for. For example, to have received a pass for June, I would have needed to apply by the first of May. So, while I could buy a full priced pass for either May or June (I don’t know if the passes are pro-rated), I couldn’t receive the subsidized pass until July.

I’m looking forward to trying out the Coaster. I may really enjoy it, being able to work or read on my commute. The time wouldn’t be wasted behind the wheel of my car.

For years, people have been talking about the paperless office, an idealized concept in which all documents and communications are of the electronic variety. I don’t know about anyone else, but looking around my office, it is far from paperless. Sure, a lot of once was done on paper is now done via electronic means, but I still have more paper around my office than I’d like.

Still, the situation at my office is far better than at home. Every day I receive reams of paper in my mailbox that I do not need. Magazines (I never read and have unsubscribed from), catalogs (from which I’ve never ordered—opting instead for their web sites), weekly circulars (for stores I never shop at), credit card offers (for cards I’d never get), and bills (which I suppose I need, sort of).

In an effort to rid myself of the piles of junk I either shred or recycle every week, and save a few trees, I did two things. First, I signed up for paperless billing from all of my utilities and paperless documents from my bank and credit union. The immediate benefit of this, besides not having my mailbox filled with paper is archival. Bank statements take up room in filing drawers and that room runs out quickly. Bills just get shredded, because I have no desire for them to take up what little room isn’t being taken by bank statements. By opting for electronic delivery, I can save as many bank statements and bills as I want—for years—and it takes less space on my hard drive than my photo collection.

Second, I signed up for GreenDimes, which advertises itself as a way to stop junk mail and save the environment. Initially, I was going to sign up for the free account and use their pointers to manage the junk mail myself. Then I noticed that the $20 fee for their premium service is a one-time fee, not a subscription. So I opted for this service, to free myself of the hassle of freeing myself from junk mail. I don’t know how effective this service will be, but I’ll report back in a couple of months on the relative success or failure of it.

One thing I found odd about GreenDimes was the $1 offer. There are three options for this nominal sum: receive it as a check in the mail; use it to plant a tree on my behalf; or receive a free trial issue of Plenty, the magazine of hip, green living. I can’t help but think this is a test. The irony of the first and third options was immediately apparent to me.

I still receive periodical publications from memberships. My bank, AAA, Costco, and the Zoological Society of San Diego. Most of the time, these magazines go unread. I save some (Zoonooz) and toss the rest into the recycle bin. Still, if possible, I’d like to receive these electronically as well. A PDF file is far more environmentally-friendly, and takes up less space, than a print magazine.

Last week, when Mrs. sirhc and I were visiting Oregon, we took advantage of the absence of a state sales tax and a sale at Costco to buy two Samsung u550 phones. They seemed like a good deal at the time, and we were assured of a very liberal return policy, so we went ahead and bought them.

We soon decided that we didn’t like our new phones very much. The features seemed limited, and I couldn’t get the volume up to a decent volume on either of my Bluetooth headsets. I also decided that I really wanted a PDA this time around, and set my sights on the new Palm Treo 755p. So back to Costco we went, down here in San Diego this time.

The return went smoothly, but the guy working the kiosk at Costco didn’t seem very interested in activating our old phones. Since the kiosk didn’t have the phones we wanted, we didn’t worry too much about this and went over to the Verizon store instead. That’s when things stopped going smoothly.

The kiosk guy didn’t reset our contracts, and there was nothing the customer service guy at the Verizon store could do about it. I had our old phones reactivated and called the original kiosk guy in Oregon. He said everything was fine and fed me a line of, what the real Verizon customer service guy told me was crap. Apparently, the kiosk guys do this all the time, to keep their commission even after a customer backs out of the contract within Verizon’s 30 day trial period. I was about to call Verizon corporate customer service myself and ready to drive back to Costco when the customer service guy said he’d make some calls and bring his manager into it.

In the end, the Verizon store guys got everything straightened out. We got our contracts reset, so we were able to get discounts on my Palm Treo 755p and Mrs. sirhc’s LG enV. So far we’re pretty happy with our new toys.

And that’s the last time I buy a phone from a kiosk.

Unintended Travel

As I mentioned on Monday, we had to modify our plans at the last minute. As my family juggled schedules and rearranged plans, stress levels rose until, finally, we agreed upon arrangements that worked for everyone and would hopefully unfold smoothly.

It was much too expensive to re-book our flight from Seattle-Tacoma International Airport to Portland, so we instead rented a car to make the two-and-a-half hour drive south to Wilsonville, Oregon. On the Hertz web site the previous morning, I had reserved a Camry. Partly because I wanted to test drive it, as I’m thinking of replacing my Avalon in a few years; partly because my other option was an Impala, and we didn’t like the last one we rented. As an added bonus, the only Camry left had a GPS unit, which I didn’t request, so I didn’t pay for it. This turned out to be more useful than I expected.

We arrived in Wilsonville shortly before my parents left to pick up my sister and her husband from the Portland airport (they were smart enough to fly Southwest, so re-booking the flight didn’t cost them an obscene amount of money), so we went ahead and checked into the Comfort Inn. We had some time to kill, and Oregon doesn’t have a state sales tax, so we went over to the local Costco to take advantage of a sale on Samsung u550 phones. This turned out to be a big mistake (more on that later).

When my parents returned with my sister and her husband, and they got settled into their own hotel, the six of us headed out for a bite to eat. Across from our hotel was a pub called Wanker’s Corner. It had a decent menu and a good selection of beer (we were, after all, only 20 minutes south of Portland). I had a steak covered in sautéed mushrooms and blue cheese, which makes my mouth water to remember it.

A Farewell for One Grandmother

My grandmother’s funeral was scheduled for Friday afternoon. In order to reduce some of the shock of the planned open-casket funeral, I took my sister to the mortuary in the morning to view the body. The best way to describe the visit would be that it was an odd experience. It was a bit like visiting Madame Tussauds: extremely realistic, but lacking that spark of life. This woman only vaguely resembled the grandmother I remember. Had I not been told who she was, I may not have recognized her at all.

I find the whole concept of open-casket funerals odd. The event is already a painful one for friends and family. The sight of their loved one’s lifeless body can’t be easy to take. I think I prefer an urn. However, I’ve only attended two funerals; the first was a Catholic mass for my (cremated) paternal grandfather.

The funeral service itself was nice. The pastor really didn’t know the family, as he was just the guy who performed services for everyone who passed through his mortuary, as it were. The eulogy was nice, if inaccurate in a few areas. My grandmother’s children—my mother and her two brothers—each said some words, as well as did one of my cousins. I was offered the opportunity, but didn’t take it. I had thought about it, but everything that came to mind was more about me than it was about my grandmother. I don’t think everyone needed to hear that; the service was about her, not me.

Following the service, the entire family joined my grandfather for dinner back at his retirement community. Since we had to get on the road to Snohomish immediately after dinner, I had gone ahead and changed out of my suit and back into my t-shirt and shorts, which I always wear when traveling. My uncle pointed out the community’s dress code, but since my shorts weren’t denim, I was okay. A cheese and fruit platter was laid out as an appetiser, the main course was salmon in a hollandaise sauce, and dessert was a delicious chocolate cake with a coconut raspberry sauce. Overall a good meal, but unfortunately the salmon would come back to haunt us.

While we had not intended to visit Oregon at all, circumstances combined for us to see most of my mom’s family (a couple of cousins couldn’t make it). A sad event to be sure, but without it I may not have seen these members of my family for several more years.

Sleepless in … Tacoma

About two hours into our three hour drive, Mrs. sirhc started feeling a bit “iffy.” We pulled over once, then a second time on the side of the freeway, as the salmon made its way back upstream, so to speak. After the second stop (a daring dart across two lanes of freeway traffic merging into the I-5), we chose to find a place to stop and wait it out.

We spent about 45 minutes at a Shell station just south of the Tacoma Dome. The temperature was only a few degrees above freezing and I’m sure the wind chill off the sound was well below that (recall that I was wearing shorts). The wind off the sound will cut right through you. It’s vicious.

When Mrs. sirhc was feeling better, we headed back to the freeway. It was an easy entrance, directly across from the gas station … had I been reading the road signs instead of listening to the GPS. The GPS guided us onto the wrong freeway. On the plus side, once it realized it had done this to us, it sent us through a rather dodgy neighborhood in its attempt to steer us back to the entrance we had missed in the first place.

Later, the GPS unit was nice enough to guide us onto the I-405 freeway … after we had passed the turnoff. That’s okay, though; I wanted to take the I-5 anyway.

A Very Happy Birthday for the Other Grandmother

On Saturday, we kept our scheduled appointment for my paternal grandmother’s celebration of her 80th birthday. My dad’s whole family was gathered together for the first time since my grandfather’s funeral, eight years ago. I played some video games with my cousins, and took a lot of pictures. For dinner, we had steaks, which I was volunteered to grill. Somehow I always end up with that job. I was happy enough to do it. I got to stand outside in the chill air in front of two Weber charcoal grills.

Finally, well into the evening, we started a game of poker. The delay is unusual for my family. In the past, the game would have started immediately, and continued all day and well into the night. These days Texas Hold’em is all the rage, even in my family. It presents a much different dynamic that not everyone has picked up. I was up at the end, which came much earlier than we had planned.

Snow!

My parents had left earlier in the evening to get back to their hotel in time to get a decent amount of sleep. Not long after they got on the road, I started receiving phone calls from them. Apparently, a snowstorm was passing through, for the first time in who knows how long. My parents were urging me to get on the road before it got worse. I took some flak from my Denver-based cousins, but my grandmother needed to get home, and I was the only person both sober enough and competent enough to make the drive. So we left.

Just as no one in Southern California can drive when it rains, it seems no one in Wa(r)shington can drive when it snows. I of all people, the kid who grew up in Hawai’i and Southern California, managed to handle the conditions just fine. Better, in fact, than the majority of people we encountered on the road.

In the end, the drive was more annoying that it was stressful. We saw two cars in ditches along the side of the road and, at one point, got stuck behind someone driving under 25 MPH and continuously braking … uphill. Anyone who has driven in the snow knows this is a particularly dangerous practice.

At my parents’ urging, we opted to take the “river road” instead of Highway 2. My grandmother protested this move until my mother finally communicated to her that this was the route she takes home from bingo. Apparently, the road is actually the Old Snohomish-Monroe Highway, while the “river road” is another route entirely. The old highway ended up being a pleasant drive. Few people go that way, and the river’s relative warmth kept the road clear of snow. Yes, my mom referred to it as the “river road” because it follows the path of the river.

At one point, we pulled into the cover of a gas station to clear the car’s windshield and air intake of snow and ice. Fortunately, this time I was wearing pants. My hand still froze as I cleared the ice. Apparently, I didn’t think to pack gloves on a trip to a location that hasn’t seen snow in ages, particularly in March.

Signs

Our flight home was delayed by an hour, so Mrs. sirhc and I had plenty time to grab lunch and spend some time relaxing at the Seattle-Tacoma airport. After evaluating our myriad options of gourmet choices, we somehow passed up Wolfgang Puck’s pizza in favor of Wendy’s hamburgers (actually, I had a chicken sandwich). As Mrs. sirhc ventured off in search of a table, I waited for our order outside the cashier area, which was sort of enclosed with windows on either side.

To understand the rest of this story, I need to first explain something. Ever since I found out Mrs. sirhc was carrying a little sirhc or sirhcette, I’ve become much more aware of two things: pregnant women, and children. What once was something I never took notice of, I see everywhere now.

Through the window on the left side of the restaurant, just inside the cashier area, was a little red-haired girl. She couldn’t have been more than four or five years old and, for some reason, I had caught her fancy. Every time I looked in her direction, she would catch my eye, smile and wave. After noticing this, I played a bit of peek-a-boo with her while I waited for our order. When our food was ready, I passed her, said hello and went on my way. Shortly after, as we sat and ate our food, the girl passed by with her family, found me across the food court, caught my eye again, smiled and waved.

I think this will be my last non-business flight for a long, long time. Not when it costs most of a paycheck just to fly somewhere for a weekend.

Update (26 Mar 2008, 09:30): I just booked a rental car and a hotel room in Oregon. Total cost, $208.32. $2.68 less than one ticket reschedule from American Airlines.

My grandmother—my mom’s mother—passed away early this morning.

She had been in declining health and suffering from Alzheimer’s disease for several years. We visited her and my grandfather over the Christmas holiday in 2005. This woman, of whom I have so many fond childhood memories, was a complete stranger to me, as I was to her. After that visit, I had resigned myself to knowing that I would never see her again. While I knew this day could not be far off, one can never truly prepare for it. Already I can feel the sadness just under the surface, welling up periodically, threatening to overtake me.

I feel worse when I think about my own mother. This will be especially hard her. Not only from of the loss, but because she was scheduled to spend time with her mother this week.

Rest in peace, Grandma. I’m sorry you’ll never get the chance to meet your great grandchild. We’ll miss you terribly.

http://babyg-thebeginnings.blogspot.com/

So Mrs. sirhc is pregnant. Eight weeks today. In seven months, there will be a little sirhc or sirhcette in the house.

We broke the news to our parents today, so it’s finally safe to write about it. The urge to post about it here has been difficult to suppress, but my family does occasionally pay a visit. Today happens to be my mother’s birthday. So, after making sure my dad had the camera ready, we let her unwrap her gift—a tiny bib that reads, “I Love Grandma.” The expression on her face was priceless.

I figure that, by now, my entire family—and countless others I’m sure—have heard the news.

Jumping right into the talk, Allison started off with the general idea of Parrot. It is a virtual machine (VM) meant to be a target for multiple (or all, really) dynamic languages. Think Perl, Python, Ruby, TCL, Lua, etc. Much like Perl itself, the overarching idea is to provide tools to make the act of writing compilers not only possible, but relatively easy.

When Parrot started, some seven years ago, people laughed when they said it would be a VM for dynamic languages. The JVM and .NET VM were all the rage at the time, and they are targeted at static languages. Today, those same people are touting how their VMs contain support for dynamic languages.

The rest of the session was a general overview of Parrot’s features and functionality. In brief,

• Similar to .NET, Parrot would allow any language to use libraries written in any other;
• Parrot is a register-based virtual machine, instead of the traditional stack-based design;
• Continuation objects are used to pass call state, instead of the usual method of pushing onto a call stack;
• PASM, the Parrot virtual machine’s assembly language;
• PIR, a layer on top of PASM, intended to be more programmer-friendly;
• NQP, an even higher layer, implementing many of the features from high level dynamic languages (Not Quite P(erl|ython|HP|ruby));

Following this simple, but educational, overview, Allison gave some examples for how to use the Parrot tools to write a Python compiler. This is something the Parrot team has, of course, already done. It’s called Pynie (a bit of an inside joke&emdash;see Ponie and Punie). It’s not really that much code to implement, either. Certainly not compared to what I wrote to parse “Turing” in college using Lex, Yacc, and lots of C code. It just goes to show how powerful the Parrot tools are.

I had read about much of this before, but unused information tends to slip away when not used. It was nice to have a refresher course for the overall architecture of the system. It’s all very much clearer now. I’m looking forward to finding a use for Parrot.

[tags]SCALE, Parrot[/tags]

I won a couple of books at the reception and raffle last night. It felt just like a KPLUG meeting, and not just because half of the membership was in attendance and several of us won prizes. I actually won three books, but I gave one away. Once you’re name has been called, they don’t give you very much time to pick out your books, and the selection was uninteresting.

After the reception, Brian took us to the Third Street Promenade in Santa Monica last night. It’s a nice area to walk around and have dinner. After dinner at FatBurger, we came back to the hotel for drinks; which was good, since I was driving.

I’ll likely spend most of my day in the Perl Mongers booth again. There is a talk on Parrot being given by Allison Randal, but I expect many of my fellow booth-sitters will also want to attend. We may have to draw straws.

[tags]SCALE[/tags]

I’ve just made a circuit of the expo floor, and it was pretty cool. I visited all the booths required to enter tonight’s raffle. And, just for fun, I visited a few more. It’s a lot of fun to have so many members of my local Linux User Group here, as I keep running into them in various parts of the expo hall.

There’s a full flight simulator running Linux in the row behind our booth. Unfortunately, it was crashed when I walked by, but I’m hoping to check it out later. Other than that, it’s the usual suspects: Red Hat, Novell, IBM, Sun, etc. In fact, the Google booth is a mere two stalls to my left. I firmly believe we’re taking advantage of their coolness factor to draw people to our corner. Not that I have any idea what Google’s demonstrating in their booth.

[tags]SCALE[/tags]

My day hasn’t been off to a great start. After a bout of insomnia and a near collision on the 405, I arrived at the Los Angeles Airpot Westin to find the parking garage full. There was some parking that we were told was off limits, despite the lack of barrier and hidden signs. I am, instead, parked in a supposedly free garage down the block. Hopefully my car will still be there this afternoon.

As it seems the network connection for the keynote has failed, I’m going to wrap this up and see if I can find any of my fellow KPLUGgers.

On the plus side, things can really only go up from here, right?

False alarm. Seems the keynote is back on. More to come later.

[tags]SCALE[/tags]

Lastly, make absolutely sure you request to reschedule your phone interview half an hour prior to its commencement. This one works especially well when I’ve cut my sleep short and arrived at work early just for your interview.

I had been watching the news broadcasts last night, but gave up and went to bed around midnight. At 6:00am, I awoke to a phone call from my mom. A smaller fire (now contained) had started near us, and she wanted us to pack up and head down to her house in La Jolla, which will remain safe. As of this afternoon, I can still ping the router in my house. As more evacuations are ordered in the communities surrounding our house—the latest appears to be for our community, but it’s unclear—I can only hope for the best.

As I said, myself, my wife, and our three cats are safe and sound at my parents’ house.

[tags]san diego, witch fire[/tags]

Today was also a very good day. I learned a lot, and had a great time doing so. While I’m already familiar with most of Perl’s best practices and the reasons for using them, there are always many things to be learned any time Damian speaks. For example, I’ve always been one to use a single method as both accessor and mutator. However, now I’ve seen a good argument to use separate methods. Granted, I could have just read the book, but who has time for that?

One thing I will recommend: try to avoid flipping the bird to your instructor, even accidentally, particularly if you’re sitting in the front row and he’s standing only six feet directly in front of you. Shortly after this incident, I had a conversation with a friend in New Zealand. He gave me an explanation of the gesture and congratulated me for executing it in such a public forum (and getting a few laughs).

Even after my faux pas, I had the distinct honour to do a bit of hacking with Damian after class. My coworker voiced a concern I’ve also had in the past: inside-out modules, in this case Contextual::Return, do not work with Data::Dumper. So what did they do? They immediately started looking for a way to make it work. Initially, I merely stood back and watched; however, I’m proud to say I did have some input into the final implementation. Essentially, we came up with the following method to make it work.


{ local $Data::Dumper::Freezer = 'Contextual::Return::FREEZE';
  Dumper $return_value;
}


It’s perhaps not the most convenient way of doing the job, but it’s not bad for something that for most people is a debugging tool.

After a short break for some rolled tacos at Nico’s, it was back to the auditorium for Damian’s presentation to the Perl Mongers. As always, he had us rolling with laughter while at the same time learning quite a lot. The primary focus of the talk was the social and technical lessons learned by the core Perl 6 development team over the last seven years of the project. The lessons can be applied to any project—or in fact any group of people—be it Open Source or within a company. While useful, I was most excited by what Damian shared of Perl 6 itself. The design is amazingly clean and elegant, and I’m really looking forward to using it in my own projects. One thing that really has me excited is junctions. These look like an awesome way to develop parallel code cleanly and intuitively (at least for me).

I have one more day of class tomorrow, one I’m really looking forward to. Damian will explain to us exactly how it is he can be so productive, even while traveling. I expect to be overwhelmed with information and it will likely take me all weekend just to absorb it, and even longer to put what I learn to use. Next year I sure hope we have him back to teach us all about Vim.

I attended the first of three courses taught by Damian Conway today, Advanced Parsing with Parse::RecDescent. This was, effectively, the Parse::RecDescent tutorial as presented live by Damian. I’ve read the tutorial, and it’s quite good, but it’s hard to beat instruction from the man himself. Not having used the module on too many occasions, the course served to clarify a few concepts of the grammar used by Parse::RecDescent.

Now I see problems in a new light—for better or worse. This evening, I joined my boss to debug a problem we’ve been seeing in our compute cluster. I joked that I could just whip up a grammar to track down the problem for us. I must resist my usual urge to apply my new, shiny tool to all problems. I mean, it’s bad enough I use the Perl hammer for everything, right?

Today’s course left me with nostalgia for the compilers course I took in college. As my partner for that long ago class reminded me, it was filled with “late nights and Mountain Dew.” Ah, good times.

This added layer of security is a good thing, and I’m glad a company like PayPal is using its popularity and market presence to encourage adoption of two-factor authentication. It’s far superior to the wish-it-was two-factor authentication schemes being implemented by some banks, including my own.

When my bank started implementing their own silly form of two-factor authentication, they did the same thing other banks have been doing. Asking me on what street was my childhood home leaves me wondering if I spelled it Street, St., or left it off altogether. When presented with questions about my favorite color, food, or day of the week, I give up altogether and write down my (usually randomly generated) answers. This is not what I would call an added layer of security. In fact, when asked over the phone by one of my bank’s customer service representatives if I would like to provide answers to some of these inane questions for identification purposes, I declined. I was warned I would instead be challenged for information about such mundane things as my Social Security number and various account information I have with the bank. I told the representative that I was fine with that. After all, I’m much more likely to guard the details of my financial accounts than I am my pets’ names, where I grew up, or the fact that I enjoy fish tacos at Rubio’s (this week).

[tags]paypal, security[/tags]

So we arrive at the vet’s office only to find out that it’s no longer the vet’s office. They have moved, and left a sign on the door with the new location. Of course, the address on the front page of the web site has not been updated.

All Cats Hospital
7040 Avenida Encinas Ste 109
Calsbad [sic], CA 92011

We called the (new) office to let them know we would be late and why. We were told we would have to reschedule.

Sure, I’ll reschedule. For an appointment with a different vet. I refuse to do business or trust someone who can’t even keep something as simple as a web site up to date. Not to mention spell the name of their city correctly.

Many would consider me a Luddite, preferring Mutt as my MUA. of choice. I can imagine the cries of people who use so-called modern mail readers: fancy text formatting! embedded images! annoying layouts! hidden viruses! phishing scams!

What happened to the power and effectiveness of the written word? I suppose many aren’t capable of scribing a well-formed sentence, so they compensate with fonts, colors, and cryptic abbreviations. Still others are attracted to the shininess of the formatting. They can send mail that looks like a web page! Even when all they wanted to do was ask a short question!

This is progress?

Normally, I’m content with killfiling any mail that arrives with a content type of text/html. Unfortunately, there are some people I simply must communicate with for whatever reason (usually it involves money in one way or another). One of the fastest ways to get on my bad side is to send me mail that requires extra effort for me to read. This rant is a result of one of these messages.

I drafted a message of moderate length to discuss some points I thought important. Normally, I would expect any responses inline or, at worst, top posted. No, the response I received was even worse than what I see from users of Eudora’s unintelligible reply style. The responses were added directly to the paragraphs I had written, but styled bold and red for “readability.”

Hello, this is my opinion on the matter. I see, but have you considered this other thing?

As can be expected, this style doesn’t lend itself well to reading in plain text. Of course, I don’t think this style lends itself to any kind of comprehension.

I responded to this message, demonstrating how difficult it was for me to read without jumping through hoops, and expressing my annoyance at being forced to jump through said hoops. I tried to be kind, blaming the bad-habit-inducing tools (Outlook) rather than the writer. So this fellow tries again.

With an attached PDF file.

Seriously? Was he so enthralled by the font styling that he felt compelled to force upon me an attached document in order to render correctly? Maybe e-mail really is dead. Apparently a well-written, plain text message is too much to ask for.

[tags]annoyances, e-mail, people[/tags]

I have a few ideas for the future of the web site. Some of these include a wiki, a blog, a book review section, anything really. Not everything will be worth pursuing. We can have a wiki on a main Perl site; we can set up individual blogs on use Perl (or Blogger or LiveJournal or whatever). However, I think it would be nice to have a web site we can call our own.

I’m open to ideas, and I try to be receptive to comments and suggestions, either on our mailing list or sent directly to me.

[tags]perl mongers, sandiego.pm[/tags]

Since we had the auditorium available to us, one of our members was nice enough to say a few words about his business and how Perl has helped him to succeed. Much of the evening was devoted to chatting about whatever Perl-related thoughts came to mind. I floated the idea of hosting a booth at FOSSCON, but that’s still too far out to really talk seriously about it.

I’m extremely pleased with how well the venue worked out. We may not have the meeting there every month, but it’s nice to have it available so we can start adding technical meetings to our calendar.

[tags]perl, perl mongers, san diego, sandiego.pm[/tags]

Looks like Chicago.pm has thrown their hat into the ring as well.

Update: I guess the LA.pm bid never gained any traction.

[tags]oscon, oscon07, yapc, perl mongers, los angeles[/tags]

This is that post. Don’t mind the smell, I’m sure it’ll clear up soon.

I happened to be clicking through some of WordPress’s myriad options tonight, when I found it can import posts and comments from Blogger. Neat! I still have to go through and manually add tags to each entry, but that task is much easier.

I wasn’t overly impressed with the quality of the tutorials or the sessions this year. Even with 15 parallel tracks, I sometimes found it difficult to find a session that held more interest for me than the hallway track. Other times, the sheer number of tracks left me flipping coins to determine which session to attend. I hope that next year the organizers of OSCON (though I don’t expect Allison reads my blog) either reduce the number of parallel tracks, or do a better job scheduling those tracks. I realize it must be a difficult job, but if everyone attending could select the sessions that interest them beforehand, I think it could work.

Last year, I jokingly referred to OSCON as DamianCon(way), after the seemingly endless number of tutorials, sessions, and keynotes he had presented. Unfortunately, this year he wasn’t even in attendance. A lot of people were disappointed to find that Randal Schwartz wasn’t in attendance either. With the absence of two of OSCON’s major celebrities and the news of Nat Torkington stepping down as OSCON program chair, a friend pondered if this meant OSCON had jumped the shark. This quickly led that same friend to ponder if the phrase, “jumped the shark,” had itself jumped the shark.

Still, OSCON isn’t wholly about the tutorials or the sessions. It’s about the people. It’s about seeing friends from around the world (Brad, Dan, Dylan), and meeting new ones (Alasdair, Josh, Kevin), and spending a week together. A week of learning and socializing. That’s the real reason I come to OSCON. After my yearly dose of geek, I return to work refreshed, with more creativity and productivity than when I left. So OSCON is still worth attending, I think, even if it wasn’t as good as we always seem to remember (and I’m sure we’ll all repeat the sentiment next year).

I can’t wait to come back next year.

They are intelligent and creative people, but I don’t have a whole lot to say about what they’re saying. However, I do appreciate the irony of my attendance, given my day job.

This talk is not about programming, but about rhetoric. In particular, the rhetoric used in business today. And how no one understands it.

So many words used in business today have other meanings. Meanings that have nothing to do with how they’re being used in business rhetoric. So what do we do? We put words together and pretend they mean something new. And, since we’re not German, we turn them into acronyms. Acronyms that may themselves mean something else. Confusing, isn’t it?

Here’s an idea. Go back in time to find words that mean something else, but that no one today remembers (at least, no more than a handful of people on the planet). Then redefine that word to mean whatever you want. This works particularly well if Google returns very few hits for the word in question. Of course, like anything, it can backfire.

After talking about the fallacy of rhetoric in modern business language, the remainder of the session was dedicated to replacing our modern business language with words from antiquity, almost all of which have meanings very close to what we want. I’m not surprised that most of the words come from the literary (as in books) domain. We are, after all, writing and publishing software.

Shamefully, no one recorded this session. I couldn’t even attempt to do it justice here.

This session has given me a desire to subscribe to the Oxford English Dictionary.

Who says the English language doesn’t have a proper word for what we mean by free software?

Liberal Software.

Duh.

Stupid politicians. Thanks guys.

They started out with the top 10 ways to sabotage your project with Subversion. It’s Friday, and there’s not that much to say about each of the slides, so I’ll merely enumerate the worst practices, without commentary, for now. Hopefully the slides will be posted later.

10. Argue about Version Control Systems

9. Do a Brute-Force Transition

8. Backups? What Backups?

7. Loads of Locales

6. Rule with an IRON FIST

5. Hide the Version Control

4. Use Complex Branching Schemes

3. Put Everything in the Repository

2. Use a Network Drive

(Oops, we do that…)

1. Really Clever Hook Scripts!

0. Edit the Repository Database

Obviously, this session was really a list of best practices presented in a humorous way, by pointing out the extreme case of not actually following those best practices.

I noticed the MacBook Pro Ben and Brian are using to drive their session has a bumper sticker on it: “My other computer is a data center.” I like it. It’s exactly what I’ve been doing to my computing.

It was nice that Ben and Brian left ample time for questions and answers. The audience appreciated the time to ask questions about how to apply Subversion best practices to their own repositories. Or just to bitch about some pain points. Fun stuff.

Anyway, on to the keynotes.

First up is Philip Rosedale, of giant, flying penis fame. Um. I mean, Second Life fame. He’s here to talk about Open Source Second Life. He had an interesting comment comparing Second Life to the X Prize. We, as humans, have two major goals. First, we could delve into inner space, the virtual world that is Second Life. Second, we could venture into outer space, leaving the planet behind altogether. But really what he wants to talk about is how Open Source can benefit Second Life and, presumably, how Second Life can benefit Open Source. Philip sees Second Life as being good for humanity and wants to see it grow in the way that only the Open Source community can manage.

I’m not entirely sure how Second Life can be good for humanity (it’s just graphical IRC, isn’t it?) and I’ve never even considered using Second Life. On the surface, it looks like it could be fun. But it’s not a game. At least the MMORPGs had stuff to do. Second Life is just real people in an imaginary world, doing all the things that real people do to annoy me. We’ll see.

Next up is Jimmy Wales, of Wikia fame. He started off with a quote. “Imagine a world in which every single person on the planet is given free access to the sum of all human knowledge.” That is free, as in speech, of course. Wikipedia was the encyclopedia. Now, Wikia wants to be the entire library.

Of course, this being OSCON, Jimmy was sure to point out that all of this free information is thanks to Open Source. Today, there are so many inexpensive options out there to publish web sites, which I certainly don’t need to enumerate to my audience. Wikipedia, and now Wikia, take full advantage of this Open Source software.

So why not extend the idea of openness to search? Today, all of our searches are locked up in companies. From so-called good companies (Google) to so-called bad companies (Microsoft). But they are still companies. Search should be open and democratic, too. So that’s what Wikia is doing, building an open search.

There are four keys to open search: transparency, collaboration, quality, and privacy.

Now for the announcement. Wikia has acquired Grub (no, not the bootloader), a distributed web crawling program. Interesting. Another distributed software application. I like the idea behind these, using all the potential of all those idle processors, but I don’t much like paying the electric bill.

Our third keynote of the day is being delivered by Simon Wardley, who points out that he is from Kent, England. He’s here to talk about one of his passions—second only to ducks—commoditisation. There is an ever-driving force in IT to push products and services to being commodities. Companies try hard to push products and services away from being commodities, using patents and DRM. However, Open Source is a major driving force for turning products and services into commodities.

This is a concept I really like. Why should we spend all of our time reinventing wheels? If something has already been done right, why can’t we all take advantage of it? In fact, it was all the rage when I attended the Platform Grid Conference last year. However, aside from the academics speaking at that conference, everyone there represented a company that wanted to capture and jail your data.

There are three main levels of commoditization, software, framework, and hardware as a service ({S,F,H}aaS). By open sourcing each of these, we create a stack capable of deploying new and interesting products, without spending so much time reinventing those bloody wheels.

Our next speaker was none other than Nathan Torkington, our program chair. He will be giving us three keynotes in fifteen minutes, just to prove that fifteen minutes is more than enough time for a keynote.

Short keynote number one: Dr. Nat’s therapy session. It was very funny, but very difficult to blog. In short, he took a page out of Dr. Phil’s book and psychoanalyzed all the software we use on a daily basis. It’s hard to describe, but he nailed each of the projects’ idiosyncrasies quite well.

Short keynote number two: Open Source has won. Nat’s running low on time, so he’s talking really, really fast in his kiwi accent. Fortunately, isn’t as strong as other kiwi accents I’ve heard, but as he speaks faster, it gets stronger. So Open Source may have won (is winning?) the battle against proprietary software companies, but we spend a lot of time fighting amongst each other.

Short keynote number three: People are stupid (don’t even get me started). Apparently, all the smart people now work for Google, leaving the rest of the world with very few smart people. The message here, it’s easy to be mean, but hard to be nice. Remember, we’re all people. Be nice to each other.

Our final keynote is from James Larsson, someone who, as Nat tells us, embodies the hacker spirit. He’s here to tell us how to “Pimp My Garbage.” I’m actually a little scared to find out what that means.

Okay, this is a great talk. He’s showing off ways he has turned old, boring games into something a bit more exciting. Not only games, but old, discarded electronics. It’s all about taking old things and thinking of new, interesting things to do with them. It is the essence of hacking. I’m tempted to subscribe to Make magazine now.

Interestingly (or perhaps not), the higher the level of sophistication of a product, the less potential it has for hackability. So the only thing you can really do with the more sophisticated things is to destroy them in interesting ways.

I don’t know how to even begin describing James’s keynote. Fortunately, it’s being recorded for later posting on YouTube. I’ll post the link when it’s available.

And that’s the end of the keynotes. Time for the break.

Anyway, go take the survey.

http://perlsurvey.org/

When Larry hooked up his computer to the projector, he had an IRC window open to #parrot on irc.perl.org. Yes, of course I did it. I jumped right into the channel and wrote, “hi mom.” I got a good laugh from those in the room, but I’ll probably never be welcome in that channel again.

Larry thinks it’s a bad idea to get rid of the term scripting. Perl already owns the brand when it comes to scripting. We have about the same chance of changing the branding of hacker.

“Programming is hard, let’s go scripting!”

Scripting isn’t so bad. It’s actually kind of easy; just look at all the script kiddies out there. But we can use Perl to turn all those script kiddies into real programmers. After all, Larry claims to have come to Perl in the same way.

So what’s the difference between scripting and programmers? Scripting is like profanity, you know it when you see it.

This year’s State of the Onion is about scripting, past, present, and future.

The past, essentially, is a brief history of Larry and his experience with scripting at different times of his life. More importantly, it’s about what all of these languages ar, how they and his experiences with them influenced what Perl was, is, and will be.

The present is an overview of the different ways languages can be designed. Binding, dispatch, typology, structure, and others are all different forks in the road of language design. Each fork developed for different reasons, whether it be efficiency of code or abstraction of language concepts. Follow all of these forks like some kind of Choose Your Own Adventure book, and different languages emerge. The lessons of each of these languages can be used as new ones are developed.

So I guess what Larry is trying to say is that Perl 6 looked at what every other language (including Perl 5) did right and what they did wrong, then went ahead and did everything right.

In fact, Perl 6 has taken Yogi Berra’s advice and took all of the forks. Sure, it seems confusing, but think of the power.

Okay, so what’s the future?

Perl 6.

Duh.

Seventeen talks this year, in a span that only allows sixteen. No break for us.

Vani Raja talked about YUI CSS. This appears to be some kind of Yahoo style sheet stuff for HTML. I’m not sure how this differs from any other style sheet out there, but she seems very proud of it. I’m guessing it’s just a set of pre-written styles that page designers can mix and match in their web sites. Oh, and apparently Nate is her hero.

Okay, now it’s time for “How Long Is Five Minutes?” by Schwern. He seems very concerned about how long five minutes is and how often he ruins his tea. Why is this important? Well, if you don’t know how long five minutes is and how much you can do in those five minutes, how can you know how much you can do in a half hour, an hour, a day, a week?

Schwern managed to get himself two slots of lightning talks. This second one is a very rapid combination of three talks. First up is a plug of the new Perl 5 wiki. He wants this to be the encyclopedia of Perl 5. As an aside, someone in my Perl Mongers group who already wants to have a wiki-thon at our next meeting. Next, we got to stand up a lot as he asked questions about our demographics. Apparently we in this room are not representative of the US at large. In any case, a survey of this information has been put up at perlsurvey.org. Finally, we’re supposed to blame Schwern. Larry has gone off to Perl 6, so Schwern is taking the responsibility of being the one who people can go to if they want to do something in Perl 5. In other words, we get to blame him for giving people the go ahead. (That was amazingly hard to type up in the five minutes Schwern was allotted.)

Ask Bjorn Hansen wanted to present qpsmtpd, which is something he threw together in Perl to implement features he wanted in qmail. In fact, Perl hackers can easily write plug-ins for the system, which is a pretty cool idea. It looks pretty nifty, I may take a look at it, if only to toy with it as a game.

Andy Lester talked about ack, an awesome way to grep trees of source code. He gave this talk last year, and I’ve been enamored of it every since. It even made it onto the Perl Advent calendar last year. He’s also set up Perl 101 (dot org), to help n00bs avoid asking n00b questions on IRC or on mailing lists. He needs help making it awesome. His third topic is Google Code. Use it instead of SourceForge, because it is awesome. Period.

Andy got a second slot, after being harassed by the audience on IRC and iChat, he jumped into his Perl-is-a-programming-language-not-a-scripting-language rant. A scripting language implies that it is less capable. Say program, not script! Dammit. Andy is an angry, angry man.

Rebecca, standing up in front of Programmers Anonymous, talked about the similarities between Open Source projects and non-profit organizations that use volunteer labor. When someone shows up and wants to help out an Open Source project, why not have a list of small things to be done that anyone can sink their teeth into.

Eric Wilhelm, who we may know from the Internet, talked about Test::Harness 3.0, which he’s come to recently as a way of parallelizing test code. TAP has evolved. In comes TAP::Parser (which will be used in Test::Harness 3.0… I think… I found that part hard to follow). This is apparently a five minute version of the talk Ovid will be giving at YAPC::EU. He’d like us to help improve the documentation and tests for TAP::Parser. Convenient link: testanything.org.

Eric continued with a second talk. Well, he promptly ducked under the table as he mentioned Module::Build. CPAN is great, but you need to upgrade it before installing. Then there’s a huge upgrade install dance. But soon (real soon now), CPAN will go back to being a one-liner and will do everything right automagically.

Julian introduced MoveMyData.org, which isn’t coded yet. However, it’s a great idea. So many different social networking sites exist (Blogger, Flickr, etc.), and they don’t interoperate at all. This is the solution. A way of moving data between social networks and making sure it’s backed up and always under your own control, not under their control. Very cool, and something I’ve always thought should be done. It’s one of the reasons I maintain my own blogging software, in fact.

Tim Bunce gave a quick talk about DBI, as he usually does. This time it’s about DBI 2 for Perl 6. The JDBC API is a great example of what he wants to do, so he’s going to steal (that is, borrow, now that Java is Open Source) what they’ve done. He continued to give some examples of how it should work and how it would look, but then he got gonged. Good stuff, though.

Second talk by Tim, DashProfiler and lightweight code instrumentation. It seems he does a lot of web service work these days, so he spends a lot of time writing code to help him make this faster. This is an instance of Tim writing code to find out what needs to be made faster. I like this. It’s very magical (read: Perlish). Just use it and it does what it does.

Tim, take three. He condensed yesterday’s 45 minute talk about Gofer into five minutes. I attended that session, so I mostly zoned out during the lightning talk. It’s another way of optimizing the infrastructure behind web services.

Michael Potter (who introduced himself at the end) wanted to talk about Open Sourcing Message Definitions, that is to say he wants a better way of getting data exchange formats into the Open Source or standard or something. I don’t know. It was short, sweet, and to some point I didn’t get.

John Rockway stood up to teach us how to create a blog using Catalyst in 5 minutes. Of course, he used slides, instead of typing it out himself. So mere mortals probably couldn’t create a blog in only 5 minutes. I’m not entirely sure Catalyst has ever been used to create anything other than a blog. That’s my biggest problem with most web frameworks. They look like they’re only useful for the fun stuff, and it’s non-obvious how to use them for other kinds of sites. That’s a bit harsh, but there are too many frameworks for me to play with all of them to see if I can use it. Oh, and I think some of the developers of Catalyst (which was a fork of Maypole) forked it off into something else again.

John continued to plug Angerwhale, an actual blog application he wrote in Catalyst. I really didn’t pay attention. I’m not sure I like Catalyst, and I’m quite sure I don’t need to fill my head with yet another blog application. Although, it is a blog application written in Perl, so I may eat my own dog food and try it out.

Someone who didn’t identify themselves stood up to talk about SVN::Notify::Mirror. No idea what he said, as I wasn’t listening.

Last, and most certainly not least, Pudge got up to perform Perl, in a Nutshell. Of course, everyone has probably already seen this on YouTube already (and if you haven’t, why not?!), but it was awesome to see live.

Domain specific languages (DSLs) are languages designed for specific programming tasks. A couple of well-known examples of DSLs are SQL and regular expressions. However, today, Jesse is talking to us about “Englishy” DSLs, which he’s been very interested in lately. Additionally, these are DSLs that are internal to Perl. Instead of parsing a DSL and executing it, they are instead implemented by playing with Perl’s syntax and taking advantage of Perl’s parser (and having all of Perl’s features available in the DSL).

The two main goals when implementing a DSL in Perl are,

1. Does it feel good?
2. Can we actually do it?

The first big DSL is Jifty::DBI, an object-relational mapper for Jifty. For the folks at Best Practical, it was a fun learning process in tweaking Perl to look the way they wanted it to while still declaring the database schema in an intuitive, pretty way.

The Template::Declare module is flat-out awesome. I’ve seen it before, and I’ve never taken the time to play with it. How stupid have I been? Coding HTML templates in Perl is cool, and something I would happily do (I don’t really like writing HTML).

As if that weren’t enough, in comes Jifty::Dispatcher. Modelled after Mason’s (auto|d)handler files, it will manipulate web application requests and take care of dispatching processes. I really like the DSL used here. It’s very declarative, removing the infrastructure entirely, which is something I’m very interested in doing in my code right now. I must be getting old; I’m more interested in telling the computer what to do, rather than how to do it, these days.

Testing web sites is ugly, and it sucks. That’s what Test::WWW::Declare is for. It’s a beautiful module. Sessions, flows, declarative statements to define the web flow. So very awesome.

I can tell that the Best Practical folks have seen Damian Conway’s Sufficiently Advanced Technologies talk. The moral of that story is, write what you want to see, and only then figure out how to make it work in Perl.

I’m sold. As soon as I get home, I’m going to work on porting my start-up company’s web site with Jifty. Jifty is, well, absolutely nifty.

At the end, Jesse showed us his own domain specific language to define his slides. It’s awesome. I want it for my own talks.

Apparently, this the people track is very popular with everyone. This session, People Hacks, is standing room only. Unfortunately, Adam Keys’ slides weren’t able to display on the screen. I think his talk stood on its own. In fact, I wish more talks lacked slides. For most people, they’re a crutch.

People Hacks is about advocacy, moving minds, and organizing teams. It’s a fact of life that no man is an island. We have to work with people, and they won’t always be our friends. Sometimes we want to hit them. Sometimes we talk past them. But we do need to work with them. And we can’t always hit them.

Most of us program because we like logic. We like dealing with machines that are predictable and rational. But we have to deal with people. People who are not always predictable and not always rational.

“There is no man page for humans.”

Truer words were never spoken.

People who are in a good mood are easy to work with. People who are sad or in a down state are difficult to work with (think emo kids—the new blonde jokes!). Get someone to smile. Humor is infectuous. Once people are laughing along with you, they’re easy to bring over to your side. Conversely, negative feelings spread like wildfire. Avoid negativity.

“The ABBA Method.” ABBA is like negativity. A little goes a really long way. When down, go listen to ABBA. How… odd.

Everyone loves a critic (Fox News?), but no one really enjoys criticism. It never goes over well. People take it poorly, they go on the defensive. When people are criticized, they withdraw from the conversation, and no one can move forward. Throw a compliment in. “Kiss their ass before handing it to them.”

Open Source has a love/hate relationship with jerks. We don’t tolerate them at all when they troll forums. However, if they’re a strong personality on an Open Source project, we’ll put up with them. A lot.

Sometimes you’re the jerk. We can all be jerks at times. If you can’t avoid it, at least recognize it and apologize for it.

After a while, the talk turned into a list of patterns of behavior found in people with ways to disarm them. The slides would have helped here, as it’s getting a bit more difficult to follow along.

He highly recommends reading How to Win Friends and Influence People.

And now it’s time for lunch, and I’m hungry, so I’m done.

Why build applications for the desktop? Speed. Network latency over long distances pushes the limits of people’s patience. Computers are getting so powerful, why not use those resources?

Why use Perl? Well, because it’s Perl.

Good documentation for wxPerl is difficult to find. Apparently someone needs to create a US mirror of the wiki. However, the C++ documentation is quite good.

Eric has created a few helper modules (most of which are on the CPAN) to make life for wxPerl developers a bit easier. He’d like to move more in the direction of Smalltalk, with more interaction and cleanliness between the code and the GUI. It’s still in the works.

One thing I really like is his phrase, “needs more Perlin’.” This means that something needs to be more like Perl. That is to say, it needs to keep easy things easy and make hard things possible… with a slick syntax.

Ben Fry started off the keynotes with a talk about the Processing Development Environment, which looks very cool. It’s similar in concept to Logo—which leaves a wonderful aftertaste of nostalgia for me—an entire development environment to do visualization, including a domain specific language to allow the programmer to focus on writing what they mean to do, not how to do it. Coincidentally, I’ll be attending a session on domain specific languages later today. He even wrote code on the fly in the environment, in front of the audience which is a very brave thing to do. But, it was an awesome demonstration of how easy yet powerful the environment is. This keynote was quite good, but he had the advantage of presenting something that can produce very fun and cool visualizations. But, isn’t that the whole point of a keynote: to educate, but still entertain? I can’t wait to play with this software.

Next up is Professor Robin Hanson of George Mason University to talk about “Overcoming Bias.” He joked about not having any slides, and being glad he didn’t after the preceding demonstration (how could he possibly top it?). People, obviously, have preconceived notions of just about everything. We think we understand that people are biased, but Robin is here to tell us that it’s much, much worse than we realize. I usually believe that I am aware of my biases, but this keynote made me think that I need to be more vigilant in watching out for my biases and to continuously evaluate them.

The keynote about bias was well timed, because next Nat introduced Bill Hilf of Microsoft by pointing out that it is a company that appears a bit “schizoid” from the outside, but that large companies often have very divergent views on the inside. Bill is here to give us an update on the status of Open Source at Microsoft. Bill joined Microsoft three and a half years ago, to be our man on the inside so to speak. There’s a concept within Microsoft, created by Bill Gates, called Software Darwinism. It’s exactly what it sounds like: survival of the fittest software in a highly competitive environment. Really? I’d hate to see the competition Microsoft Exchange had. Funny anecdote: a new senior programmer at Microsoft once asked if it was okay to visit a Linux web site. The moral of the story appears to be that Microsoft isn’t really evil; that Microsoft really does contribute to Open Source. I’ll believe it when Ballmer and RMS share a stage (am I biased?). Um. Wow. I don’t even know how to respond this oxymoron. Before Bill could run off the stage, Nat jumped up to put him on the spot about patents and Novell. Way to go Nat!

Nat segued into the next speaker, Rick Falkvinge, the founder of the Pirate Party of Sweden, to talk about Copyright Regime vs. Civil Liberties. While this is a very well done keynote, I find it difficult to summarize it better than the title has already done. The message Rick wants to drive home is that the real conflict isn’t the one on the surface, the one about copyright infringement and the loss of revenue. It’s really about loss of privacy. He briefly summarized the platform of the Pirate Party and showed that they have influenced other parties—in Norway. It’s a hard, uphill battle in the United States, unfortunately. Still, this guy is awesome. He’s actively demonstrating the power an upstart political party with decent ideals can have. It also demonstrates the advantage a small party can have in a parliamentary system, versus the system we have in the States.

The last keynote of the morning, Steve Yegge of Google (but not on behalf of Google), was introduced by Nat as a knowledgeable and funny person. A perfect way to cap off a great morning of keynotes. He’s here to tell us “How to Ignore Marketing and Become Irrelevant in Two Easy Steps.” Open Source developers are notorious for ignoring marketing, much to their own detriment. Unfortunately, he got started off with some technical difficulties. The O’Reilly tech couldn’t get his Mac to sync up properly with the projector system. Stupid Macs . Steve immediately questioned how people choose software. Someone in the audience answered, “logic!” We all got a good laugh out of that. Brands are like pointers. They’re a placeholder for a product in our minds. So how are these brands created? I’m not entirely sure he ever explained it beyond, “they just do.” The single biggest branding problem in Open Source is the name “Open Source.” There’s no brand, no association, and no trademark. I must say, I’m impressed. Even without his slides, Steve managed to give us a smooth, entertaining, and educational presentation. That’s the mark of a great speaker, when he doesn’t even need his slides to get his point across.

No Q&A after these keynotes, since we ran long. So we’re done here.

The wait staff couldn’t pour a beer that was anything less than half head, and they were so inefficient that the beer line was always too long to wait in. The plastic racing tricycles (!!) were broken (as if someone couldn’t have seen that coming). There were ping pong balls and paddles, but no ping pong tables.

Overheard at one point: “Well that’s Sun for you. Always promising, never delivering.”

I really enjoyed the video of a tae kwon do match as a real-world analog of software development. Try one technique, see the result (get hit); try another technique, see the result (get knocked down); ad infinitum.

There are three phases: preparation, modeling, and implementation. These phases are not linear in nature. One moves between phases as necessary to design the solution.

PDL was demonstrated in the modeling phase. Brad was pretty happy when one of the slides contained a web site address for information on PDL, which happened to be a web server at his job.

As he delved into the case studies, I started to zone out, so I have little to say about his examples of machine learning and Perl in action. I wanted to enjoy this session more, since I’ve often wanted to get back into using neural networks and other machine learning techniques in my code. Unfortunately, I just found it too difficult to follow his case studies. Still, I have some good pointers for packages that will help me sprinkle some machine learning goodness in my code.

I like his conclusion: “Perl excels at empowering people in all three phases of the development of a machine learning application.” Perl is awesome for rapid application development, which in turn gets solutions to people who need them faster.

New features include adverbial typing, such that class and module names can include adverbial modifiers. These specify things like author, authorities, and versions. The syntax is a bit scary, but they can be aliased.

Perl 6 now has inline comments (yay!). It’s typically Perl, too. The syntax is #{inline comment}, instead of the usual C-like syntax.

Wait, what’s this? Built-ins no longer default to using the $_ variable? How will I write confusing code now?

The zipper/yen operator has been renamed to Z. This is good for me, as I’ve never been very good at memorizing Vim’s digraphs.

The min and max operators now have infix versions. Strange at first, but it looks like it could be useful in some situations ($foo min= $bar).

Ranges are really lazy. So lazy they can be unbounded: for $i (1..*)... (to infinity and beyond!).

The power of the new file test operators demonstrate quite well how useful Perl 6 will be. It takes TIMTOWTDI to levels few Perl coders could ever have imagined.

There’s a MAIN subroutine now. It’s like we’ve stepped back 30 years to be C programmers again. The power it gives the programmer to define command line processing is very cool, though. Perl 6 will even call USAGE for you, if you’ve happened to define it.

Perl 6 has real repeat (do..while) loops now. Real, as in all the loop control statements work.

As if postfix control statements weren’t confusing enough. Now they can be nested! say $foo if $bar while $baz. Actually, I can’t tell you how many times I’ve wished for this.

Continuing the theme of parallelism, Perl 6 will make it easy to parallelize map and even do atomic locking on serial statements. I appreciate that Larry managed to change his slide to mirror what Simon Peyton Jones talked about in his keynote this morning. Very apropos.

Fixed-length arrays? Seriously, what is this, Java? Well, at least it allows you to define array bounds as “eh, whatever.” I especially like the “whatever whatevers” operator (**).

POD lists are dramatically cleaned up. Thank goodness. No more =over or =back. Nested lists! Tables! Bigger! More markup! Better! Includes! More awesome! Really! Useful! POD!

Honestly, I can’t wait to move to Perl 6. I can already see a lot of my code getting a lot shorter. Imagine, entire job control systems that fit in one screen of code!

This session is very much like other sessions I’ve attended. It’s essentially a brain dump of as many features Tim can squeeze into the alloted time as possible. It’s almost too much to follow. It’s certainly too much to take notes. Fortunately, he’s told us the slides will be available on-line.

From the description of the session, I had hoped DBD::Gofer would scratch an itch we have at work. Essentially, we need to ensure data finds its way into a database, even if the database may not be available. We have a custom solution at the moment, but it would be great if we could replace it with a packaged, maintained module. However, it appears that, while DBD::Gofer makes an excellent proxy, it wouldn’t fit our needs.

Examples have included connection pooling and load balancing, often to reduce load on the main database server. It’s apparent from the use cases that this module was developed for use by heavily trafficked web sites (its development was sponsored by Shopzilla.com). It’s design is modular, so perhaps it can be extended to do what we want. I won’t know until I’ve had a chance to look at the distribution.

Some interesting things for the future are HTTP caching and JSON, effectively turning DBI into a web service. This is cool. I can see this opening up a lot of possibilities as more applications are constructed from individual services, complete in their own right.

This year (being my second conference), I lack any real desire to collect t-shirts—not that many vendors have them anyway. Even if I wanted the t-shirts, I don’t want to go to the effort required to swipe my badge (thus handing over my contact information) and listening to a sales representative.

I have no interest in sales pitches. I want to see cool demos. What can this software do for me? No marketing glossies, please.

The fundamental problem with vendors at an Open Source conference is the demographics. The software is generally free. So businesses have adapted to that by selling services instead. I don’t want these services. Whenever I’ve brought these services back to work, no one wants them.

Oddly, the vendor presence I find most fascinating is the New York Times. I couldn’t figure out why they were here, so I asked. They aren’t selling anything (though they are recruiting Open Source talent—good for them!). Instead, they’re showing off how they use Open Source to develop their on-line services. They even have a blog. They’re even running a BOF session on the use of Amazon Web Services, which I will likely attend.

There are a couple of other booths that are worth visiting. Intel looks cool—and is a good friend to Open Source—and OSL is demonstrating the XO-1. I’ll make a few more rounds of the floor to see if my attitude towards the vendors improves.

It was nice that the real Nat Torkington finally decided to join us. Until this morning, we were plagued by an imposter wearing a plain, boring shirt. I’m sad to hear that Nat won’t be returning to OSCON next year. First Randal, then Damian, now Nat? I’m starting to wonder if this conference will be worth attending next year. Makes me wish I’d started attending back when OSCON was in San Diego (my own home town!).

After the usual round of announcements, Nat explained that this year OSCON has a session track dedicated to people. How to work with them, how to design software people actually want to use, that kind of thing.

Tim O’Reilly’s keynote is made up of his radar, otherwise known as “What’s On Tim’s Mind This Year.” In a nutshell, he is pondering the future of Open Source in a Web 2.0 world. These days, many new things are built on top of services. Services that may be free to use, but may not themselves be Open Source. Even if the code running the services were completely open, in so many cases it wouldn’t be useful (perhaps it requires massive compute power to run, like Google). He warned the Open Source community to keep an eye of the future of information. He perceives a race to own the information that will power the future.

Next up was a bit of a repeat of Monday night. James Reinders, Intel’s director of marketing for Open Source products, stood up to plug a new product. Actually, Threaded Building Blocks isn’t a new product, but it has been newly open sourced. Intel is dedicated to support it on as many processors and in as many compilers as possible. They really want to be the drivers of parallelization in the future.

Continuing the theme of parallelization, Simon Peyton Jones from Microsoft Research in Cambridge, England, continued told us about the downfalls of locking models in parallel programming. He talked about task parallelism and what he called the atomic locking model. Instead of writing complex software to manage parallelism, traditional sequential code is wrapped to protect it from the pitfalls of parallelism—without the need to change the sequential code. This is great stuff, and something I advocate daily: remove the infrastructure from the programmer. Let the programmer focus on the task at hand and doing that task correctly.

All this focus on parallelism excites me. At work we have a huge cluster of compute power, most of which is dedicated to running individual sequential applications. Even with all of the multi-core systems we’re adding to our data center, we end up treating each core as a distinct processor. It’s a win when it comes to compute density in the data center, but we’re stuck in the old paradigm. The applications we’re using aren’t taking advantage of the increased parallelism to do more work in the same amount of time.

After all the talk of the future and parallelism, Tim O’Reilly interviewed Mark Shuttleworth, the head of the Ubuntu project. I don’t use Ubuntu, nor do I pay much attention to it, so by extension, I didn’t pay much attention to the interview. However, Ubuntu gets a lot of buzz in the Open Source community. I use (and have been known to sometimes contribute to) Fedora. More and more, I see Fedora—and, by extention, Red Hat—looked down upon by some in the Open Source community. I’ve even started to lose interest in contributing to the project. Is it still the right distribution for me? Where did my excitement about the project go?

Finally, there was a question and answer panel with all of the keynote speakers. I zoned out around this time, so I don’t know what was asked or what the answers were.

I was offered this supposed upgrade when I checked in at the self check-in terminal (why spend extra money on people to man the check-in desk?). The cost of the upgrade was US$44. However, I was told that just for me the cost would be… US$44. Boy, do I feel special. All those frequent flyer miles are really paying off.

Well, it turns out my flight was overbooked. I had a confirmed reservation, but no seat assignment. Guess which seats tend to be available after every other seat has been filled. That’s right, all those seats no one felt were worth a quarter of their original ticket price.

So, if you want extra leg room on a United Airlines aircraft, you can pony up the cash for the privilege–or just book your flight late.

It took me three days to realize that ordering a pint in Canada results in receiving an imperial pint. Not the paltry sixteen fluid ounces one might receive in the States. Nay, this is a man’s pint.

I think the fact that bars around here serve beer in their proper glassware threw me off for a while. All the different shapes (and tasty contents) distracted me.

Milestone’s featured summer menu apparently drew inspiration from southern beaches. Florida would be my guess, but none of the food struck me as being specific to any specific ethnic cuisine. I ended up ordering grilled coconut shrimp, which came on three skewers resting atop a mound of sticky rice with chunks of pineapple. It was quite good. I tend to prefer grilled shrimp over deep fried, which is good, because that tends to be healthier.

After two nights of giving in to the lure of Hoegaarden, I returned to my usual behaviours. It was time again to drink the local nectars. I paired tonight’s dinner with a honey red lager from Palomino Craft Beer. I enjoyed it very much. It was smooth, refreshing, and had just a touch of sweetness. A little Googling leads me to believe that this is a private-label beer brewed locally. I heartily recommend it.