Tagged: jim-nielsen

  • Saying “No” In an Age of Abundance - Jim Nielsen’s Blog

    It’s never been a good idea to ship everything you think of. Every addition accretes complexity and comes with a cognitive cost.

    Maybe we need to reframe the concept of scarcity from us, the makers of software, to them, the users of software. Their resources are what matter most:

    • Attention (too many features and they can’t all be used, or even tried)
    • Stability (too much frequent change is an impediment to learning a product)
    • Clarity (too many options creates confusion and paralysis)
    • Coherence (too many plots and subplots cannot tell a unified story)
  • The Case For Design Engineers, Pt. II - Jim Nielsen’s Blog

    Jim Nielsen makes the case for design engineers as professionals who do design work with code. He also emphasizes the limitations of traditional design tools, which often produce static images that don’t fully capture the dynamic nature of web interactions, and advocates for designing in the browser instead.

    You need someone who can do design work with code.

    That’s right: design work with code.

    Pixels of an interface from a GUI tool are a static representations of a dynamic form. It’s the difference between a picture of me and the living, breathing, moving me.

    Design engineers don’t just push pixels around in a GUI tool, they do it in a web browser — the medium of delivery — designing not just the visuals but the interactions that make sense for a living, breathing, moving interface.