Well, the designer I work with has a approach, which I think would lend itself better to to a waterfall process than to any iterative approach of software development. In one sentence: Throwing high-fidelity photoshop mocks over the fence to a code monkey.
Having a lot of good ideas, but lacking programming skills, realizing which details cost more than they are worth is hard, especially when one doesn't bother to consult somebody who knows.
I recently contemplated leaving my job, because I'm a bit pissed about the dysfunctional communication, in which I feel to be basically disenfranchised from most meaningful aspects of the project.
I am so sorry this happens. Why aren't "sit, strategize, and coordinate" sessions normalized? I don't get how apps are successful with all the communication chaos happening behind the veil??
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.
Well, the designer I work with has a approach, which I think would lend itself better to to a waterfall process than to any iterative approach of software development. In one sentence: Throwing high-fidelity photoshop mocks over the fence to a code monkey.
Having a lot of good ideas, but lacking programming skills, realizing which details cost more than they are worth is hard, especially when one doesn't bother to consult somebody who knows.
I recently contemplated leaving my job, because I'm a bit pissed about the dysfunctional communication, in which I feel to be basically disenfranchised from most meaningful aspects of the project.
Oh my goodness I know what you mean!
I once worked with an incredibly talented designer who I could not communicate with to save my life. Makes me frustrated just thinking about it.
I am so sorry this happens. Why aren't "sit, strategize, and coordinate" sessions normalized? I don't get how apps are successful with all the communication chaos happening behind the veil??