I’ve added very crude support for Python to the libm40h library. I’ll continue to refine this into something stable, but for the time buing you can build using the “python setup.py build” and “python setup.py install” commands.

I’ve fixed a few bugs in the Monome m40h library, so it should be at least usable now.  After compiling the main C library with ./configure && make you can run phpize in the php directory followed by the standard ./configure && make && make install.  Python is next on the list, after that I’ll clean all this up a bit so the build is more friendly.

Last night was Yuri’s Night 2007, and it was pretty cool. It was held at a hanger in the NASA Ames Research Center in Moffett Field, CA. Ihave some pictures here, but for actually good pictures go checkoutLaughing Squid’s post on the night. The tour of Ames Research Centerwas very cool it included the ArcJet, Columbia super comptuer, and Future Flight Central.

Gopal recently blogged about ways to minimize your value to the company. The last item on the list being “Contribute to an open source project”, stating:

Assume your full time job involves working on an open source project. Now answer me this, “what *competitive* advantage does your work bring to this company ?”. After all the code that you write automatically becomes available to everybody - irrespective of who paid for the development costs. Code thus released drops to near zero value and ergo, the process of creating it …

While I enjoy the humor in the post, and the fact that there is some truth to the above, I would say that I’ve seen substantial benefits to having persons within your company dedicated in part or full to working on open source projects. This makes the assumption that your company in fact uses said project of course. (not all these are great arguments to the above, just thoughts on the matter). (please also take note of Gopal’s PS update.)

• Internal Know-how: You company gains internal knowledge about the inner workings of the open source projects your company relies on. This is useful for when the shit breaks, and you need to fix it… like right now.
• Customize: While it’s not always contributed back, having someone work on a project lends itself to customizations for performance or other gains that reside within the company or are made available as patches because they are too risky or custom for inclusion within a standard project distribution. PHP is good example of this, with a number of patches that have been proposed, not accetped, but still made available for other’s use. Facebook also has a number of internal changes to PHP that aren’t proper for inclusion within PHP itself. (while this doesn’t always adress the Gopal’s point, I think you can see where there’s a grey area of an individuals ability to do this based upon their past work with a project).
• Quid pro quo: A number of open source projects that save companies a significant amount of money and development costs are often (but not always) the sumation of contributions made by a large body of individiduals and individuals within companies. For this type of cooperative work to continue, you need to make contributions back. You may not see the direct tradeoff for your work, but you’ll definitely build up some karma that you’ve probably already cashed out on or may in the future
• Many eyes are better than one: When working on changes to an open source project, or creating something new, it’s often nice to have it reviewed before you put it into use for everyone to see (and possibly laugh at). It’s even better if you get it reviewed by your co-workers, your co-developers, and get it in about a hundred other peoples production environment before you decide it’s stable enough to use. It’s also great when they fix something before you do, simply because you decided to show it to them.
• Come work for us: in silicon valley it’s important to have a name that draws in top tallent. Part of this name recognizition is working on really cool shit, and making this cool shit open source. Letting people know that you’re part of a community and not a nameless corporation is a big selling point for building to notch development team.

Item number 2 was “Write a technical blog”, I better go shave %1 off of PHP runtime to make up for this…