I don't think he's talking about the power user. It's geared at the pragmatic user who wants to get work done. However, it assumes there is always an objective

I don't think he's talking about the power user. It's geared at the pragmatic user who wants to get work done. However, it assumes there is always an objective better way. That's something I'm not convinced of. The rational that reducing choices will lead to less software bugs is certainly true, though. That's the reason I'd pick to have less config. Config options generally map directly to conditionals in your code base, which means more potential code flows and multiplicative combinations of possible things your code can do depending on what is turned on and off. There is a real maintenance cost to having lots of configuration.