I can actually build and design it. If the design isn't satisfactory, I can.... wait for it.. actually iterate on it.
In fact, if I had another engineer instead of a photoshop-monkey we could iterate twice as fast on either device or browser.
I can actually build and design it. If the design isn't satisfactory, I can.... wait for it.. actually iterate on it.
In fact, if I had another engineer instead of a photoshop-monkey we could iterate twice as fast on either device or browser.
So goddamn irritating.
Just learn to fucking write some html, js, and css or go back to print design... if it still exists.
I find that most UX people I work with rely way to heavily on A/B testing. A/B testing is a great tool to get to the perfect UI, but when you are A/B testing every feature because you have no idea what works and what doesn't it becomes a huge waste of my time.
Not sure what you are replying to, you were too vague.
The design department is managed separately from the Engineering department. I have no control over their tooling, hiring practices, or deliverables.