It's been thirteen years since I updated this site. That's crazy! Who the heck's been paying the hosting fees for more than a decade to keep this dead site up? Oh, right -- me.

What took so long?

A good example of an event emitter needs three things:

• A thing that emits events
• A thing that listens to, and handles, those events
• Something that drives the two, causing events to be emitted.

Using node v0.4.11-pre, here is a small example illustrating custom event handling using EventEmitter.

The latest turn in the computer science industry is a new development process called "Marketing Driven Programming."

It is designed to make it easier for people who don’t have programming experience, but who do work in the Marketing Department, to develop applications independently of a technology or programming staff.

My seven year old daughter made a Halloween card for her grandmother. On the back of the card, she drew a pretty butterfly. The butterfly was happy. Tara added glitter to the card to make the butterfly nice and sparkly. Then, she remembered that Halloween cards are "supposed to be scary." So she changed the card a bit….

Manager-types like to look at things from a "high level." Instead of worrying about the crucial details of a project, they prefer to be a bit further off, so they can see issues from multiple angles, and how those issues relate to each other.

I don’t have anything against this. But some managers can be very literal about how "high up" they are when looking at the problem.

I wanted to use a more OO approach to error handling in perl instead of just plain old eval, so I did some looking around. I wanted it to be easy, so I looked at these modules:

• Exception
• Error
• Exception::Class

I hate job listings that describe what the job might become in the future if the immediate project is successful. It seems inherently dishonest to tempt people to apply for a possible good future job as a package deal with a current lower-paying, short-term job.