— Jason Lengstorf said:
Over half the people are gonna choose the default. So, by default do the right thing and you immediately have improved whatever ecosystem/community you’re part of.
— Jason Lengstorf said:
Over half the people are gonna choose the default. So, by default do the right thing and you immediately have improved whatever ecosystem/community you’re part of.
Default impact
Everyday, we all use a large number of tools to input and output content the way we need it, and all of those tools have a default way of working. The purpose of a default configuration is to be able to use the tool straight away for what it is made. And it works! But the trade off is often a bit less obvious. In fact, the end result is not always fully optimized for what you just need because it includes a lot more things you didn’t even know or expected. Of course, it’s easy for the creator of the tool to overlook the default and make it the most impressive it can be. But he must be aware that 50% of the people are going to use it by default without asking questions, even if it’s not fully optimized for their use case. Unfortunately, what we usually end up with is a less good experience for the end user. As Jason Lengstorf summarized it well, "By making the default to do just the right things, you immediately improve whatever ecosystem/community you’re part of."