[akira2501]

> and so the very first thing that will happen in the investigation will be looking at the code with the assert

And the very next thing that will happen is me swearing up and down that I wished I captured more context at the point of error so I could understand the corner case much more easily.

assert, on failure, should dump as much function and stack context as it possibly can generate; and possibly, a string tag for _user_ convenience in reporting on and differentiating for themselves the specific error condition.

mainframes are great for this. You get a custom tagged error message that conveys the subsystem, error level, and error number along with a text error string. This makes cataloging and classifying errors automatic for everyone who sees and conveys them. Then you can use the system record store to go get the context information generated at the site of the error itself and build a much clearer idea of why the particular operation failed.

[commandersaki]

I'm more with skeeto on this that asserts should make it easy to slip into a debugger to get that further context you're looking for: https://nullprogram.com/blog/2022/06/26/