Lea: The Unity design process (and how you can play a part in it)

Lea: The Unity design process (and how you can play a part in it)

Today, there are too many software systems for anyone to be an expert in all of them. If learning to manually configure a given software system to do what I want takes an hour, manually configuring it to do that thing takes 20 seconds, and it comes with a wizard that lets me create a configuration that does what I want in 15 seconds, it will never pay off for me to learn how to manually configure it until I want to do something outside the scope of the wizard - and even then it might be saner to take the output of the wizard and tweak it rather than hand-rolling a configuration from scratch.

Thus, as long as it is feasible to manually configure the system, having "wizards" to automate configuration for common use cases is actively beneficial; it allows me to concentrate on learning the intricacies of the software systems I do want to do exotic things with, rather than having to learn the intricacies of every software system I use.