> it's the more blatant problems that tend to bite me, and those are eliminated by making sure all the code gets executed at least once Maybe I'm taking your r

> it's the more blatant problems that tend to bite me, and those are eliminated by making sure all the code gets executed at least once Maybe I'm taking your repeated reference to testing all 256 permutations too literally. > Try writing code for systems without the ability to debug. Or where something is going wrong and there's no way to figure out why based on logging or debugging. Or without complete (or correct!) documentation. Or for projects where, once you ship, there is no option to patch your app, so it needs to be as close as possible to bug free. Thankfully modern platforms (mostly!) avoid the last pitfall, but I've been there, along with the other situations. And I win these battles. At least I've dodged one of those bullets: I haven't worked on anything outright unpatchable just yet :). > No, I'm just not communicating effectively. And it's no longer worth it for me to try any harder. I appreciate the effort you've made.