Error gossip and last words

So far, we’ve only used the Rails framework with most of the default options. These default options include some configurations that would otherwise hinder and slow down the overall experience for the end user. These options make sense in development, as they make debugging and testing really easy. As developers, we need to be able to set up our local environment as soon as possible and start programming away. However, these default options do not make sense in a production environment. One of these defaults concerns error reporting. We saw locally how errors are displayed, but in a real-life scenario, we would never want these errors to be shown in the same way. We would not want detailed error output stating paths, variables, or even what database we’re using, as this could be a security breach, or at least the beginning of one. We would want the error to be like gossip: quiet and behind our backs. And that’s exactly what we’...