Firefox

17899 readers

37 users here now

A place to discuss the news and latest developments on the open-source browser Firefox

founded 4 years ago

MODERATORS

k_o_t@lemmy.ml

442

Mozilla has fired Chief Product Officer Steve Teixeira after cancer diagnosis (mastodon.social)

submitted 1 month ago by LWD@lemm.ee to c/firefox@lemmy.ml

106 comments fedilink hide all child comments

sigh

you are viewing a single comment's thread
view the rest of the comments

[–] possiblylinux127@lemmy.zip 3 points 1 month ago (1 children)

They are just really poorly managed

[–] PM_Your_Nudes_Please@lemmy.world 7 points 1 month ago (1 children)

Sure, but it’s worth asking why the management is so poor. Many people have theorized that it’s because Google is pulling the strings; It would be in Google’s best interest to keep Firefox around on life support, because it helps them avoid antitrust lawsuits if they can point to Firefox and go “nope not every browser is Chromium based!” But it’s also in Google’s best interest to whittle Firefox’s usage down to near zero, which is what every single recent Mozilla decision has been aiming to do.

Mozilla was getting paid a lot of money by Google before Google got their hand slapped in an antitrust lawsuit. Many people have theorized that since that lawsuit, Google has pivoted to making deals directly with Mozilla’s management instead.

[–] KLISHDFSDF@lemmy.ml 1 points 1 month ago

Sure, but it’s worth asking why the management is so poor

Could just be incompetence.

Working in a bigger corp and seeing people continuously fail upwards or get hired into positions where they run around like headless chickens - sometimes the reason is leadership putting people in the wrong role and not holding them accountable because its easy to "fudge metrics" and believe things are going well.

The strategy I've seen far too often:

Deliver a half-working project that is bursting at the seams and requires more work and resources (or introduces a technical debt that most people can't even begin to comprehend).
Leadership declares it a success because a long enough train wreck takes time to be noticed when you're near the end of the tracks and the people at the front lines are doing everything they can to avoid it.
Find a new job before the shit hits the fan (typically hold off until your RSU's fully vest) and talk about how you implemented X while saving company Y and how successful it was.
Leave the place worse off than before.
The project/implementation starts showing signs of failure and leadership blames others (because the guy who implemented things is now gone and he did things so well how could it possibly be their fault?)

Too often I've seen meetings between management not even understanding what their "core issues" are. How do you even make a business better if you don't even understand your pain points?

It's both fascinating and scary.