Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Evaluating Technology

Evaluating Technology

We work with technology every day. And every day it seems like there's more and more technology to understand: graphic design tools, build tools, frameworks and libraries, not to mention new HTML, CSS and JavaScript features landing in browsers. How should we best choose which technologies to invest our time in? When we decide to weigh up the technology choices that confront us, what are the best criteria for doing that? This talk will help you evaluate tools and technologies in a way that best benefits the people who use the websites that we are designing and developing. Let's take a look at some of the hottest new web technologies like service workers and web components. Together we will dig beneath the hype to find out whether they will really change life on the web for the better.

Jeremy Keith

April 04, 2017

More Decks by Jeremy Keith

Other Decks in Technology


  1. WWW

  2. HTML 5 document conformance requirements should be designed so that

    web content can degrade gracefully in older or less capable user agents, even when making use of new elements, attributes, APIs and content models.” “ —HTML Design Principles
  3. Software, like all technologies, is inherently political. Code inevitably reflects

    the choices, biases and desires of its creators.” “ —Jamais Cascio
  4. amish The Amish have the undeserved reputation of being luddites,

    of people who refuse to employ new technology. The Amish are steadily adopting technology — at their pace. They are slow geeks.” “ —Kevin Kelly -ish
  5. How well does it work? How well does it fail?

    Who benefits? What are the assumptions?