Blog

Car dashboard

There is one thing that often frustrates me and yet it happens quite often: I am driving and listening to the radio, and at some point they play a song I like. I would love to buy it, but I don’t know neither the song title nor its author.

Sometimes radio announcers say it immediately after, but some other times (most, actually) they do not, leaving no alternatives other than firing up Shazam to discover what is the song you like. And, well, if you are driving, that generally is a poor choice.

Now, just think about how we could redesign that process to make it more effective, using present-day technology and infrastructure.

Here is one possibility I would love to see happen.

CONTINUE READING

…is not the device itself, but it is the whole ecosystem that surrounds it.Kindle, 3rd Generation

I have received my Kindle as a gift at the beginning of this year, and it quickly became my favorite gift of all time.

That can be quite surprising, knowing me. I own many different devices, gadgets and computers, but I have always been fond of the smell and feeling of paper books. Knowing that, some people were ready to bet that I would use the Kindle for just a few days and neglect it shortly after for something else (e.g. my iPad).

I must admit that I am sure this is exactly what would have happened with any other e-reader device. My experience with the Kindle, however, was (surprisingly) awesome, and it due to reasons I didn’t expect.

CONTINUE READING

During the course of the last months, we have seen frequent news of security breaches, with many websites falling victims of malicious attacks. While this by itself is not a news, the frequency and scale of this kind of attacks hardly passes without notice.

Sony’s example is probably the most visible example of this trend, as Kevin Mitnick points out.

But they are not the only ones: the attacks on Citigroup and security company RSA are even more alarming. If even those companies that should be dealing with security issues every day are not impenetrable, chances are everyone’s data is at risk. Or, at least, that’s the message that most of the newspapers appear to be conveying.

While it’s easy to dismiss those people as fools, those facts should teach us something different: there is no such thing as a secure system.

CONTINUE READING

I had been thinking about the idea behind this post for a while now, but reading this post about getting newbies involved in open source just convinced me to write it down.

Being a concept developed in the Open Source world, it is no wonder that distributed revision control systems give their best in that context. There are many pros and cons, that other people described in detail better than I can do. Of all the features they offer, however, the one I prefer is the least technical one, and it is related to the way they encourage new developers to contribute to open source projects. In that perspective, git and mercurial are a lot more effective than svn, for example.

It all comes as a side effect of authors and committers being two different roles. This can encourage new contributors, who are approaching a new project for the first time, and individuals who may not have the time and energy to dedicate long periods of their time to a project, but may be able to contribute with just a few patches.

A commit from GitHub How GitHub displays both the author and the committer of a single change. Oh, and yes, there is something wrong with the dates. 😉

Think about that. Recognition is one of the most important drivers for Open Source contributors but, unfortunately, centralized revision control (subversion, CVS and the like) doesn’t help in giving credit to newcomers or occasional contributors.

That’s because, generally, sending a single patch (or even a few of them) is not enough to be granted commit access to a project repository (and rightly so) and the commit itself must be done by a project member with enough privileges.

CONTINUE READING

As Software Engineers, we often tend to be overly optimistic about software. In particular, it often happens that we underestimate the probability of systems and components failures and the impact this kind of events can have on our applications.

We usually tend to dismiss failure events as random, unlikely and sporadic. And, often, we are proven wrong.

Systems do fail indeed. Moreover, when something goes wrong, either it’s barely noticeable, or it leads to extreme consequences. Take the example of the recent AWS outage: everything was caused by a mistake during a routine network change.

Right now, some days after the event, post-mortem analyses and survival stories count in the dozens. There is one recurring lesson that can be learned from what happened.

CONTINUE READING

During the last weeks, I’ve been writing a lot of code while commuting.

Since I was working on an application that uses Facebook’s and Amazon’s APIs and I was working offline, I often found myself unable to test the code I was writing against live data.

I must confess I struggled at the beginning.

I had no chance to try out my small application while I was working on it and, generally, I had to code during 1-hour trips, waiting until I got to work/home to see whether everything was performing as expected.

The outcome? I was surprisingly productive. And I’m sure it was not just because of the absence of common distraction sources (IMs, Email, Twitter and the like).

So, what made the difference? Here are some of the insights I got from the experience.

CONTINUE READING

Let’s start with two quick facts: 1. Google recently refurbished Google Bookmarks (after neglecting them for a couple of years), giving them more importance in search and allowing us to share them with friends more easily. 2. Meanwhile, a different team (I guess), implemented Bookmark Sync from Chrome, a new features that synchronizes bookmarks with a Google account (quite handy when you routinely use Chrome on many computers). Those bookmarks end up in a read-only directory in your Google Docs space.

CONTINUE READING

I’m sharing this story because it may be useful for someone else, as well. This morning I found out that my monitor (a Packard Bell Maestro 220wdv) was not working anymore. After messing with the cables for a while, it turned out that I wasn’t able to connect anything using DVI, while the two VGA ports were perfectly functional. I was ready to buy a new DVI cable (hoping that it was not the monitor’s fault) when I found out this forum thread, which stated:

CONTINUE READING

Knowing how much I enjoy indie games, a dear friend of mine bought me a new treat for Christmas. It’s called Machinarium, from Czech-based Amanita Design. We just finished it today, and although it wasn’t very long, we enjoyed it so much that I thought it was worth mentioning. If you are curious about the game, you can find out more here. (I strongly encourage you to check it out.)

CONTINUE READING

In Milan, like in many other cities, public transport tickets have a magnetic strip on the side that is used to check their validity by means of electronic readers. Even now, some years after the introduction of the new tickets, a lot of people still insert their tickets in the readers in the wrong direction, and can’t pass the turnstiles until they get it right. The technical reason for that is the magnetic strip placed on one side of each ticket so that it can be read by a machine, but it’s a poor design choice forcing people to pay attention to a puny detail such as this.

CONTINUE READING