On a linguio-historical point "Cry Havoc" means something slightly more than a spanking. In medieval warfare a besieged city would be offered the chance to surrender with honour, and the inhabitants would keep their lives and their possessions. If they declined then the general of the besieging army might “Cry Havoc.” This would be a licence for the soldiers to pillage, kill and rape.
Sorry Max, but you missed out on all that.
Technical articles may get more or less attention, based upon one's current needs and interest, but non-technical stuff has a more general appeal and, if one is too busy at work (AND smart enough to recognize them by the headline) he/she can take a note and get back to it when at home. This just to say that, if the newsletter was strictly technical, it may lose a certain percentage of hits (mine, for sure and for what it's worth): this is something the Supreme Commander may want to have a thought on during the long winter evenings down in the bunker...
I get many bland newsletters stuffed full of vendor supplied technical content. The quirky bits and the engaging writing style is the differentiating factor which means this newsletter gets read and the others do not.
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.