Excel should not force you to fight the tool just to write what you mean. The user who typed `-1-10` and watched it become `-11` isn't making a mistake, Excel is. And the fact that switching to manual calculation only adds a strikethrough instead of solving the problem tells you everything about how the software prioritizes its own logic over yours.
This is a small frustration with a big lesson. When a spreadsheet interprets `-1-10` as arithmetic rather than a range notation, it reveals a core assumption baked into legacy tools: that numbers are always for calculating. But data work is not only math. It is labeling, describing, referencing, and organizing. A user trying to write a range like `-1-10` is doing something perfectly natural in any other context, specifying a sequence from negative one to negative ten. Excel sees subtraction and jumps to compute. The workaround? Prefix the entry with an apostrophe or format the cell as text. Those fixes exist, but they shouldn't be required for such a basic need.
What this means in practical terms is that millions of users lose time every day correcting software that should be correcting itself. The user in this case tried the obvious path, changing calculation options, and got a line through the result, not a solution. That is not a user error; it is a product failure. A tool that cannot distinguish between a calculation and a label is not intuitive. It is rigid. And rigidity in data tools does not just annoy people, it slows down work, introduces errors, and makes users feel like they are the problem.
Our view is clear: the future of spreadsheets should not require users to learn secret escape hatches just to write what they see. An AI-native approach would understand context. It would recognize that `-1-10` might be a range, check the user's intent, and offer a choice rather than force an assumption. Until then, the best advice is practical: use an apostrophe before the entry, or format the cell as text before you type. But do not mistake the workaround for a feature. The real fix is building tools that listen first and calculate second.