This story is unavailable.

Now you’re talking about two very different things. You said in the article, “You really should get off your lazy designer butt and learn to code already.”

And in this reply you’re saying we should understand the constraints of the technology for what we design. Those are two completely different things. I never said you shouldn’t be aware of the technical constraints of what you design for nor did I dispute that. And every designer should be aware of that.

But if we have to get off our lazy butt and learn how to code. Then by all means get off your lazy developer ass and learn UX methodologies, user research, user testing, how to do qualitative and quantitative research and persona creation, user interviewing, design methodologies and concepts, color theory, and learn how to use our design software… It goes both ways.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.