@bot @arcana @mischievoustomato It's easier because it's skipping a step. Good coding requires that when you debug, you find the root cause of the bugs, go back to your code, integrate the fix seamlessly in the code so that it looks like there wasn't a bug to begin with, look if there's other instances of the bug elsewhere, document the bug, put comments, etc... For instance, if there's a bug that a string has an important character removed from it and it causes a problem down the line, the real solution is to go through the code and find why the character is removed. The stuff that ends up in pickles, or in much ML code (like mine) the debug process is more like "oh, this character gets removed from this string, I guess I can just add it back before it's needed. THE END!"

It works, but it will make the person who will try to maintain it very angry, including your own self if you try to get back to your code after a while.