Archive of: webdevelopment

  • Performance matters

    Caring about performance isn’t only a business goal […]. It’s about fundamental empathy and putting the best interest of the users first.

    As technologists, it’s our responsibility not to hijack attention and time people could be happily spending elsewhere. Our objective is to build tools that are conscious of time and human focus.

    The State of the Web by Karolina Szczur

  • Debating Progressive Enhancement

    Don’t make up your mind about Progressive Enhancement by reading reductive blog posts or presentations that gloss over or outright ignore the details and nuances of actual web work. Read up on the individual tactics used. Judge them in terms of how effective they might be at solving the problems you are tackling. Every tactic strikes a different balance. Unless you plan on only solving one kind of problem, again and again, throughout your career, you owe it to yourself to study the tactics that lie outside your comfort zone.

    Baldur Bjarnason

  • Atomic design

    Atomic design is a mental model that enables designers to create both the parts and the whole of a UI design system concurrently. It is not a rigid system that dictates a particular process, but rather a framework for building design systems efficiently and consistently.

    Vitaly Friedman - Taking Pattern Libraries To The Next Level

  • On performance

    There needs to be a cultural change in how we approach building for the web. Yes, some of the tools we choose are part of the problem, but the bigger problem is that performance still isn’t being recognised as the most important factor in how people feel about websites (and by extension, the web). This isn’t just a developer issue. It’s a design issue. It’s a UX issue. It’s a business issue. Performance is everybody’s collective responsibility.

    Jeremy Keith

  • Building APIs

    One of the quickest ways to kill your API is to define the API in your code, instead of coding to its definition

    Mike Stowe