$30 off During Our Annual Pro Sale. View Details »

History of Art vs. Web Design vs CSS Development

Nils
June 05, 2022

History of Art vs. Web Design vs CSS Development

Communication between designers and developers can sometimes be a bit difficult. It's probably something all of us have experienced at one time or another. But in the same way, communication between two developers or two designers can also be challenging. To quote Chris Coyer: "Two front-end developers are sitting at a bar. They have nothing to talk about."

In this talk, I'll show you that these problems didn't just happen with the invention of the Internet. Let me take you on a bit of a trip into the history of art. Using the example of two very different but outstanding artists in their field, I will show how we can have more understanding and benefit from each other. Oh, and there will be a bit of CSS in there, as I will show you that it helps to judge a layout, not by pixels and color values, but to see it as a work of art that you can analyze.

Nils

June 05, 2022
Tweet

More Decks by Nils

Other Decks in Programming

Transcript

  1. NILS BINDER @supremebeing09 www.ichimnetz.com 👨💻

  2. Jackson 
 Pollock 1912 - 1956

  3. Jackson 
 Pollock 1912 - 1956

  4. None
  5. None
  6. None
  7. Filippo 
 Brunelleschi 1377 - 1446

  8. Filippo 
 Brunelleschi 1377 - 1446

  9. Filippo 
 Brunelleschi 1377 - 1446

  10. Filippo 
 Brunelleschi 1377 - 1446

  11. None
  12. None
  13. None
  14. None
  15. None
  16. None
  17. None
  18. None
  19. None
  20. 🤷

  21. Emotions Math

  22. Emotions Math

  23. Emotions Math

  24. Emotions Math

  25. Emotions Math

  26. Emotions Math

  27. Emotions Math

  28. Emotions Math

  29. Emotions Math

  30. Emotions Math

  31. Emotions Math

  32. Emotions Math

  33. Emotions Math

  34. Emotions Math

  35. Emotions Math

  36. Emotions Math

  37. Emotions Math

  38. None
  39. None
  40. None
  41. None
  42. None
  43. None
  44. None
  45. None
  46. None
  47. WE NEED TO TALK!

  48. WE NEED TO TALK! This looks awesome!

  49. None
  50. None
  51. None
  52. None
  53. None
  54. None
  55. None
  56. None
  57. None
  58. None
  59. None
  60. None
  61. None
  62. None
  63. None
  64. WE NEED TO TALK!

  65. WE NEED TO TALK! You don’t understand the medium!

  66. WE NEED TO TALK! You don’t understand the medium! Here’s

    a Figma template with Tailwind components.
  67. WE NEED TO TALK! You don’t understand the medium! Here’s

    a Figma template with Tailwind components. Developer* experience is much better, if you stick to this… * read: “My”
  68. WE NEED TO TALK! 🤯☠👿 You don’t understand the medium!

    Here’s a Figma template with Tailwind components. Developer* experience is much better, if you stick to this… * read: “My”
  69. WE NEED TO TALK! 🤯☠👿 You don’t understand the medium!

    Here’s a Figma template with Tailwind components. Developer* experience is much better, if you stick to this… * read: “My” 🥺😢
  70. None
  71. None
  72. The Great Divide

  73. The Great Divide Frontend Developer (Full Stack?)

  74. The Great Divide Front of the Frontend Frontend Developer (Full

    Stack?)
  75. The Great Divide Front of the Frontend Back of the

    Frontend Frontend Developer (Full Stack?)
  76. The Great Divide Front of the Frontend Back of the

    Frontend Frontend Developer (Full Stack?) Full Stack Designer
  77. The Great Divide Front of the Frontend Back of the

    Frontend Frontend Developer (Full Stack?) Should designers learn how to code? Full Stack Designer
  78. The Great Divide Front of the Frontend Back of the

    Frontend Frontend Developer (Full Stack?) Should designers learn how to code? Full Stack Designer
  79. None
  80. 🧚

  81. 🧚

  82. 🧚

  83. 🧚 Not a designer not yet a developer.

  84. 🧚 Not a designer not yet a developer.

  85. 🧚 Not a designer not yet a developer.

  86. @supremebeing09 www.ichimnetz.com 👨💻 Thank you