Sometimes tools are too flexible. Configuration options that only exist to support every single possible use case. For example, being able to customize the folder name for a tests. Many small customizations that compound in an unnecessarily complex tool.
-
-
Tell me more.
-
Depends on the extremes that you want to debate. I don't think every single config option is unnecessary but should be weighted against the ability for the tool to innovate and the actual usefulness. Some options can be predicted to actively prevent certain architectural changes.
- 3 more replies
New conversation -
-
-
Sometimes also to help people migrate from other tools
-
Conforming to standard conventions should be the first start of a migration
End of conversation
New conversation -
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
"You can please some of the people some of the time..." "Focusing is about saying no..."
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I think that's basically right, but you can get away with allowing more configuration along these lines through layering: if people want to change something, they go to the more flexible layer underneath.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
he/him 