> I've often thought about that and used similar mechanisms in my tech work.
This made me laugh because I can't for the life of me figure out what this means. Can you elaborate? Sounds interesting.
This made me laugh because I can't for the life of me figure out what this means. Can you elaborate? Sounds interesting.
Even if it's not the thing you're actively working on, something being out of place tends to stick out as wrong and will help you notice problems earlier. An example from pairing with someone at work recently: "Wait a minute, that ran way too fast, there's no way it actually succeeded" - indeed, it had failed in a way the system couldn't detect.
I kinda thought everyone does this at at least a basic level. How else would you realize your code has the wrong output?