13
hitko
3y

Why can't managers understand that functionality changes and UX changes should be two separate epics? There's a huge fucking difference between composing an UI from existing components vs. having to figure out new components while at the same time paying attention to 12234234 new scenarios while at the same time duplicating existing components because existing portion of the app has to keep old UX.

And then they say bullshit like "we need solutions, not problems". Fuck you. Solution is to keep existing UX and focus on functionality, and do complex UX changes when functionality is well-defined and STABLE. But no, you fuckers won't listen even when the fucking lead dev tells you to.

Comments
  • 5
    "We need solutions, not problems" is so arrogant. Basically, it translates to: "I don’t want your arguments and logic. I don’t understand them anyway. Just make it possible. That is your only job."
  • 1
    @JustThat That manager doesn't have the time to make UX redesign and new functionality two separate epics, what makes you thing they have the time to listen to that long wordy sentence? 🤣
Add Comment