Skip to Content Skip to Search Go to Top Navigation Go to Side Menu


"Web" Category


Python


Saturday, March 31, 2007

I’m mainly a perl programmer, but last week I’ve decided to explore the python language.

To keep my motivation high I’ve decided to use python for something useful to me: download every day my favorite web comic into the Pictures directory of my home directory on Mac OS X and keep it uncluttered by removing older episodes.

In the working of the project I’ve learned how in python to scrap web sites, parse XML with DOM, handling exceptions, manipulating the filesystem, doing time calculations, using regular expressions, …

Python is quite cool, and I’m planning to further improve the application.
I’m still using the default Mac OS X python, the 2.3.5 without readline :-(
I’ll try to install a more recent version with readline support.
Python 2.5 is tempting by I don’t know if it is well supported yet by Trac, an open-source python project I’m intending to hack at some point.

I’ve added in my del.icio.us bookmarks a bunch of links that I’ve found helpful.


Flickr Photos Clouds


Saturday, March 24, 2007

Two alternative ways to navigate my flickr photos thanks to netomer’s flickr inspector:

Designed for me


Saturday, January 27, 2007

Interesting article about software design methodology: design for one or two typical users, don’t try to satisfy all users.

It makes sense to me it’s a better to make one user happy than discontent everyone.
The trick I suppose is to correctly profile this one typical user.

I think it does apply to any product, not only software.

I wonder how Apple do identify THE user and what is their typical user’s profile (called ‘persona’ in the article linked above). I ask that because I like so much some of their product I feel like they were designed for me alone :-)
Although I like technology It very rarely translates into an acquisition: I still don’t have a portable media player.

It’s only when I need it enough and like it a lot both inside and outside and feel like it was made for me that I may consider a purchase action (that can take weeks or months).

One of the Nokia E-series smart-phone is about to land in the purchase action and the Nintendo Wii has left the parkway for the runway, but I don’t how long is the flight :-)

The other interesting thing is there seems to be a relationship between money earned by product sold and a user’s satisfaction.
It might sound like stating the obvious but not to all company seem to get it.
Apple and Nintendo are making huge amount of money for each product they sell compared to their respective competitor (Sony loses money for each console sold, PC market is sluggish with a industry’s growth far below Apple’s)

Why?

I bet they are a lot of users of Apple and Nintendo who feel like their acquisition was designed for them. It makes them happy and make them in better disposition to invest more into the product (service and software, new versions).

(an interesting comparative read is the “after the honeymoon” reviews for the Wii and for the PS3 at Ars Technica: guess which one of the review feels more positive and transpire reviewer’s happiness at using the product?)

Typically when designing for a subset of the users population, you’ll reach a smaller number of people.
I think that’s called a niche market, but who cares as long as both side of the transaction are happy: Product maker earns money (typically the margin are higher) and the user (notice, I didn’t say consumer) is happy, a perfect virtuous circle.

Now that’s obviously not true for the iPod whose market share cannot really be called a niche.

I think, in addition of an excellent user profiling, I suspect there is the fashion effect. At least here in the UK, I’m sure most people who buy an iPod do so because it’s fashionable, not because they studied what media players are available and selected the iPod because it’s the ONE (by the way, this is how I bought my first mac in 1996, after months of study of what’s in offer by the computer industry at that time).

That said, some of them will find the iPod is not what they wanted, while other will really like it and makes them happy of their purchase. They will explore the possibly of iTunes (software) , buy more songs on iTunes Store (service) and possibly look into other Apple products: the Halo effect.

Transforming a normally niche (i.e: small market share, high margin) product into a mass-consumption product is probably the dream of any company.

Apple has now made it, Nintendo’s got the idea and works on it and Nokia made it long time ago.

The others?

Just too busy milking as many as possible uninformed or misinformed consumers (notice, I didn’t say users) ’till the last drop while trying to destroy each other.

I’m not saying the mentioned brands don’t do that, I’m saying that’s it’s not their main focus and they don’t get carried away by the necessity of a capitalist world.

Disclaimer: I’ve mentioned Apple, Nintendo and Nokia because they made products that I’m happy with, I fully understand that people can be happy with product from other make, we are all different after all :-) It just turns out that, in my opinion, these three are coincidentally particularly good at designing product with specific profile of user in mind, which explains why they excel in their niche(s).

One last message to gadget makers:
If you are desperate to get me buy your product, read my mind (but don’t listen to me) and design it just for ME, then may be I will.

The grave of the fake ones


Sunday, January 14, 2007

Now that Apple unveiled the real “thing“, This website shows a photo gallery of some fake designs that appeared on the web when the “thing” was still a crazy recurring rumour.

Google Zeitgeist


Sunday, January 14, 2007

It’s fascinating to read the Google Zeitgeist (the list of the most frequent queries to Google search).

the list for November 2006 in UK is very illustrative of the period (pre-Christmas shopping season).

It was interesting to see “cricket” appearing in top 15 in India but not in UK.

It also show that greek people are searching for a hedonistic life, may be to try to have a similar life to all of these celebrities that are searching on Google :-)
And of course there are the eternally popular queries in almost every countries: Jessica Alba, Paris Hilton, Angelina Jolie, Britney Spears.

Finally, I admire the concision of danish queries

In the same vein, Digg.com links to an article about what chinese are searching for the most in Baidu (the most popular search engine in China)

Buzztracker


Saturday, January 13, 2007

Buzztracker - World News - 2007-01-12

Almost a year ago, I discover a web site that track global news and represents them on a world map as circles. The larger the circle the more frequent are the news about the place. Buzz tracker also represents inter-references between places in the news articles by a link between two circles.

Using the image available on Buzztracker.org site, I’ve made a small film showing the evolution of the map over 14 days (7 of them consecutive, for the others I have been a bit lazy).

It’s interesting to see that the biggest circles are almost always the same (Iraq, big western cities) but the smaller ones are more mobile.

[QUICKTIME rtsp://streaming.pommetab.com/streaming.pommetab.com/buzztracker.mov 320 257]
CC licence images in the film are from buzztracker.org web site and the film is licenced under the same Creative Commons licence.

Google’s Answer to Filling Jobs Is an Algorithm


Friday, January 5, 2007

Fancy becoming the input data for an algorithm? In other word, do you want to apply for a job at Google? :-)

Google’s Answer to Filling Jobs Is an Algorithm: “An anonymous reader tipped us to a New York Times article about Google’s newest HR tool: an algorithm. Starting soon, the company (which gets roughly 100,000 applications a month) will require all interested applicants to fill out an in-depth survey. They’ll be using a sophisticated algorithm to work through the submitted surveys, matching applicants with positions. The company has apparently doubled in size in each of the last three years. Even though it’s already 10,000 employees strong Laszlo Bock, Google’s vice president for people operations, sees no reason the company won’t reach 20,000 by the end of the year. This will mean hiring something like 200 people a week, every week, all year …”

(Via Slashdot.)

Azureus Partners with the BBC to Sell TV Shows


Tuesday, December 19, 2006

… in the US.

“The popular BitTorrent client, Azureus has just struck a deal with the BBC to offer TV shows on its recently launched content store/website, Zudeo.”

read more | digg story

Boing Boing: Firefox ascendant in Europe


Friday, December 8, 2006

I like maps. So here is a nice one representing the usage of Firefox in Europe:

Firefox marketshare in Europe

source:

Boing Boing: Firefox ascendant in Europe

Doing a Demo? Don’t Rely on an API


Monday, October 30, 2006

And that’s why automated testing of the integration points are very important!

I’m currently involved in a huge project made of multiple components.
To each component corresponds a project team.
My direct upstream dependency is a web API.

In addition to our own unit tests and system tests, we’ve got a set of test scripts that monitor the features we are using. That includes:

  • validating the supplier API against their own XML Schemas (Relax-NG in our case) for the API calls used in our system
  • If both components use a common set of reference data, a test to check that the data set is the same in the API and in our component

There’s trouble only if the XML Schemas are not updated when changes are made to the API.

As the tests are run regularly we discover changes in supplier’s API quickly. If we don’t have time to make the change in our side (e.g: 5 minutes before a demo) we switch to another instance of the API with the old code (the supplier has a set of rolling instances that guarantees that the previous version of the API is always available on an instance). This is not really applicable with public APIs.

An additional step we have taken is to mock up the results of API calls into static XML. These are normally used for our internal system testing, but if the integration tests with the supplier fails and there isn’t a workable instance of their API, we can switch to the static XMLs (this situation happened once in our project).

This approach will also work with public APIs that output XML like Flickr’s API and Amazon REST service.

Doing a Demo? Don’t Rely on an API: “

Eurobuddy Matt was doing a presentation when there was an API change at GoogleMaps. He’s a quick fella, but I’ve been caught with my pants down.

(Via ONLamp.com.)