Thanks for asking this, by the way. Going back to intentionally look through a few things for examples is helping me better clarify why I've had this impressio

Thanks for asking this, by the way. Going back to intentionally look through a few things for examples is helping me better clarify why I've had this impression slowly building up... 1. Some Shellcheck code titles/short messages communicate uncertainty well, but some others can read as more confident/absolute than the situation merits. 2. Broadly, Shellcheck tends to steer people away from word-splitting. Word-splitting can be a surprising PITA, so I get it. But, it's also a critical concept for understanding shell. If you are reluctantly writing Bash/shell, it's good to have Shellcheck help you avoid it. If you want or need to understand the language, you're going to have to grapple with word-splitting to get there.