Kibera in Nairobi, Kenya, widely known as Africa's largest slum, remains a blank spot on the map. Without basic knowledge of the geography and resources of Kibera it is impossible to have an informed discussion on how to improve the lives of residents. This November, young Kiberans create the first public digital map of their own community.

Theme of the symposium was “la ville cartographiée” (the city map), and to give our contribute to the discussion, we were warmly welcome to the ‘Cité des sciences et de l’industrie‘; built in the 19th arrondissement, just beside Parc de la Villette, ‘La Cité des Sciences et de l’Industrie’ is one of the world’s largest and most visited science museums, and looks as an impressive modern site which offers a wide variety of exhibitions and shows.

15 Questionnaire

It would be very interesting if you could share a mockup, template of your questionnaire. Or if specific to each projects you are creating, at least, the type of questions in the questionnaire.

On the side of the No No for projects, setting a deadline for delivery of the projects or even a step without having all the materials which guarantee the delivery date.

We have to be very careful when committing to dates, to also set the right expectations of the client. Too often, in a project, it is possible to say, let’s release this section at this date YYYY-MM-DD, the materials will be given to you in the next two weeks. Red flag. It is often better to say, once given this list of items (deliveryDate), we will be releasing this section at “deliveryDate 10 business days”.

In middle size agencies, there is also an issue of resources management. There is more than one project in parallel. Explaining to the client that if he/she misses a particular window, the project will be delayed.

Keep written records of every discussions you had, put down the RESOLUTION and the ACTION. After each meeting, send your meeting minutes to the project participants and the client. It is often better to have a scribe. If you get phone calls from the clients (which is fine), send a summary of the discussion just after.

If you are using a project management system (be mail, sharepoint, basecamp, etc. anything), if the client says “It is not the way I work”, rise a red flag again.

Be careful also of the “just this time” or “just for once” on a exceptional work issue, because if you authorize it once, the client will keep the foot in the door, to reuse it again.

posted at 10:38 am on October 21, 2009 by karlcow

Places & Spaces: Mapping Science is meant to inspire cross-disciplinary discussion on how to best track and communicate human activity and scientific progress on a global scale. It has two components: the physical part supports the close inspection of high quality reproductions of maps for display at conferences and education centers; the online counterpart provides links to a selected series of maps and their makers along with detailed explanations of how these maps work. The exhibit is a 10-year effort. Each year, 10 new maps are added resulting in 100 maps total in 2014.

Way back in 2006 I wrote a blog post concerning the modelling of time in RDF (see Refactoring Bio With Einstein Part 3: Temporal Invariants. That post also provoked some discussion in the blogosphere. Although I haven’t written anything on the subject for the past three years I haven’t stopped thinking about it. In fact I’ve been working quite hard on the problem, mainly by modelling real data, especially geographical information. This is the first of a series of blog posts describing my experiments. I’d like to thank Leigh Dodds and Jeni Tennison who gave me valuable feedback on an earlier version of this write-up.

tldr is an application for navigating through large-scale online discussions. The application visualizes structures and patterns within ongoing conversations to let the user browse to content of most interest. In addition to visual overviews, it also incorporates features such as thread summarization, non-linear navigation, multi-dimensional filtering, and various other features that improve the experience of participating in large-discussions.

# There are meaningful “entry points” into the app - URIs. (No, I’m not going to mention the R-word.) It’s simply entirely unacceptable for a Web app to expose only a single URI, break the “Back” button, and disallow linking. Frameworks that don’t support URIs for application concepts, such as every customer, order, contact report, document etc. should simply be banned.

# Application boundaries are a concern to developers, not users. The Web is about linking stuff together, without any concern about application boundaries. There’s absolutely no reason why you shouldn’t be able to follow a link in your CRM application that takes you to a product page in your online catalog, or from a customer record to the information about when they last logged in to the Web site, or from a page that’s part of a complex business process UI to the appropriate documentation and on to the discussion group where you can tell everybody how much it sucks.

# Documents are accessible in a standard way. The idea of accessing any kind of document, such as an insurance application form that’s been scanned in, a letter sent to a business partner last year, or a contract with a business partner, by any other means than an HTTP GET is just stupid.

A one-sentence overview of the poster concept

A scientific poster is a large document that can communicate your research at a scientific meeting, and is composed of a short title, an introduction to your burning question, an overview of your trendy experimental approach, your amazing results, some insightful discussion of aforementioned results, a listing of previously published articles that are important to your research, and some brief acknowledgement of the tremendous assistance and financial support conned from others—if all text is kept to a minimum, a person could fully read your poster in under 10 minutes.

A subsequent discussion about "inserts" revealed that Google had initially been unaware of the complications of the book licensing environment and that the education process led to considerable delay in reaching an agreement.

Google ne connaît que les process et les standards qu'il crée. Demander à Google de faire comme tout le monde demande un long travail d'éducation.

So we discussed this challenge of reframing things and some how that lead to a short discussion of parenting — getting kids to try things that they don’t want and disallowing them from doing things they shouldn’t. This point came up directly — “yeah, and they’ll say — can I wash the cat in the toilet?” Somehow this started the story, where we ourselves reversed our assumptions and looked at it from the positive side. How do you encourage unconventional, presumably preposterous things and not assume failed results?