4 ms·
This is one of the things about this whole episode that I find baffling. Stuff like adjusting bug priorities and arranging for someone to tweet an announcement
by JamesMcGill 7y ago
This is one of the things about this whole episode that I find baffling. Stuff like adjusting bug priorities and arranging for someone to tweet an announcement is the work of a good engineering manager. This is the right person to run interference and handle comms and deal with things outside of the critical path, like bugzilla updates.
- dao- 7y agoThe priority field just plays no practical role here since the bug was immediately escalated.
- pbhjpbhj 7y agoIf people can see it externally it definitely has an effect, "oh moz aren't taking this browser breaking bug seriously". Which is probably why the parent said it's a management issue rather than a directly technical one, per se.
- rhizome 7y agoStuff like adjusting bug priorities and arranging for someone to tweet an announcement is the work of a good engineering manager So we can come to the obvious conclusion about Mozilla, then? No good "engineering" managers? Miss one reprioritization and you're out! This is what sane people think?
- Twirrim 7y agoAt no stage did the parent post state there are no good engineering managers at Mozilla. They just said that adjusting bug priorities is the work of a good engineering manager. There's a world of difference. If you want to complain about knee-jerk overreactions, I think you might want to look in the mirror first.
- rhizome 7y agoI have empathy for people in the middle of hair-on-fire incidents.