My goal with this blog

I write about relevant changes in the way that people use the web and how startups are built to provide services and products for this ever changing wonderful thing we still know as "the web." As a former entrepreneur turned early-stage investor, my greatest hope is for this to be useful to other folks that are like me in the hopes that they can avoid some of the mistakes I've made.

The Culture of Tools

I've spent the week interviewing for a new engineering we've got and have met with some good folks. Among the things I like to talk about is programming language preference. Now I know that all good "computer scientists" are not supposed to care beyond the fact that a language is Turing complete, but the reality is that asking a potential developer about language preference is akin to asking them about their esthetic without sounding pretentious.

One of the things I always try to get to right away when talking about programming languages is the strong-verus-dynamic question. I am a firm believer that late-binding (latent typing) languages like Python, Ruby, and even Perl are one of the best tools for developing products when you don't really know what it is you're going to end up with when you start. A lot of smart people have made this very observation before so I am not going to belabor it here. But I was a bit surprised this week when I heard from someone who I was fully expecting would embrace the dynamism of the Python (by stuff I'd seen on his blog) that the dynamic nature of Python wasn't what really drew him to it.

After giving this a little thought, I realized that he was right in the following sense: the open source languages are just as interesting for the communities they attract (and what ollows from these communities) as for any major features in their design/implementation. I would still contend that latent typing is a Very Good Thing for a lot of application work but I am glad to be reminded that comp.lang.python (and all of the culture that comes with it) can be just as important.

One quick example: among the folks I met this week was a very senior J2EE architect that came highly recommended from a series of very successful venture-backed startups. The guy was clearly very sharp and a true Java expert. During our conversation he let it be known that Aspects were the new Holy Grail for the bleeding edge of Java. Never having really understood the big deal with aspects, I spent most of our hour together quizzing him about the way he had successfully used aspects in his recent work. He gave me some examples and then pointed to some other open source luminaries who are better future architectural directions of aspects.

And yet at the end of the day, all that I came away convinced of was that aspects were a hyped up version of decorators in python. Now we use decorators in our app for a couple of neat hacks but I never would have thought to make a big deal about it because I happened to have read about them one day while following an interesting debate on comp.lang.python.

It's good sometimes to look up and see the forest for the trees.