> How about don't write shitty software. Just because joes flower shop wants shitty custom database software doesn't mean I can't push the state of art and what's possible.
"I write perfect software, which will always either crash or run perfectly." Given the fact that runtimes like Python and Node have had problems in this field, I'm calling bullshit.
But that glosses over the fact that you might need to run some software that you didn't write (shocker, I know). If that software has non-fatal failure modes, logs won't help you. Logs won't help you with most fatal failure modes anyway (you need coredumps in most hard cases).
Thinking that "stop writing shitty software" is a solution to the existence of bugs is just harmful to anyone who has to manage your software. If you think your software had never failed, that's because the people debugging it didn't want you in the room at the time.
"I write perfect software, which will always either crash or run perfectly." Given the fact that runtimes like Python and Node have had problems in this field, I'm calling bullshit.
But that glosses over the fact that you might need to run some software that you didn't write (shocker, I know). If that software has non-fatal failure modes, logs won't help you. Logs won't help you with most fatal failure modes anyway (you need coredumps in most hard cases).
Thinking that "stop writing shitty software" is a solution to the existence of bugs is just harmful to anyone who has to manage your software. If you think your software had never failed, that's because the people debugging it didn't want you in the room at the time.