hrefna,
@hrefna@hachyderm.io avatar

I find it worthwhile to go back now and again and look through analyses of why a piece of software succeeded or failed.

It's always particularly illuminating to look at three things:

  1. The role of leadership in the failure.
  2. How much leadership got paid regardless/what happened to leadership afterwards.
  3. What happened to the rank-and-file who actually build the software.

The story is always basically the same, with a few variations on the themes.

https://kotaku.com/how-biowares-anthem-went-wrong-1833731964

hrefna,
@hrefna@hachyderm.io avatar

People will occasionally poke at Google's developers for something about one of Google's products and its like… I agree with you, as do most developers I know (not that I talk about specifics publicly in the moment).

You have to look above the team who is doing the work. They've probably already said their piece and were simply ignored.

gretared,
@gretared@sfba.social avatar

@hrefna it’s a little like getting mad at a deli workers for what sandwiches are on offer except these are very well paid deli workers who in theory could go work for another deli…where they still don’t make the menu

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • DreamBathrooms
  • ngwrru68w68
  • modclub
  • magazineikmin
  • thenastyranch
  • rosin
  • khanakhh
  • InstantRegret
  • Youngstown
  • slotface
  • Durango
  • kavyap
  • mdbf
  • GTA5RPClips
  • JUstTest
  • tacticalgear
  • normalnudes
  • tester
  • osvaldo12
  • everett
  • cubers
  • ethstaker
  • anitta
  • provamag3
  • Leos
  • cisconetworking
  • megavids
  • lostlight
  • All magazines