Departures happen, but the way in which they happen determines the culture and maturity of a company; its sad to see Steve leave like this.
I hope you go somewhere that truly values you.
Thank u, next
41–50 of 182 posts
Re: Thank u, next
#42Earlier quoted context omitted.
I don't think it's particularly professional to get into more detail than I did in my post, as much as I'd like to. As the saying goes, there are three sides to every story. I'd rather focus on the future.
Why hint at it at all then? Without details it won't satisfy the curious nor help fix whatever problems there might be. As someone who still works for Mozilla out of conviction, this feels like an unnecessary low blow.
I have no problem with hinting at it. If someone inside Mozilla whom Steve normally does not deal with is concerned and as curious, and wants to know the problem(s) AND fix it, they will give Steve an opportunity to chat (not necessarily asking him back). If they are not interested in fixing or listening then it will be a typical exit interview.
Re: Thank u, next
#43This is a bummer on many levels, but also personally, a bit of a relief. For a while I was considering going all-in to try to get a role at Mozilla. I really believe in their mission, and I drink the kool-aid when it comes to the browser market getting gobbled up. What held me back at the time were the company reviews. The culture sounds toxic, and the management sounds incompetent, and there's no force of change tha…
> culture sounds toxic Is this an indirect reference to Brendan Eich's sacking or is it even worse?
Even worse. I think the Brendan Eich sacking falls more in line with the management being incompetent.
Re: Thank u, next
#44Earlier quoted context omitted.
I don't think it's particularly professional to get into more detail than I did in my post, as much as I'd like to. As the saying goes, there are three sides to every story. I'd rather focus on the future.
Why hint at it at all then? Without details it won't satisfy the curious nor help fix whatever problems there might be. As someone who still works for Mozilla out of conviction, this feels like an unnecessary low blow.
I tried to stick purely to facts. I don't want this to be taken as some sort of low blow. Maybe email me with some specifics that you think are bad and I can edit the post?
Re: Thank u, next
#45Earlier quoted context omitted.
I don't think it's particularly professional to get into more detail than I did in my post, as much as I'd like to. As the saying goes, there are three sides to every story. I'd rather focus on the future.
Why hint at it at all then? Without details it won't satisfy the curious nor help fix whatever problems there might be. As someone who still works for Mozilla out of conviction, this feels like an unnecessary low blow.
You talk as if you are _owed_ these explanations. You are not.
I read the post as an explanation of his decision, with as much information as he was comfortable sharing. And since it's his post, his job and his _choice_ then that's all we get.
Re: Thank u, next
#46Earlier quoted context omitted.
I don't think it's particularly professional to get into more detail than I did in my post, as much as I'd like to. As the saying goes, there are three sides to every story. I'd rather focus on the future.
Why hint at it at all then? Without details it won't satisfy the curious nor help fix whatever problems there might be. As someone who still works for Mozilla out of conviction, this feels like an unnecessary low blow.
I suspect you might be able to get more info over a non-public channel. For me as an outsider, seeing this is helpful to put it into context (and evaluate what sort of failure this is and how this impacts my future trust of Rust / Mozilla / Steve / etc.) but it's certainly not something that's my place to fix. And I understand that many people are unhappy with their management for what sounds like broadly similar reasons, and this isn't a statement that Mozilla is uniquely bad.
Re: Thank u, next
#47Earlier quoted context omitted.
Mozilla doesn't really "shepherd" Rust development. We've constructed the Rust project so that Mozilla cannot control it; decisions are made via consensus, and Mozilla employees make up ~10% of the overall Rust team. There's never been some sort of mandate to do something specific with Rust from upon high, and I don't expect there to ever be. If they tried, it wouldn't work!
The big concern is not that it wouldn't work, it is that they might try, and that you may have been one of the things preventing that from happening. All the best luck going forward, because you absolutely deserve it.
I can assure you that Mozilla will not try to take control of Rust development.
(It's unclear to me what that would even mean anyway. Rust is getting pretty mature, and the direction of the language is largely fixed at this point.)
Re: Thank u, next
#48Earlier quoted context omitted.
> culture sounds toxic Is this an indirect reference to Brendan Eich's sacking or is it even worse?
Even worse. I think the Brendan Eich sacking falls more in line with the management being incompetent.
I thought Brendan Eich /was/ management at the time of his defenestration.
Re: Thank u, next
#49This is a bummer on many levels, but also personally, a bit of a relief. For a while I was considering going all-in to try to get a role at Mozilla. I really believe in their mission, and I drink the kool-aid when it comes to the browser market getting gobbled up. What held me back at the time were the company reviews. The culture sounds toxic, and the management sounds incompetent, and there's no force of change tha…
> culture sounds toxic Is this an indirect reference to Brendan Eich's sacking or is it even worse?
Not the OP, but I don't have a problem with the Brendan Eich incident (if a CEO doesn't have the confidence of their employees, then they shouldn't be CEO), but I still have a bad impression of Mozilla culture. To me the clearest sign is their product decisions. They just haven't made a lot of sense recently.
Re: Thank u, next
#50Earlier quoted context omitted.
Mozilla doesn't really "shepherd" Rust development. We've constructed the Rust project so that Mozilla cannot control it; decisions are made via consensus, and Mozilla employees make up ~10% of the overall Rust team. There's never been some sort of mandate to do something specific with Rust from upon high, and I don't expect there to ever be. If they tried, it wouldn't work!
The big concern is not that it wouldn't work, it is that they might try, and that you may have been one of the things preventing that from happening. All the best luck going forward, because you absolutely deserve it.
If that's your worry, then you should be relieved by this change. This is one more person who is involved with decisions in Rust who isn't employed by Mozilla.
That said, to repeat, I don't believe this is something Mozilla would ever try to do.
And thanks.