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 [email protected].

Posted by Michael Desmond on 03/13/2008


comments powered by Disqus

Featured

  • IDE Irony: Coding Errors Cause 'Critical' Vulnerability in Visual Studio

    In a larger-than-normal Patch Tuesday, Microsoft warned of a "critical" vulnerability in Visual Studio that should be fixed immediately if automatic patching isn't enabled, ironically caused by coding errors.

  • Building Blazor Applications

    A trio of Blazor experts will conduct a full-day workshop for devs to learn everything about the tech a a March developer conference in Las Vegas keynoted by Microsoft execs and featuring many Microsoft devs.

  • Gradient Boosting Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the gradient boosting regression technique, where the goal is to predict a single numeric value. Compared to existing library implementations of gradient boosting regression, a from-scratch implementation allows much easier customization and integration with other .NET systems.

  • Microsoft Execs to Tackle AI and Cloud in Dev Conference Keynotes

    AI unsurprisingly is all over keynotes that Microsoft execs will helm to kick off the Visual Studio Live! developer conference in Las Vegas, March 10-14, which the company described as "a must-attend event."

  • Copilot Agentic AI Dev Environment Opens Up to All

    Microsoft removed waitlist restrictions for some of its most advanced GenAI tech, Copilot Workspace, recently made available as a technical preview.

Subscribe on YouTube