Getting lost is the best way to learn an area. And what a chance to discover things you didn't know were there. Getting directions might in reality be a waste of time better spent in exploring uncharted neighborhoods. Call it the
conquistador syndrome. Onward to the cities of gold...
It seems the male reluctance to stop and ask for directions is more a western observation than the east. With confusing street names and 5 or more lines of addressing (not to mention no street names!) in countries like India, every one, male or female, stops and asks for directions!
You bring up a really good point. There's hardly any reason to be lost now with everything at our fingertips--that wasn't true in the past. But really, is that the reason--the quality of the directions received? Hmmm.
Generally, the reason that I (and most guys I know) don't stop to ask for directions is that most people (of both genders) are terrible at giving directions, even when they know where you're going. It's much faster to read a map or use a GPS.
I don't understand. What does "when lost" mean?
And aren't directions something that you GIVE, not ASK FOR?
Seriously, save the bother and expense of downloading yet another App. Just go ahead and have your wreck. Then you can ask the paramedics for directions and your friends will never know.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.