I’ve made a conscious effort to stop apologizing for bugs in my code

Re:I’ve made a conscious effort to stop apologizing for bugs... by fermienrico on Friday April 24, 2020 @11:15AM (#22968853)

When you design a hammer and sell it to the end user, there are limitations on how they can use it. You simply cannot encompass and address every situation that the end user would subject the hammer to. What if they left the hammer in a hot 1500 C oven? The designer cannot design it such that it can universally work in every situation. There are usage guidelines and limitations.

A hammer that melts in a furnace is considered a bug?

The possibilities and test paths a piece of code can possibly take exceeds a very large number in a complex software application.

[ Parent | on HN ]

Re:I’ve made a conscious effort to stop apologizing for bugs... by saagarjha on Friday April 24, 2020 @12:09PM (#22969592)

Is it really a bug when your software crashes when there is no memory available? Usually, this isn’t considered one.

[ Parent | on HN ]

Re:I’ve made a conscious effort to stop apologizing for bugs... by fermienrico on Friday April 24, 2020 @07:13PM (#22973952)

Actually situations like this are still considered a bug in software. It is always the responsibility of the software to be resilient against externalities.

Zoom should work and gracefully fail if there is not a single microphone device found on the client’s PC.

[ Parent | on HN ]