Evaluating Technology

A presentation at Beyond Tellerrand in May 2017 in Düsseldorf, Germany by Jeremy Keith

Slide 1

Slide 1

EVALUATING TECHNOLOGY

Slide 2

Slide 2

Slide 3

Slide 3

A C G T

Slide 4

Slide 4

specialisation ubiquity cooperation

Slide 5

Slide 5

Slide 6

Slide 6

We shape our tools and therea ! er our tools shape us.” “ —John Culkin

Slide 7

Slide 7

specialisation ubiquity cooperation

Slide 8

Slide 8

Slide 9

Slide 9

Slide 10

Slide 10

Chind ō gu

Slide 11

Slide 11

Chind ō gu

Slide 12

Slide 12

Chind ō gu

Slide 13

Slide 13

Chind ō gu

Slide 14

Slide 14

Chind ō gu

Slide 15

Slide 15

Chind ō gu

Slide 16

Slide 16

Chind ō gu

Slide 17

Slide 17

hardware software human

Slide 18

Slide 18

Slide 19

Slide 19

Slide 20

Slide 20

hardware software human

Slide 21

Slide 21

WWW

Slide 22

Slide 22

computers internet electricity WWW industrialisation

Slide 23

Slide 23

HTTP WWW URLs HTML

Slide 24

Slide 24

Slide 25

Slide 25

Humans are allergic to change. ” “ —Grace Hopper

Slide 26

Slide 26

HTTP WWW URLs HTML SGML DNS TCP/IP

Slide 27

Slide 27

SGML

<body> <title> <p> <h1> <h2> <h3> <ol> <li> <ul> <dl> <dt> <dd>

Slide 28

Slide 28

HTML

<article> <section> <main> <aside> <figure> <footer> <header>

Slide 29

Slide 29

HTML <canvas> <video> <datalist> <audio> <picture>

Slide 30

Slide 30

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

Slide 31

Slide 31

principles.adactio.com

Slide 32

Slide 32

principles goals patterns

Slide 33

Slide 33

HTML <canvas> <video> <datalist> <audio> <picture>

Slide 34

Slide 34

How well does it work?

Slide 35

Slide 35

How well does it fail?

Slide 36

Slide 36

Slide 37

Slide 37

Slide 38

Slide 38

Slide 39

Slide 39

service workers

Slide 40

Slide 40

Slide 41

Slide 41

How well does it work?

Slide 42

Slide 42

Slide 43

Slide 43

How well does it fail?

Slide 44

Slide 44

web components shadow DOM custom elements

Slide 45

Slide 45

HTML <canvas> <video> <datalist> <audio> <picture>

Slide 46

Slide 46

<mega-menu> <slippy-map> <off-canvas> <image-gallery> <modal-lightbox>

Slide 47

Slide 47

How well does it work?

Slide 48

Slide 48

Slide 49

Slide 49

How well does it fail?

Slide 50

Slide 50

<image-gallery> <img src="…" alt="…"> <img src="…" alt="…"> <img src="…" alt="…"> </image-gallery>

Slide 51

Slide 51

<image-gallery> </image-gallery>

Slide 52

Slide 52

<body> <shop-app> </shop-app> <script>…</script> </body> shop.polymer-project.org

Slide 53

Slide 53

service workers web components

Slide 54

Slide 54

ajax responsive web design progressive web app the extensible web

Slide 55

Slide 55

service worker manifest file progressive web app HTTPS + +

Slide 56

Slide 56

Slide 57

Slide 57

Slide 58

Slide 58

Slide 59

Slide 59

Who benefits?

Slide 60

Slide 60

developers users

Slide 61

Slide 61

sass less git gulp npm jQuery bootstrap angular react ember

Slide 62

Slide 62

What are the assumptions?

Slide 63

Slide 63

So ! ware, like all technologies, is inherently political. Code ine v itably reflects the choices, biases and desires of its creators.” “ —Jamais Cascio

Slide 64

Slide 64

Slide 65

Slide 65

$ e street finds its own uses for things.” “ —William Gibson Burning Chrome

Slide 66

Slide 66

Slide 67

Slide 67

Technolog y is neither good nor bad; nor is it neutral.” “ —Melvin Kranzberg

Slide 68

Slide 68

Slide 69

Slide 69

Slide 70

Slide 70

What Technolog y Wants

e Inevitable

Slide 71

Slide 71

amish $ e Amish have the undeserved reputation of being luddites, of people who refuse to employ new technolog y. $ e Amish are steadily adopting technolog y — at their pace. $ ey are slow geeks.” “ —Kevin Kelly -ish

Slide 72

Slide 72

Slide 73

Slide 73

How well does it work? How well does it fail? Who benefits? What are the assumptions?

Slide 74

Slide 74

Slide 75

Slide 75

Thank you