Things designers and developers should know (WDS18)
•
0 likes•2,329 views
My talk from Web Directions Summit 2018, about things designers and developers should know about each other. If you've ever asked or been asked "should designers code", this talk is for you :)
Report
Share
Things designers and developers should know (WDS18)
- 1. Things Designers and Developers Should KnowThings Designers and Developers Should Know Ben Buchanan @200okpublic, designops.expert
- 6. Design Dev Creativity, problem solving ⬌ Creativity, problem solving Design critique ⬌ Code review Sketching, discovery ⬌ Spikes, PoC Oh it's easy, my nephew designed a website! ⬌ Oh it's easy, my nephew built a website!
- 7. Knowing to understand empathy and respect Knowing to do execution
- 8. 初心
- 9. Golden rule of collaborative knowledge Learn about others as you'd have them learn about you.
- 10. Corollary Be a guide for others to find the joy you found.
- 11. The inevitable question...The inevitable question... Should designers code? Should developers design?
- 12. It's nonsense!It's nonsense! Design and development are interlinked.
- 13. Would we ask...?Would we ask...? Should we be good at our jobs? Should we build empathy with coworkers?
- 14. To what level should you code/design?To what level should you code/design? None at all Understand but don't do Do to non-production standard Do to production standard
- 15. Levels of knowledgeLevels of knowledge None at all part of the job Understand but don't do Do to non-production standard Do to production standard
- 16. Levels of knowledgeLevels of knowledge None at all part of the job Understand but don't do Do to non-production standard Do to production standard career change
- 18. Data!Data! Surveyed 176 people on design and development collaboration.
- 19. ResultsResults How much code should designers know or do? 2.8%2.8% 52.3%52.3% 42%42% 2.8%2.8% None at all Know how code works, but not write any code Be able to write code, but not to production standard Be able to code to production level
- 20. ResultsResults How much design should developers know or do? 1.1%1.1% 47.7%47.7% 48.3%48.3% 2.8%2.8% None at all Know how design works, but don't do any design Be able to do some design, but not to production standard Be able to design to production level
- 21. LevelsLevels (now with data for extra shine!)(now with data for extra shine!) None at all Understand but don't do Do to non-production standard Do to production standard
- 22. What should you learn, then?What should you learn, then? Roles and process 'The basics' History and schools of the craft
- 23. How important is it to understand roles, process and principles? 1 (not important) 2 3 4 (critical)
- 24. ResultsResults How important is it to understand history and schools? 1 (not important) 2 3 4 (critical)
- 25. We are part of historyWe are part of history
- 27. SchoolsSchools Design Movements Programming Paradigms Minimalism, Bauhaus, Modernism, Postmodernism Procedural, Literate, Object Oriented, Functional
- 28. Back to roles, process, basics 1 (not important) 2 3 4 (critical)
- 29. Roles & ProcessRoles & Process
- 30. Design RolesDesign Roles Research does it solve the problem? UX how it feels and flows Interaction design how it behaves Visual design how it looks
- 33. Development RolesDevelopment Roles Frontend/UI code for rendering things Backend/Application code to apply business rules Data code to supply content DevOps code to deploy the other code QA code to make sure the other code is still working
- 34. Would you believe developers haven't produced lovely infographics about their roles?
- 35. ProcessProcess While every team differs, there are common shapes.
- 40. The Basics™ for designersThe Basics™ for designers The medium HTML, CSS, JS Where design breaks code accessibility, performance Working together versioning
- 41. HTMLHTML
- 50. Cloud systems need versions tooCloud systems need versions too
- 51. Then...Then... Keep learning code! CLI basics Data structures AI concepts
- 52. The Basics™ for developersThe Basics™ for developers Design is not random fundamentals Design language fundamentals Design as problem solving research, Design Thinking
- 57. C.R.A.P.C.R.A.P.
- 59. Voice & ToneVoice & Tone
- 61. Golden rule of collaborative knowledge Learn about others as you'd have them learn about you. Corollary Be a guide for others to find the joy you found.
- 62. Lead by understanding Lead by doing
- 63. Thank you.Thank you. Thanks to all those who shared the joy of design with me.
- 64. LinksLinks Learn to Code HTML & CSS Chris Coyier: Hey designers, if you only know one thing about JavaScript, this is what I would recommend WAI: Accessibility for designers Webaim: Accessibility for designers Paciello Group CCA Yesenia Perez-Cruz: Design decisions through the lens of performance Brad Frost: performance budget builder https://www.performancebudget.io/
- 65. LinksLinks Understanding colour theory Canva: learn design The illusion of life (animation) Voice and Tone Voice and Tone guides Spectrum of design roles
- 66. Image creditsImage credits Created by Adrien Coquet from the Noun Project Created by Lakshisha from the Noun Project
- 67. Created by BomSymbols from the Noun Project Created by Aly Dodds from the Noun Project Created by B Barrett from the Noun Project
- 68. Created by Nikita Kozin from the Noun Project Created by Grégory Montigny from the Noun Project Created by Trevor Dsouza from the Noun Project
- 69. Created by Maxim Kulikov from the Noun Project Created by GD Creativ from the Noun Project
- 70. Image creditsImage credits https://fstoppers.com/education/how-color-theory-improves-your-photography-and- retouching-215697 https://thelogocompany.net/blog/infographics/psychology-color-logo-design/ https://material.io/design/typography/understanding-typography.html https://www.crazyegg.com/blog/psychology-of-fonts-infographic/ https://paper-leaf.com/blog/2012/10/principles-of-design-quick-reference-poster/ Squiggle from https://thedesignsquiggle.com/ Some I could not find a definitive source to credit.