Output and errors can create a lot of signal to noise problem. When a command is run - such as a bundle install or yarn install, a significant amount of output is created - most of which is not actionable. In fact, unless there is an error there is no actionable information. For these instances we tend towards hiding output until it is required before presenting a pre-filtered version to the end-user.

From a pre-filtered version, we have already scanned the output for known issues and caveats, applying automated fixes where possible. This means that the output is targeted, provided just in time, and reduces noise for the end user.