←back to thread

1318 points xvector | 9 comments | | HN request time: 1.188s | source | bottom
Show context
driverdan ◴[] No.19823850[source]
First they force code signing on everyone without a way to disable it then they break it. This is an extreme level of incompetence I didn't expect from Mozilla.

They'd better have the best post mortum ever, possibly with someone being fired.

replies(9): >>19823853 #>>19823924 #>>19823927 #>>19823983 #>>19823993 #>>19824074 #>>19824096 #>>19824180 #>>19824307 #
1. steve19 ◴[] No.19823924[source]
Why does someone need to be fired? Does some blood spilled really make it better? Have some compassion.
replies(2): >>19823982 #>>19824132 #
2. driverdan ◴[] No.19823982[source]
I'm generally not a fan of firing people for making mistakes. This one is so monumental it may require it though. This breaks most FF installations.
replies(3): >>19824003 #>>19824156 #>>19824456 #
3. steve19 ◴[] No.19824003[source]
You didn't answer my question. What does firing achieve? You fire a person who learnt their lesson and will never make the mistake again? And then hire someone new?

Or you fire the scapegoat because of a broken system that allowed one person to make a mistake?

replies(2): >>19824134 #>>19824498 #
4. Silhouette ◴[] No.19824132[source]
Why does someone need to be fired?

That might seem rather extreme, but the fact that this situation was even possible was a consequence of a series of bad decisions over an extended period of time about the required behaviour of new versions of Firefox, combined with technical failures that betray fundamental weaknesses in the whole system design. Whoever was ultimately responsible for those failings demonstrably isn't competent to run something of this importance and should probably either implement immediate and dramatic changes to the relevant policies and technical details or consider their position. Anything less is surely going to damage trust, which is something Firefox can ill afford when it's already in danger of being reduced to a niche product rather than a mainstream browser.

5. driverdan ◴[] No.19824134{3}[source]
If this mistake was due to incompetence then the person should be fired. Incompetence shouldn't be tolerated.

But we're outsiders looking in and don't know what's going on at this point. That's why I used the qualifier "possibly." It's quite possibly it wasn't incompetence.

replies(1): >>19824661 #
6. eli ◴[] No.19824156[source]
Couldn’t disagree more. Do you want to fix the conditions that led to the problem? Or do you view a post mortem as a punitive process?
7. mrep ◴[] No.19824456[source]
Can you link to your linkedin profile so we all know who to dox next time you make a mistake? If you have a twitter, please add that as twitter works even better for mobs.

Thanks :)

8. luckylion ◴[] No.19824498{3}[source]
> You fire a person who learnt their lesson and will never make the mistake again?

That's true, sort of. How often do you let people make huge mistakes before you decide that maybe they are just not apt for the position that they've been promoted to and Peter was right? Once? Twice? And unlimited amount, as long as it's never the exact same mistake?

9. floatingatoll ◴[] No.19824661{4}[source]
“quite possible”