Rent's due today, thank heavens I just got paid.
I don't set up standing orders, got burned once with unarranged overdraft fees, that wasn't a good mont...
A lot of the time the cause of bad UX or poor quality code is not the Devs, but management, one way or another. Either through pressure to build more to increasingly delirious timelines or by not looking after their company culture.
You tend to see nonsensical, disjointed product UX and usability decisions a lot more in bigger, highly hierarchical organisations, with big teams, highly specialised, siloed ICs several levels removed from their end users by layers and layers of middle management fat.
I imagine if HSBC put out apps like OP’s article claims is because they probably follow a command and control structure like above, where developers are just tiny cogs hyper-focused on low-level tasks in a bigger, complex corporate machine and nobody really understands the full picture.
You tend to see nonsensical, disjointed product UX and usability decisions a lot more in bigger, highly hierarchical organisations, with big teams, highly specialised, siloed ICs several levels removed from their end users by layers and layers of middle management fat.
Yep, and those layers and layers of middle management will never walk away from a UI/UX review saying “yeah, looks good to me!” because that wouldn’t justify their existence, so they feel compelled to say something even when there’s zero real issues, which is how you end up with inane bullshit
Agreed.
A lot of the time the cause of bad UX or poor quality code is not the Devs, but management, one way or another. Either through pressure to build more to increasingly delirious timelines or by not looking after their company culture.
You tend to see nonsensical, disjointed product UX and usability decisions a lot more in bigger, highly hierarchical organisations, with big teams, highly specialised, siloed ICs several levels removed from their end users by layers and layers of middle management fat.
I imagine if HSBC put out apps like OP’s article claims is because they probably follow a command and control structure like above, where developers are just tiny cogs hyper-focused on low-level tasks in a bigger, complex corporate machine and nobody really understands the full picture.
Yep, and those layers and layers of middle management will never walk away from a UI/UX review saying “yeah, looks good to me!” because that wouldn’t justify their existence, so they feel compelled to say something even when there’s zero real issues, which is how you end up with inane bullshit