Google Maps is, often, on crack
Sep. 27th, 2010 10:31 am![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
jducoeur[First of several little posts about Coronation and reflections on the reign.]
The travel to Coronation was generally fun and stress-free, at least insofar as Friday rush-hour driving ever is. But it was a good reminder that Google Maps is an automated program, and sometimes shows poor judgement. To wit: regardless of the traffic on the Garden State Parkway and New Jersey Turnpike, taking us through the middle of downtown Newark is probably *never* the right answer. This will remind me to look at the route it has laid out, and see what that actually *means*, before uncritically following it.
(On Sunday, we did the more sensible thing:![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-userinfo.gif)
msmemory figured out the route herself, and we just used Google to keep an eye on the traffic...)
The travel to Coronation was generally fun and stress-free, at least insofar as Friday rush-hour driving ever is. But it was a good reminder that Google Maps is an automated program, and sometimes shows poor judgement. To wit: regardless of the traffic on the Garden State Parkway and New Jersey Turnpike, taking us through the middle of downtown Newark is probably *never* the right answer. This will remind me to look at the route it has laid out, and see what that actually *means*, before uncritically following it.
(On Sunday, we did the more sensible thing:
msmemory figured out the route herself, and we just used Google to keep an eye on the traffic...)