In Part 1, I argued that the need for a designer to know how to code what they create is based on the designer’s chosen professional path and the overall size of the project they are working on. This has resulted in a variety of great comments, both here on the blog and on the twitterverse. If you haven’t had a chance to read it, please check it out.
Having dealt with that side of the argument, I want to provide some thoughts on why it’s important for designers to know about code, understand what a development lifecycle looks like, and why knowing these two aspects of digital creation is vital to being a well rounded designer. As I mentioned in the previous post, my educational background is in Computer Science. There are very few aspects of the coursework that I use in my everyday work, but what I do use is the concepts and domain knowledge that came along with it. Because of the curriculum I have a fundamental understanding of Object Oriented Programming, System Architecture, and the theory behind programming languages and their structure. Continue reading →