• KillingTimeItself@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    1
    ·
    2 months ago

    actually, i would like to counter this. Developers often times put together shitty UIs that are hard to navigate (mostly because UI design is bad and we’ve been living with floating WMs for the past 30 years so nobody knows any fucking better for some godforsaken reason)

    But it’s no fault of the user for using a shitty interface if it was designed to be used in that manner, by the person who built it. This is why so many people like CLI, it’s impossible to fuck up. You can use it wrong as a user, but that’s because it has specific syntaxing. It’s designed to only be used in that one manner, where as most graphical applications are designed to be “generally applicable” for some reason, and then when a user uses it in a “generally applicable” manner, somehow that’s now the wrong way to use it?

  • Aceticon@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    2 months ago

    I’ve actually worked with a genuine UX/UI designer (not a mere Graphics Designer but their version of a Senior Developer-Designer/Technical-Architect).

    Lets just say most developers aren’t at all good at user interface design.

    I would even go as far as saying most Graphics Designers aren’t all that good at user interface design.

    Certain that explains a lot the shit user interface design out there, same as the “quality” of most common Frameworks and Libraries out there (such as from the likes of Google) can be explained by them not actually having people with real world Technical Architect level or even Senior Designer-Developer experience overseeing the design of Frameworks and Libraries for 3rd party use.