How to Design Software Good

Re:How to Design Software Good by mort96 on Saturday November 10, 2018 @10:03AM (#18421559)

You're assuming all products are apps or websites or something with a GUI. A product could be a library, or an OS kernel, or a web API, or any number of things, where knowledge of how to make a GUI with a good UX is completely irrelevant; or the programmer could be working on a very technical part; the engineers working on, say, Safari to optimize the javascript engine's performance similarly don't need any knowledge of what good UX means for a graphical interface.

Apple and Google shouldn't fire their best compiler/JIT writers just because they write lousy GUIs.

[ Parent | on HN ]

Re:How to Design Software Good by Volt on Saturday November 10, 2018 @06:43PM (#18424139)

There's a UX for those things too. The users would be the consumers of the API.

[ Parent | on HN ]

Re:How to Design Software Good by mort96 on Monday November 12, 2018 @05:32AM (#18431722)

Obviously, but the kind of UX discussed here is obviously that of graphical applications; nobody would say that a web API's or a compiler's UX is a "stuttering mess".

[ Parent | on HN ]

Re:How to Design Software Good by quakenul on Wednesday November 14, 2018 @10:35AM (#18450602)

Basically everything computer that interfaces with humans is graphical. That doesn't mean it's in the designers domain to fix.

A designer is not responsible for making sure that the implementation of their design runs at stutter free at 60fps in a browser -- that is an engineers job. If the engineer who implements such a design is insensitive to these things and needs convincing that it's important to not have the implementation not stutter, jerk or jank you are never gonna get good results.

[ Parent | on HN ]