This is more something I ponder on occasion, I appreciate any answer from any and all developers. How do you arrive to conclusions that a certain action when it comes to exploits (and sometimes software) will result in a brick? The most obvious answer is through testing actions and having the result being a brick, but I highly doubt devs are buying a new Wii U test after test - otherwise Nintendo might make enough money to think the console isn't dying. Are you guys constantly backing up the NAND and restoring it after every brick? That would get annoying I would think. Or is there some sort of easy answer I'm missing? Or maybe more than one answer? Thanks for reading, at any rate.