The latest articles on DEV Community by Matthew Mack (@matthras). https://dev.to/matthras https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F21085%2F74535d81-46b1-46be-bb51-9a598840ed58.jpeg https://dev.to/matthras en Matthew Mack Tue, 14 May 2019 23:43:35 +0000 https://dev.to/matthras/how-does-one-explain-to-non-tech-people-that-it-s-difficult-to-anticipate-all-potential-errors-before-deployment-hk8 https://dev.to/matthras/how-does-one-explain-to-non-tech-people-that-it-s-difficult-to-anticipate-all-potential-errors-before-deployment-hk8 <p>Recent news in Australia is that a country-wide test called NAPLAN encountered technical difficulties in its second iteration of allowing students to take the test online. </p> <p>I was talking about it on Twitter and was trying to explain how that even if we had a bunch of techs/programmers sit together, brainstorm every possible edge case and test for them, there would still most likely be an edge case overlooked, sometimes due to imperfect information, other times due to resource constraints, etc.</p> <p>The impression I get from non-tech people is that it <strong>is</strong> possible to account for every case, and to not to otherwise would otherwise signify incompetency.</p> <p>Does anyone have a nice analogy/situation/scenario/explanation that gets that message across to enable them to be nicer and more empathetic to the difficulties associated with programming and anything tech-related?</p> help