Keri Savoca
1 min readMar 16, 2019

--

I don’t disagree with you and if you think I’m arguing, I’m not. I phrased everything as a question for a reason. I didn’t state my opinion. The purpose was to generate a discussion.

Of course a tremendous amount of work goes into development and testing, and there will always be bugs. The question is, what do we do when these bugs have catastrophic consequences? What are the takeaways for software engineers? Your comments are kind of implying that we should throw our hands in the air and say “Well, that happened.” I’m sure you don’t actually feel that way, so that’s why I ended this article by asking for your takeaways.

Does thinking about the potential for catastrophe if an error isn’t found soon enough affect the way you approach your work?

No need to argue when we’re on the same page. Just trying to make people think.

--

--

Keri Savoca
Keri Savoca

No responses yet