Jan DMaking users go through configuration steps because providing working defaults is "limiting user freedom" is a rather particular idea of freedom.
Maybe more accurately: Configuring yourself is freedom (cause you do it), not needing to configure is limiting freedom (since someone else suggested the default which is not seen as legit).
Is there something interesting in this or should it be filed at "heroic individualism mapped to a glittering generality?"
Spoofer3@simulo a limited take, I think it depends on where you are in your journey. At the beginning, I appreciate someone else's experience and recommendations... after I've become more knowledgeable or expert myself, probably not as much, until I learn some more and are able to appreciate it differently.
@simulo I vote for the latter. This reminds me of the "Jetway test" in Alan Cooper's book "The inmates are running the asylum". Some people always prefer to have full control over each single setting and others prefer to simplify their thinking and have confidence in the default settings. (1/2)
@simulo To that developer: The UX rule #1 is "You are not the user" - so stop burdening users with thousands of settings because you consider this your freedom. Unless users are bored or in a playful mood, they use software to achieve their goal, not to play with fancy settings and enjoy a developer's particular notion of freedom. (2/2)