borracciaBlu

The article conclude stating that you should still know more than maps and decide by your own, but it gets against the whole idea of using the apps in the first place.

I do use google maps because it has more information than i do else i wouldn't use it at all.

In particular, i think the story is the perfect case of what's happening when the only metric available to evaluate a route is ETA.

I would say this is a missing feature which i would call `Route difficulty` or similar.

This would be the same concept used in some cooking recipies that have tags stating if the recipie is doable for a beginner.

I think, as part of the `Route difficulty` metrics they could use:

- number of petrol stations and distances

- road slope (more than 30 deg could be challenging)

- traffic (if something happen, how many people will pass by to have support)

Having this additional metrics would make the life so much easier and safer to evaluate the best route to take.

If think about estimate as learning activity in the sense of Theory Building, then you won't really care about the estimate by itself (which is a nice by-product) but as a confirm that the task is clear and actionable. In that the real value I think.

I've been witness of developers not working in isolation, with clear specs and requirements, who knew what was the expectation and still use the tech they preferred.

I would say they were unprofessional and selfish. Not great as cultural fit neither.

Discipline should came first. Imagine you go to a restaurant and order a pizza and instead you receive sushi just because the chef wanted to learn a new cooking style..

Hi nik3r do you have any screencast using the product? If so, could you share the links pls?

do you still fill productive with your phone on the desk?