DEV Community

Discussion on: How does one explain to non-tech people that it's difficult to anticipate all potential errors before deployment?

Collapse
 
matthras profile image
Matthew Mack

As a mathematician I'm very accustomed to asking the 'whys' (since everything can be justified logically in maths), so I appreciate your additional insight - especially the Clarke quote!

I definitely wanted to give the NAPLAN techs the benefit of the doubt, mainly because I've noticed mainstream media tending to focus on and capitalise on mistakes for headlines, which pains me to some extent.

Maybe it's easier to shrug, say "Murphy's Law" and call it a day. Obviously I can't control how people end up perceiving tech as a result, but I sure don't want it to be made any worse! Maybe the answer is to normalise and get across the message that making mistakes in tech is normal. That's something I can definitely do!

Collapse
 
picocreator profile image
Eugene Cheah • Edited

To make mistakes is human; to stumble is commonplace; to be able to laugh at yourself is maturity. ~ William Arthur Ward

What you suggested, on normalizing problems, would really help to get other to understand the problem, instead of demanding them to be magically solved.

It would definitely help the developers who are working on it, and who may have made mistakes on it - fix it. And if it's a resource constraint, perhaps lead to more resources needed for it.

Saying this as someone who's code has crashed live systems in active use before 😢