Isn’t this still true for the large language models and math is detected and handled by an external tool? Anything you can give as a source for the latest state of the art?
Sending power outage context to the vehicles does not seem like enough of a response. I hope at least they have internal plans for more. For large, complex systems, you want multiple layers of protections. The response feels way too reactive when they could use this incident to guide improvements across the board.
Maybe I’m just a skeptic, but it seems like a software engineer or SRE familiar with the application should be able to come to the conclusion of load testing fairly easily. For sure not as fast like 80 seconds though which is impressive. As noted you still need an engineer to review the data and complete those proposed action items.
I think the idea is you could still have a page in the UI that shows archived data but you wouldn’t do that normally with a soft delete. The lifecycle thing makes it up front with the user instead of hiding soft delete as an implementation detail.
In Visual Studio if you drag the execution arrow up, it will rewind to that point. It works really well. It’s okay especially useful when you step over a line you wanted to step into instead.