3 ms·
> You could have a patched together backend that "just > works" and has a great UI that customers love, but how is > that "quality" software? The software e
by falsedan 11y ago
> You could have a patched together backend that "just
> works" and has a great UI that customers love, but how is
> that "quality" software? The software end of it is clunky
> and patched.
>
> On the other hand, you can have completely documented,
> easy to read, well thought-out code that has a terrible
> UI that no one will bother using. I guess you can say the
> software is "quality," but it doesn't matter.
We've been discussing what quality for our team at work, and one of the key outcomes has been recognising 'Perceived Quality' & 'Actual Quality' as distinct concepts. The main difference is, to a user, they are the same and can't be distinguished--until something goes wrong.