Categories
On the web

The right medium

Just finished reading Jeff Jarvis book What Would Google Do. It’s an interesting study of applying google thinking to a wide range of other businesses. In the book he mentioned the Is google making us stupid article, which mulls over what happens if we can just search for everything, do we even need to remember anything anymore? And what happens if we shift our reading from books, to blog posts, to 160 letter twitter posts. Does that make us more stupid? Of course not! The only thing that twitter, blogs and facebook is making us better at, is choosing the right medium to convey our message. That is to say, in a more effecient way.  Some ideas are best presented in a book, some in a blog post and some in twitter. Too often books could be cut in half (anyone else noticed that the sweet spot for books seems about 200 pages?) and sometimes a blog post might as well have been a twitter status update. It’s all of matter of choosing the right medium.

Luckily ideas can start out as a simple twitter post or idle chat in the hallway and then turn into something bigger. We often play around with ideas at the IOLA office. Sometimes they end at the drawing board, either discarded or put into the ever growing stack of fun ideas to try out when we got time, and sometimes they turn into sometimes bigger, like Nemo or YayArt. The interesting part of course is always what happens when you show your ideas to the world. That is often the litmus test, will people take the idea and run with it, or was it dead before it even started.

Categories
Programming

On designing libraries

I recently finished up a big project at IOLA which used two major components: Javascript and c# (.NET). It was interesting for me to see the big difference in the libraries for these platforms. For Javascript we used the excellent jQuery library. For .NET we used the very buggy Devexpress library. jQuery, like Javascript, is very simple. .NET on the other hand is overload with interfaces and concepts. What is interesting of course is that this philosophy shines through in libraries build on top of both platforms.

Devexpress is overloaded with concepts and the size of the library is just insane, the latest release is 221MB excluding kitching sink. Compared to jQueries 19KB. jQuery on the other hand focuses on a simple core with just the right amount of abstractions (very lispy), and delegates specific functionality to plugins, such as flot. The difference of course in part comes from the fact that jQuery is an open source project, while devexpress is a commercial project.

You just have to look at the release notes for each of these projects in order to see the difference. jQuery focused on making their already working code faster and fixing bugs. While devexpress spend most of their time added a number of new features. The problem is that in a commercial project fixing bugs doesn’t pay up as well as implementing new features. Or at least that used to be the case. In the era of google that simply is not true. Anyone can put in devexpress and find out if the library sucks (which it to a large degree does) or if it rocks. The sooner they realise that small is the new big, the sooner we will start getting better libraries.

Categories
Blog

Generators and decorators in Python

Was reading through some old blog posts today and found an interesting talk about Coroutines and Concurrency. The talk is pretty long but presents some nice ideas about how to split a problem up and making it more modular using yielding. It seems like python has extended this a little so that you can actually use generators to consume messages also. What I found particular interesting though in the talk, was when he briefly showed a decorator. Decorators are really powerful and seems to bring about the best of lisps macro extensability to Python without loosing the excellent syntax 🙂 I googled a bit and found the following list of patterns that you can do with decorators.