Beyond "sensible defaults", it's also important to have the defaults specified sensibly. For robust application development, mainly when working with large soft

Beyond "sensible defaults", it's also important to have the defaults specified sensibly. For robust application development, mainly when working with large software systems, I find it best to disallow "unset" configuration options and the implicit behaviour they entail. That is, every option must have its setting explicitly specified in the configuration. The defaults should exist as a "full" configuration, similar to the configuration file pgcli comes with. Unset configuration options result in a runtime error during application startup. Also, I believe I first heard of pgcli from an HN comment, and since then I have been a daily user of it.