Should I really bother learning to code?

This talk looks at what you can achieve with a little bit—not a lot!—of code. It's a brief look at how code in my design process has challenged my assumptions, improved accessibility, and helped me communicate with engineers. Beyond that, you'll see how to get real value of out coding skills without ever shipping production code or becoming a unicorn.

Web Directions Design 2018, Melbourne

Link: https://didoesdigital.com/project/code-for-designers/

Transcript

1. Should I really bother learning to code? by Diana MacDonald
2. Diana MacDonald @DiDoesDigital
9. Today
10. - Roles
11. - Roles - 3 ways to use code in design
12. - Roles - 3 ways to use code in design - Where to go next
13. Show of hands
14. Designers should…
22. Design roles
23. Design roles
24. This is a false dichotomy
25. Design roles
26. There are other unicorn skills
27. Design roles
28. There is an opportunity cost
29. Design roles
30. No one works alone
31. Design roles
32. Design roles
33. There is value in fluency
34. Design roles
35. Design roles
36. Coach people on your process
37. Design roles
39. 3 ways to use code in design
40. - 1. Designing in the browser
41. - 1. Designing in the browser - 2. Prototyping
42. - 1. Designing in the browser - 2. Prototyping - 3. Personal projects
43. 1. Designing in browser
44. document.designMode = 'on'
45. Designing in browser
46. Designing in browser
48. 2. Prototyping
49. Prototyping
50. Balance speed and fidelity
52. 3. Personal projects
53. Personal projects
54. Personal projects
55. Personal projects
56. Personal projects
57. Personal projects
58. Personal projects
59. Code what you can and fake everything else
60. Personal projects
61. aria-pressed
62. Personal projects
63. Immediate value
65. Where to start?
66. Where to start? - Don't fear the Internet
 by Jessica Hische & Russ Maschmeyer
 http://www.dontfeartheinternet.com/
67. Where to start? - Don't fear the Internet
 by Jessica Hische & Russ Maschmeyer
 http://www.dontfeartheinternet.com/ - The Elements of Typographic Style Applied to the Web
 by Richard Rutter
 http://webtypography.net/
68. Where to start? - Don't fear the Internet
 by Jessica Hische & Russ Maschmeyer
 http://www.dontfeartheinternet.com/ - The Elements of Typographic Style Applied to the Web
 by Richard Rutter
 http://webtypography.net/ - Designing in the browser
 by Kayce Basques, Google
 https://developers.google.com/web/tools/chrome- devtools/css/
69. Where to go next? - Next-level Prototyping for Web Design
 by Ling Zhou
 https://blog.usejournal.com/next-level-prototyping-for- web-design-2c9f54e51d57
70. Where to go next? - Next-level Prototyping for Web Design
 by Ling Zhou
 https://blog.usejournal.com/next-level-prototyping-for- web-design-2c9f54e51d57 - Passion Projects (Procrastiworking)
 by Jessica Hische
 https://youtu.be/RZbqJxQJ5LY
71. Where to go next? - Next-level Prototyping for Web Design
 by Ling Zhou
 https://blog.usejournal.com/next-level-prototyping-for- web-design-2c9f54e51d57 - Passion Projects (Procrastiworking)
 by Jessica Hische
 https://youtu.be/RZbqJxQJ5LY - Sketch plugins
 by Sagi Shrieber
 http://hackingui.com/sketch-design/how-to-create-a- sketch-plugin/
73. How much code? - “Design or code” is a false dichotomy - There’s opportunity cost—in teams & AI - There’s value in fluency—without coding - Design in the browser—with a little code - Balance speed and fidelity in prototypes —with as much as you need for realism - Code for immediate value and fake everything else DiDoesDigital.com
74. Code for designers https://DiDoesDigital.com
75. Should you really bother learning to code?
76. Questions? Diana MacDonald | @DiDoesDigital