Developer's Toolkit

Blog archive

Excel Flunks Basic Math

If you were in IT in 1994, you probably remember Intel's huge Pentium recall because of floating point math errors. The errors seemed tiny on the surface (Byte magazine estimated an error every 9 billion calculations), but a small error carried across a massive set of spreadsheets and other apps equals big, big problems.

Today's Excel has a similar problem but since this is software, not processors, fixing this bug shouldn't cost the $200 million or so that Intel shelled out.

Microsoft says that Excel can produce an error when calculating a problem that should return 65,535 or 65,536 as is its result. Somehow, Excel adds 34,465 (or 34,464) and gives 100,000 as the sum. Weird.

Posted by Doug Barney on 10/01/2007


comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube