The specification

I have always felt that it is better if I know upfront upon reading something what I shall be building and what its goal is. Even a vague specification is better than no specification at all, so in this spirit, let’s turn to our imaginary scenario again:

The management would like to have a way to quickly browse all the cars in the database and have an overview of them – how many Volkswagens or Fiat Puntos are available, what the average production year is, and so on (this one is pretty vague, but we get the idea). The management would also love to receive and be able to send automated reports about cars that have been added in the last 7 or 30 days.

Armed with our FARM stack knowledge, we know that we can tackle this, but what’s more important is that we know that we will also be able to address future requests, modifications, and features, while using the same technologies and finding a very cheap (or free!) deployment solution to kickstart...