This edition of Cutter IT Journal features five articles that discuss existing and future (but not at all fictional) risks in what we currently call the Internet of Things and that in the very near future will evolve into the Internet of Everything (IoE). It presents examples of risks and attacks in the different domains of our personal life, commercial world, and industry in which IoT devices are used, and highlights the corresponding technological and managerial challenges for confronting — even anticipating and warding against — security attacks.

This issue of Cutter IT Journal offers a variety of perspectives on what is required to ensure success in big data analytics, covering topics from methodologies to architectures, as well as a dive into one of the key technologies of the field. Our authors provide five distinctly different views on where you should direct your attention over the coming years of evolving BDA practice.

In this issue of Cutter IT Journal, we have assembled four articles that address different choices created by information systems, along with the many ethical questions raised by the algorithms that underpin them.

In this edition of Cutter IT Journal, we focus your attention on an important issue facing us in leveraging the potential of the IoT: data management and analytics. To do so, we bring to you five excellent discussions around the IoT. We plucked these articles from an overwhelming response to our call for papers, identifying those with a fine balance of the rigors of theory and research together with examples and case studies that discuss direct practical applications of IoT. 

A cursory description of the technical debt problem oversimplifies and overlooks many important details. For instance, the differences between technical debt and other kinds of debt, the different forms of intentional and unintentional technical debt, the specific coding sins that lead to technical debt, or the steps needed to both eliminate current debt and prevent future debt. On that last front, opinions vary widely, from "Run a static code analysis tool once in a while" to "Just don't write poor code." Fortunately, in this issue of Cutter IT Journal, we have many good articles that help flesh out these critical details.