2 ms·

I think you are looking at this all wrong. Just like the designer would benefit from knowing how code works, don't you think the developer would benefit from k

I think you are looking at this all wrong. Just like the designer would benefit from knowing how code works, don't you think the developer would benefit from knowing how photoshop works? I find it kind of interesting that a developer would even feel a reluctance to understand one of the basic methods used to deliver to them what they need to develop. You are missing out on great opportunity to have an informed opinion, think about alternatives, find potential business ideas from something thats not optimal and in general just have a better and more productive relationship with designers. I at least realized that learning to code as a designer, even just a little bit, both taught me a great deal of how to build things for developers, help them solves problems that might require a different way to think about the technical issue of something and not do stuff that are completely retarded and impossible to do.

sbov 11y ago
Not particularly. The parallel to learning how code works is learning about UX/UI design, not necessarily photoshop. The parallel to learning photoshop would be asking you to learn vim/emacs/<insert IDE>, source control, etc.
- ThomPete 11y ago
  No they are actually benefits from learning photoshop because you understand what they are doing more technically. Adding a drop-shadow as an example. Or doing a gradient with specific ratio, angle and so on. You literally get access to the very parameters and their values you might have to use. It's not about learning how to use photoshop. It's learning how photoshop works, just like I learn code to understand how most code work. That doesn't mean I would call myself a developer who can code like a pro.