3 ms·
It's software that has never said no to a feature. So you get a pile of conflicting goals. Generally to resolve this you need to demand a high level of user c
by kristopolous 4y ago
It's software that has never said no to a feature.
So you get a pile of conflicting goals.
Generally to resolve this you need to demand a high level of user competency. Think emacs; does everything, things are mutually exclusive, competency is required.
The teams approach though is to try to satisfy this without requiring any competency. It's probably not doable