Hello, my name is: Amy

Design vs. Code

There was a time in my life where I loved to design. It was always something I enjoyed and even considered it one of my better skills, or ways to express creativity.

As I'm learning to code though, I'm finding myself to be at a loss for design, or at least that I've found there to be a very clear line in the sand between if I like print design and if I like web design.

With web design, I simply haven't found a way to turn off my programmers brain to just design how I think something should look or feel.

Even when I'm working solely in Photoshop, or even on paper, my Design brain is still crippled by my Programmer brain going the next step and visualizing how to solve the problem. It's almost as if there are too many options, and I can't stop visualizing them all to pull the trigger on one.

I do agree with the idea that web designers (and project managers!) should learn aspects of how code works. There is immense value in understanding how web pages/apps are put together that will result in a better product and save a lot of time. But this kind of learning should come from conversations, not classrooms. At least in my experience, going too far down the coding rabbit hole might block a designer from creating.

Of course, it's entirely possible that I've never devoted the energy to formally learning how to design for the web. For now, though, I'm OK with using my creativity for programming problems.