> accidental Admittedly this may not be the best choice of words... but it was a good trade-off of length/clarity at the time for me. The longer version is: a

> accidental Admittedly this may not be the best choice of words... but it was a good trade-off of length/clarity at the time for me. The longer version is: an _ideal_ programming language (from the perspective of debugging, though not all other perspectives) would just allow a full reverse playback through time from the point-of-failure to an arbitrary point in the past. A (small) step towards that is the "Breadcrumb" as introduced by Sentry; a hint at what happened before an error occurred. I argue that, in the coding-style as discussed, and when exposing local variables in stacktraces, local variables actually serve as breadcrumbs, albeit not explicitly set using the breadcrumb-tooling. > along with a print statement yeah but the point is that in this combination of coding style and tooling print statements become redundant > third-party addon called Bugsink If by third-party you mean "the data flows to a third party" you're mistaken, Bugsink is explicitly made to keep the data with you. If by "third party" you mean "not written by either myself or the creators of my language of choice, you're right.