1. 17
  1.  

  2. 8

    I feel UI tends to be a Conway’s law-esque manifestation of its backend. Some program designs will make different UI approaches easier than others. I think constantly how AppKit vs. Win32 encourages certain patterns (i.e. focus vs. first responder, latter making implementing a universal Edit menu easier, etc.).

    Also: API design is UI design.

    1. 2

      There’s a lot of overlap here with clarity at the point of use: Design a function’s signature to maximize how easily understood its call sites will be, without the reader having to look at the declaration.

      1. 1

        Named arguments are great for this. Unfortunately, some languages still don’t have them in 2022.

        1. 2

          Swift goes one better and lets argument labels be optional, and distinct from parameter names, in order to let the call site read as fluently as possible. Array.insert(item, at: index) showcases both.

      2. 1

        “if it’s not in frame, it doesn’t exist” <character of Fritz Murnau in ‘Shadow of a Vampire’>

        if there’s no proper UI+UX, the feature does not exist. <me, here>

        1. 1

          This is interesting because I agree with that I see and do UI design every time I touch html. I am a software developer who does front end mostly, but I can immediately notice when something is a pixel off.

          1. 2

            In fact that’s what I expected the article to be about, but I liked the real content of it just as much.