Desmond File

Blog archive

E-Mail and the Law of Unintended Consequences

I've always been a big fan of the law of unintended consequences. Whether it's Henry Ford's invention threatening to melt the polar ice caps or Ray Kroc's innovative fast-food business helping transform America into the most obese nation on earth, it seems that even great ideas can have terrible consequences.

Ask Ray Tomlinson. He knows. The man who invented e-mail back in 1971 was interviewed this week by the Times Online and said he had no idea how huge his innovation would become and the threat it might unleash.

"At that time, the number of people who used e-mail was very small -- maybe between 500 to 1,000. So if you were getting spam, you'd know who was sending it. You'd be able to say to them: that's not a good thing to do," Tomlinson told the Times Online.

The lesson seems pretty darn simple: If you design something to become a success, you better be ready to manage the wages of that success -- whether it's an unintended side-effect, an environmental impact or simply bad people leveraging that success against others.

What's honestly surprising is that software designers often fail to pay full attention to the law of unintended consequences.

Microsoft's ActiveX is such an obvious case in point that I'm almost reluctant to use it here. But ActiveX should stand as an object lesson of what not to do with a software architecture. Intended to enable rich, desktop-like, Web-served applications within Internet Explorer, ActiveX instead emerged as an unacceptable security risk. The same tight and rich integration that made ActiveX so valuable for applications also made it a perfect vehicle for malware.

As with Ford's mass-produced automobile and Kroc's fast food restaurants, Tomlinson's e-mail and Bill Gates' ActiveX are, to an extent, victims of their own success.

"E-mail is like any tool -- it can be used for good or bad," Tomlinson said.

Have you had a development effort that's run into the law of unintended consequences? What did you do to remedy the issue? E-mail me at mdesmond@reddevnews.com.

Posted by Michael Desmond on 03/13/2008


comments powered by Disqus

Featured

  • New 'Visual Studio Hub' 1-Stop-Shop for GitHub Copilot Resources, More

    Unsurprisingly, GitHub Copilot resources are front-and-center in Microsoft's new Visual Studio Hub, a one-stop-shop for all things concerning your favorite IDE.

  • Mastering Blazor Authentication and Authorization

    At the Visual Studio Live! @ Microsoft HQ developer conference set for August, Rockford Lhotka will explain the ins and outs of authentication across Blazor Server, WebAssembly, and .NET MAUI Hybrid apps, and show how to use identity and claims to customize application behavior through fine-grained authorization.

  • Linear Support Vector Regression from Scratch Using C# with Evolutionary Training

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the linear support vector regression (linear SVR) technique, where the goal is to predict a single numeric value. A linear SVR model uses an unusual error/loss function and cannot be trained using standard simple techniques, and so evolutionary optimization training is used.

  • Low-Code Report Says AI Will Enhance, Not Replace DIY Dev Tools

    Along with replacing software developers and possibly killing humanity, advanced AI is seen by many as a death knell for the do-it-yourself, low-code/no-code tooling industry, but a new report belies that notion.

  • Vibe Coding with Latest Visual Studio Preview

    Microsoft's latest Visual Studio preview facilitates "vibe coding," where developers mainly use GitHub Copilot AI to do all the programming in accordance with spoken or typed instructions.

Subscribe on YouTube