> recognizing when your calculator gives a bogus result because you made a keyboarding error
It might be counterintuitive, but the cheaper (and therefore successful) solution will always be more technological integration, not less.
In this case, better speech recognition, so the user doesn't have to type the numbers anymore, and an LLM middleman that's aware of the real-world context of the question, so the user can be asked if he's sure about the number before it gets passed to the calculator.
It might be counterintuitive, but the cheaper (and therefore successful) solution will always be more technological integration, not less.
In this case, better speech recognition, so the user doesn't have to type the numbers anymore, and an LLM middleman that's aware of the real-world context of the question, so the user can be asked if he's sure about the number before it gets passed to the calculator.