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

Evaluating Technology

Jeremy Keith
April 04, 2017
Technology
4
180

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
Tweet

More Decks by Jeremy Keith

See All by Jeremy Keith
Of Time And The Web
adactio
0
50
“Web3” and “AI”
adactio
0
42
In And Out Of Style
adactio
0
12
The State Of The Web
adactio
0
28
Sci-fi And Me
adactio
0
34
Design Principles For The Web
adactio
0
33
Building
adactio
0
23
The Layers Of The Web
adactio
0
260
Taking Back The Web
adactio
1
680

Other Decks in Technology

See All in Technology
Taming you application's environments
salaboy
0
180
複雑なState管理からの脱却
sansantech
PRO
1
140
誰も全体を知らない ～ ロールの垣根を超えて引き上げる開発生産性 / Boosting Development Productivity Across Roles
kakehashi
1
220
Incident Response Practices: Waroom's Features and Future Challenges
rrreeeyyy
0
160
開発生産性を上げながらビジネスも30倍成長させてきたチームの姿
kamina_zzz
2
1.7k
B2B SaaS × AI機能開発 〜テナント分離のパターン解説〜 / B2B SaaS x AI function development - Explanation of tenant separation pattern
oztick139
2
220
元旅行会社の情シス部員が教えるおすすめなre:Inventへの行き方 / What is the most efficient way to re:Invent
naospon
2
330
個人でもIAM Identity Centerを使おう!(アクセス管理編)
ryder472
3
180
信頼性に挑む中で拡張できる・得られる１人のスキルセットとは？
ken5scal
2
530
100 名超が参加した日経グループ横断の競技型 AWS 学習イベント「Nikkei Group AWS GameDay」の紹介/mediajaws202411
nikkei_engineer_recruiting
1
170
障害対応指揮の意思決定と情報共有における価値観 / Waroom Meetup #2
arthur1
5
470
TypeScript、上達の瞬間
sadnessojisan
46
13k

Featured

See All Featured
Building Applications with DynamoDB
mza
90
6.1k
Rebuilding a faster, lazier Slack
samanthasiow
79
8.7k
Bootstrapping a Software Product
garrettdimon
PRO
305
110k
"I'm Feeling Lucky" - Building Great Search Experiences for Today's Users (#IAC19)
danielanewman
226
22k
Java REST API Framework Comparison - PWX 2021
mraible
PRO
28
8.2k
XXLCSS - How to scale CSS and keep your sanity
sugarenia
246
1.3M
4 Signs Your Business is Dying
shpigford
180
21k
Adopting Sorbet at Scale
ufuk
73
9.1k
Building Adaptive Systems
keathley
38
2.3k
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
rmw
31
2.7k
The Illustrated Children's Guide to Kubernetes
chrisshort
48
48k
[Rails World 2023 - Day 1 Closing Keynote] - The Magic of Rails
eileencodes
33
1.9k

Transcript

  1. EVALUATING TECHNOLOGY

  2. None

  3. A C G T

  4. specialisation ubiquity cooperation

  5. None

  6. We shape our tools and thereafter our tools shape us.”

    “ —John Culkin

  7. specialisation ubiquity cooperation

  8. None
  9. None

  10. Chindōgu

  11. Chindōgu

  12. Chindōgu

  13. Chindōgu

  14. Chindōgu

  15. Chindōgu

  16. Chindōgu

  17. hardware software human

  18. None
  19. None

  20. hardware software human

  21. WWW

  22. computers internet electricity WWW industrialisation

  23. HTTP WWW URLs HTML

  24. None

  25. Humans are allergic to change.” “ —Grace Hopper

  26. HTTP WWW URLs HTML SGML DNS TCP/IP

  27. SGML <body> <title> <p> <h1> <h2> <h3> <ol> <li> <ul>

    <dl> <dt> <dd>

  28. HTML <article> <section> <main> <aside> <figure> <footer> <header>

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

  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

  31. principles.adactio.com

  32. principles goals patterns

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

  34. How well does it work?

  35. How well does it fail?

  36. None
  37. None
  38. None

  39. service workers

  40. None

  41. How well does it work?

  42. None

  43. How well does it fail?

  44. web components shadow DOM custom elements

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

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

  47. <mega-menu> <link rel="import" href="mega-menu.html"> HTML CSS JS

  48. How well does it work?

  49. None

  50. How well does it fail?

  51. <image-gallery> <img src="…" alt="…"> <img src="…" alt="…"> <img src="…" alt="…">

    </image-gallery>

  52. <image-gallery> </image-gallery>

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

  54. service workers web components

  55. ajax responsive web design progressive web app the extensible web

  56. service worker manifest file progressive web app HTTPS + +

    =
  57. None
  58. None
  59. None

  60. Who benefits?

  61. developers users

  62. sass less git gulp npm jQuery bootstrap angular react ember

  63. What are the assumptions?

  64. Software, like all technologies, is inherently political. Code inevitably reflects

    the choices, biases and desires of its creators.” “ —Jamais Cascio
  65. None

  66. The street finds its own uses for things.” “ —William

    Gibson Burning Chrome
  67. None

  68. Technology is neither good nor bad; nor is it neutral.”

    “ —Melvin Kranzberg
  69. None
  70. None

  71. What Technology Wants The Inevitable

  72. 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
  73. None

  74. How well does it work? How well does it fail?

    Who benefits? What are the assumptions?
  75. None

  76. Thank you