Description

Should designers code?

Subscribe: ITUNES | ANDROID | STITCHER | RSS FEED

Music and links from this episode

1. Who Is Responsible for Design - Creative Review Article
2. Eutrophic by Mystery Mammal
3. Cart before the horse by Myriadar
4. Where There Is No darkness by Nihilore

Line-by-line notes

1. There's several debates that are forever recurring in the design and tech worlds
2. Is design art?
3. Or is art design?
4. Should a designer do multiple things?
5. And the hottest topic and that comes around every week
6. Should designers code?
7. I probably going to get a bit offensive to designers in this episode.
8. This is AADA, and I’m Craig Burgess
9. MUSIC
10. Over the years I've lost count of how many times I've had this argument
11. But I'm going to go at it again, becaause I like causing controversy
12. And amazingly, I've not discussed it on this podcast before
13. Let me lay out my stance straight away
14. I have a dim view of designers who choose not to bother learning to code
15. It's not just about designers though
16. I have a dim view of anybody who actively chooses to stop learning things
17. When it comes to designers, they actively choose not to bother learning how to code, or any of the technical side
18. I'll try learning anything, because I love learning things
19. And we should all love learning things, because it's the only way to grow as human beings, not just at our craft
20. So I find it fascinating and maddening when I see anybody putting up a barrier to themselves and saying
21. "No, I don't want to learn that and I don't want to know anymore about that"
22. Knowing more about something makes you design it better, that is just a fact
23. Not even technical stuff, the more you know about anything the better you'll design it
24. So when it comes to websites, and especially now with responsive websites and there being so much changing so quickly
25. You have to know how to build websites, to a point
26. HTML and CSS isn't difficult to learn for anybody
27. And I can't see a logical reason why somebody wouldn't want to learn it, or can't learn it
28. The reasons for a designer designing websites to learn it are nothing but positive
29. It helps you understand websites more
30. It helps you design and make better websites
31. And it makes you a better designer
32. Why on earth would you not want those things?
33. Who could argue against those points?
34. We get too bogged down with titles 
35. And too caught up with labels
36. I'm a designer, therefore I can't be anything else
37. I'm a developer, so that means the design is left to somebody else
38. These titles aren't...