Any piece of software has a set of configurations, toggles, and switches that make it come alive.
The configuration is what makes the software work for your customer and makes it “their own, unique copy”.
Four things a configuration should always have;
- A place to go and make the change, not forcing the customer to jump here, there, and everywhere.
- Settings that do what they are supposed to do.
- Be simple in their implementation, if it can be explained simply by the developer, the end user will never be able to consume it.
- Work.
The worst thing is when a configuration is exposed, people get excited, and doesn’t work – it always has to work.
And always keep your configurations simple, you want people to use them, not to be confused by them.
