As with any SQL Server feature, maximizing its potential involves tuning that feature for your specific environment. Common advice would be to begin with the defaults, then compare these with commonly agreed best practices and adjust those to what makes sense for your use case if necessary. Often there will be a widely accepted set of best practices within the community for typical deviations from Microsoft defaults. Sometimes defaults that appear "dumb" are often set that way, not because Microsoft is ignorant of its product or user base but for backward compatibility reasons.