Thanks for the comments Glen. YOu have to be careful with languages. Even if you know them well it's easy to make mistakes. For example in French "une demande" is a request and "une requete" is nearer in meaning to a demand. You can sometimes get yourself in trouble like that....
Another good tale! The part about French technish reminds me of a French FAE I once met with. He used an term unfamiliar to me - "clock recuperation" - which took me a couple seconds to realize he was referring to "clock recovery". Made sense, one can either recover or recuperate from an illness.
Same technish lessons for some Japanese engineers when I used the term "daisy chain" and then had to explain what a daisy chain was, starting from the old definition of a garland of flowers made by young women and then how it evolved to the meaning of serially cascaded devices.
Whatever, most engineers can find common ground in their technical languages.
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.