Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@tosensei When the existing element is a looping image gallery, and the art director places a button above it, should I automatically know this is one button for the whole thing, or one button per image? Or should I be briefed about that kind of stuff?
-
@Inxentas but in that case, the director still doesn't need to check the backend ?
He wants a button above the gallery.
You ask, only one button or a different one for each ?
Or ask the director some mock-up from what he wants.
Is an art director/manager that makes designs for an existing website expected to brief the developer on how he wants his new designs to work? Or is the developer expected to innately understand what his functional desire is from the design itself?
My art director/manager claims that he shouldn't have to log into the backend to see how things relate to one another, and that his designs alone should imply what is intended.
When some design element overlaps an existing image gallery, am I expected to magically know whether this element is singular or partaining to the current image shown?
I want to know whether or not me getting mad at him for not telling me how he wants stuff to work is valid, and whether or not I should demand that he briefs me how his design relate to existing taxonomy.
Am I the bad guy?
question