Is the Current State of Data Processing Our Greatest Threat?

Last week, I found myself locked out of LinkedIn for several days due to their new authenticator implementation. This hiccup might explain my recent drop in activity across various platforms.

Reflecting on this, I couldn’t help but think back to an article I wrote in the late 1970s about a similar issue. My friend Steve Leibson—an accomplished engineer, analyst, marketer, and storyteller—joined me in co-authoring a book called The Great Small Business Computer Rip-Off. While the book didn’t make waves (I think my mom and maybe a cousin bought a copy), it was a big moment for us. It was our first foray into publishing, with Steve even handling the printing and binding in his garage.

At the time, Steve was leading the charge as the I/O Engineer for Hewlett-Packard computers in Fort Collins, Colorado. Meanwhile, I was working as a publishing salesman, eager to break into the burgeoning computer industry.

Now, let me set the scene for you. The early days of personal computing were akin to the Wild West. The software that powered those "hobby computers" was cobbled together by young, ambitious programmers—many of whom were still figuring out how to grow a full beard. They swapped bits of code back and forth, refining each other’s work until something functional emerged.

The small computer industry was born from the collective efforts of countless tech enthusiasts—thousands of them—collaborating on pieces of code that they shared and refined together. This grassroots exchange, a mix of functional and experimental programming, fueled a wave of innovation.

For example, I developed a simple word processor and a routine for real-time table sorting. I sold the latter to a company, which adapted it for their needs and passed it along. While it’s unlikely, there’s a chance that something I wrote is running on the computer you’re using today. Though chaotic, this collaborative ingenuity became the foundation for the technological revolution we now live in.

LinkedIn’s requirement for users to install an authenticator app mirrors the system used by my bank—a device that generates a new six-digit code every 30 seconds. I rely on this code whenever I make a wire transfer, without the cost of the physical device.

IBM soon realized that the rise of microcomputers was significantly impacting the sales of its Selectric typewriters. In response, the original IBM PC was essentially a replica of the microcomputers being developed by over 400 emerging startups, primarily based in California. To regain its competitive edge, IBM partnered with Microsoft to develop a proprietary operating system, OS/2, for its new PS/2 computer line. However, the effort ultimately fell short. IBM eventually discontinued the PS/2 line and handed over OS/2 entirely to Microsoft, which evolved into what we now know as Microsoft Windows.

An Open System in the field of computers refers to a system that is designed with interoperability, standardization, and flexibility in mind. It typically adheres to publicly available standards and protocols, ensuring compatibility across diverse hardware and software platforms. Open Systems allow developers and users to integrate various components seamlessly, thereby encouraging innovation and reducing vendor lock-in. Examples include operating systems based on open standards, such as Linux, which can be modified and distributed freely. This openness fosters collaboration and adaptability, key attributes in the rapidly evolving landscape of computing.

However, there’s a catch. Open systems allow unrestricted access to the code that powers these computers, making it just as available to those with malicious intent. As a result, computers face constant threats—ranging from hobbyists testing their skills to foreign governments aiming to disrupt critical infrastructure, such as the power grid.

I find Open Systems to be as alarming, if not more so, than the threat of nuclear attacks from unstable regimes led by ruthless dictators. This is an issue that demands urgent attention. The question remains—will it be addressed proactively, or only after a significant attack targets the United States and its allies?

Please Join Us At Convenience Store Supply Chain Management for more discussions of interest to retailers.