This weekend I read four articles, three of which discussed the surprisingly controversial topic of whether designers should code. The first article I read (http://andyrutledge.com/web-design-is-product-design.php by Andy Rutledge) argues that designers need to know how to code their own websites as the actual website--not the picture--is their product. In response David Casali (http://intenseminimalism.com/2011/designers-shouldnt-code-the-digital-duo/) blatantly calls "bullshit" & explains the phenomena of Multiple Intelligences, the priority to study psychology, & the benefits of teamwork in web design. Finally, Usability Post (http://www.usabilitypost.com/2011/09/01/should-web-designers-code/) reviews the two sides of this argue, claims they both can be right & provides insight to the difference between graphic and web designers, the differences between codes, and just what the benefits can be to knowing code.
The last of the four articles (http://www.bernzilla.com/item.php?id=416) was a brief review of the differences of tags and classes in HTML & CSS coding, the premise being that IDs are specific & unique, being used only once per page, while classes literally classify elements into groups & may be used numerously through a code.
No comments:
Post a Comment