It seems that by purposely blowing up chips, you could use this clever device to create some really cool SOC devices, and also repackage things like putting (er I mean vapor depositing) an Ivy Bridge into a TO-92 package.
At a summer job in college I was in my supervisor's office when another student came in and proudly proclaimed that he had found the faulty chip, holding it in the air. "Good job!" the supervisor told him. When the student walked out the supervisor started laughing and I heard the engineer in the next cubicle also laughing. The engineer stood up with a cigarette in hand (it was legal back then) and one end of a tube that had been snaked under the bottom of the circuit board under test. That was one of the many initiations we went through that summer. If we'd had a smoke re-concentrator back then, he would have been sent to find the user's manual no doubt.
My own initiation was nontechnical for some reason, and not suitable for print.
similar to there being smoke inside all chips (and a powerful spring too if you judge by the effect of plugging a 5v chip into a 12v rail has in terms of flinging small bits of plastic around) there is also a red LED inside every green LED if you forget to put a series resistor in (admittedly once you've seen the red one the likelihood is the green one will cease working forthwith)
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.