2 ms·
Yeah, I have noticed a certain measure of developer autonomy has been lost, going to product management (who in-turn defer to design/UX). I don't think it's all
by spamizbad 5y ago
Yeah, I have noticed a certain measure of developer autonomy has been lost, going to product management (who in-turn defer to design/UX). I don't think it's all bad: I always appreciated expertise when it comes to esthetic and experiential parts of software.
What I do find frustrating is when they only concern themselves "happy path", and developers don't have the authority to fill in the gaps. It creates a waterfall-like experience where you are often stuck waiting to hear back from product/design to make a decision because they didn't consider a scenario where the user might submit a form with an incorrect field or some other seemingly obvious path.
Another bad practice is product people who assume screenshots or Figma files are technical requirements; not realizing these only give you clues as to how something will look, not how something will work, so flows and business logic go under-examined by product, which can lead to more "let's hold off on that, let me think about it" after telling you to start something ASAP.
- BreakfastB0b 5y agoI like to call this the human centipede of product development. This is why I only work at smaller companies where this is less of a problem.
- emptysea 5y agoDesign at my current place doesn't include loading and error states in their designs so we have to free hand those ourselves. IMHO, loading states and error states are one of the more important parts of the design since they'll be seen often (for loading) and when the product isn't working for a user (error states).