If you’ve ever sat in the driver’s seat of an automobile, you’ve used the dashboard—or “instrument cluster,” to use the technical term. The dashboard puts all the information you need front and center, so you don’t have to take your eyes off the road to see what’s going on with the car.
Once upon a time, computer programming was done in “machine language;” the low-level instructions that told the computer’s processor exactly what to do. At a somewhat higher level was assembly language, which hid much of the processor-level instructions but was still painstaking, easy to mess up, and hard to debug. Both levels were also specific to a type of processor; programming a computer with a different manufacturer’s processor meant learning a whole new language.
Among the more farfetched artifacts in the Star Trek universe is the medical tricorder. It’s a handheld device that can read a patient’s vital signs and even diagnose diseases when held near the patient. There’s no need for blood draws, biopsies, or waiting for lab results; just “wave the magic wand” and get all the medical information you need within seconds.
We’ve discussed recently the importance of firmware engineering, especially in light of the coming deluge of Internet of Things (IoT) devices.
Today we go into a bit more detail about firmware development: How we got where we are in the evolution of firmware development, some of the main differences between firmware development and PC or mobile software development, and how those differences drive the execution of a firmware project.
Cryptocurrencies, especially bitcoin, are making headlines these days. When speculators run-up cryptocurrency value vs. the dollar, euro, and other government currencies, a speculative bubble results that can eventually burst. The resulting price crash causes significant financial losses to those became players late in the game.
Digital transformation: What is it? What can it mean to your organization? What does it take to be successful in a digital transformation initiative?
