The problem with that approach is the sentiment that, given sufficient effort, you can eliminate errors when, in fact, failure is the default state of software. And when software fails, the better that users, support people, and developers understand what actually happened, the more effectively they can address the underlying problem.
I don't think anyone is suggesting not to expect errors. It's just a Fluffy quote. Like, the best weapon is one you never have to fire. It's being over-thought.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The problem with that approach is the sentiment that, given sufficient effort, you can eliminate errors when, in fact, failure is the default state of software. And when software fails, the better that users, support people, and developers understand what actually happened, the more effectively they can address the underlying problem.
I don't think anyone is suggesting not to expect errors. It's just a Fluffy quote. Like, the best weapon is one you never have to fire. It's being over-thought.