I don't remember where I read this, but I'm pretty certain it was on dev.to... can't seem to remember the title though -- darn! -- maybe it was on Twitter?
Anyway, there was a scenario where a dev and a designer were discussing. The designer was discussing how they often felt disconnected with their engineers, mostly because there expectations were mismatched. And then either the designer had reached out or one of the engineers offered to teach some basics of programming -- the point of the lesson was to help the designer understand some technical requirements essentially.
I think it's important for both sides to understand where each other are coming from. Just like Peter said it's important to offer opportunities for devs to weigh in on creative decisions, I think it can also be useful for designers to see what sort of technical constraints (or possibilities) are in place.
This also reminds of one recent anecdote we had. We as a team had a group session where Ben was demo'ing the article sidebar, and we sat around as he asked for our input. It was a simple "oh I like this," "that looks good," "what if we do that?" back and forth conversation, and I think everyone came out of it feeling pretty solid about the feature and the design going forward. it was great to hear everyone's ideas, and it was an opportunity to include the whole team in the design + development process.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I don't remember where I read this, but I'm pretty certain it was on dev.to... can't seem to remember the title though -- darn! -- maybe it was on Twitter?
Anyway, there was a scenario where a dev and a designer were discussing. The designer was discussing how they often felt disconnected with their engineers, mostly because there expectations were mismatched. And then either the designer had reached out or one of the engineers offered to teach some basics of programming -- the point of the lesson was to help the designer understand some technical requirements essentially.
I think it's important for both sides to understand where each other are coming from. Just like Peter said it's important to offer opportunities for devs to weigh in on creative decisions, I think it can also be useful for designers to see what sort of technical constraints (or possibilities) are in place.
This also reminds of one recent anecdote we had. We as a team had a group session where Ben was demo'ing the article sidebar, and we sat around as he asked for our input. It was a simple "oh I like this," "that looks good," "what if we do that?" back and forth conversation, and I think everyone came out of it feeling pretty solid about the feature and the design going forward. it was great to hear everyone's ideas, and it was an opportunity to include the whole team in the design + development process.