The article is wrong though. For error codes, 0 being a success value is the CONVENTION. A non-zero code is an error. This isn't about "programming languages."
The problem is that for bash `true` is a function (or builtin) that returns 0, while for C (and thus most languages) any non-zero value (typically 1 for the builtins) is true. In c99 and later with stdbool.h, `true` is almost always defined as `#define true 1`.
the existence of the && and || operators (not to mention the true and false utilities) would indicate it's more than just a convention.
Wrong is a bit harsh for a convention or semantics, more like imprecisely worded.