How dare I polish and remove kludges from previous releases. 😆

Also, none of those kludges would have even been necessary if the project scope was properly defined from the start and the project manager didn’t let the users keep trickling in new requirements without also extending the deadline.

So yeah, how dare I go back and implement something the way it should have been done the first time?

  • Redkey@programming.dev
    1·
    3 months ago

    Yeah, I’m sure that almost all of us have felt this way at one time or another. But the thing is, every team behind every moronic, bone-headed interface “update” that you’ve ever hated also sees themselves in the programmer’s position in this meme.

    • Admiral Patrick@dubvee.orgOPEnglish
      1·
      3 months ago

      Oh for sure.

      The meme is just a very exaggerated tale of moving a tacked-on, added-at-the-absolute-last second button from the previous release into the action menu where it should have gone originally. It’s an in-house application, and the people that complained are also the type that will bold an entire page because “it’s important”. lol

  • kamstrup@programming.dev
    1·
    2 months ago

    There is a dangerously large population of devs and managers that look at themselves, unironically, as the gigachads pumping out ui “upgrades”

    Many of these fail to realize how disruptive it is. UI change is like API breakage for the brain.

    I have lost track of how many times I’ve tried to help an elderly family member with an app after some pointless, trivial, ui change. Only ending with them entirely giving up on using the app after the “upgrade” because the cognitive overhead of the change is beyond the skill that can fairly be expected for them 💔

  • JoshCodes@programming.dev
    0·
    2 months ago

    Nice try Microsoft, I still don’t like your monthly “small” ui changes that hide the features I use and add extra “get copilot now” buttons