3 ms·
I don't think infinite customizeability is a problem. Poor default configurations are the problem when you build in the ability to customize. The idea is that
by kelnos 2mo ago
I don't think infinite customizeability is a problem. Poor default configurations are the problem when you build in the ability to customize.
The idea is that the user should be able to be productive more or less immediately after installing the software, and then incrementally customize it as they discover they have different needs than the defaults give them.
A lot of developers/companies forget the first part, and ship something that requires a team of consultants six months to set up before anyone can do anything useful with it. Of course no one wants that. (Well, except for the highly-paid consultants.)
- 3eb7988a1663 2mo agoWhat mythical software is this? The only infinitely customizable software I can think of is emacs, and that takes an enormous amount of effort to become proficient.
- Scarblac 2mo agoSpreadsheet software, like Excel.
- ssdspoimdsjvv 2mo agoany serious enterprise software that attempts to fit every company's workflow (rather than forcing the company to follow theirs)
- Animats 2mo ago> I don't think infinite customizeability is a problem. Poor default configurations are the problem when you build in the ability to customize. This is a classic IDE problem. The IDE has a preferred directory layout it wants, and some other build tool you're using has a different directory layout.
- _carbyau_ 2mo agoSensible defaults and/or a basic wizard to choose templated configs or assist with customising the few things that have to be.