Comment by mohamedkoubaa

18 hours ago

Principal engineer balks at bad UX when the PM should know better (it's their job)

2023: Ah well I guess we can't do it

2025: you're fired. Hey kid we hired two weeks ago, implement bad idea please

17 comments

mohamedkoubaa

Reply
palata  18 hours ago

To be fair, it was already done by bad managers long before.

  • wmeredith  1 hour ago

    This is what I sees getting missed in a lot of LLM conversations. They're amplifiers. Full stop. If you have good practices they supercharge them, if you had bad practices, same thing.

  • hirako2000  16 hours ago

    I saw a trend of UX/UI designers coming with practice which I knew better were wrong. But they insisted. E.g hijack brosser native controls.

    Will never know whether they passed along some manager/PM commandements or were just incompetent.

    • Terr_  10 hours ago

      > But they insisted. E.g hijack brosser native controls.

      [Rant-Example] The goshdarn ticketing-system hijacks alt-f, so that instead of opening the File menu of my browser, and instead toggles the favorite-status of whatever ticket I happen to be viewing.

      3 replies →

    • themanualstates  11 hours ago

      To be fair, the native browser controls have had too many quirks and features fox UX/UI consistency.

      Corporate needs their Brand™ look precisely as specified in their expensive Style Guide. IBM wouldn't want the Google vibes of Android Material Design TextFields, I imagine.

      Scratch beneath the visuals, and starker technical differences appear.

      Safari on iOS (used to?) has a 350ms debounce delay on every tap / click, in case you want to do a multitouch gesture.

      JavaScript (Frameworks) were the only way this arbitrary delay to user input could be reduced before 2015, when Apple finally released a native API for this.

      https://webkit.org/blog/5610/more-responsive-tapping-on-ios/

      1 reply →