This woman seems not sincere at all ¯\_(ツ)_/¯
Leaving Mozilla
31–40 of 190 posts
Re: Leaving Mozilla
#32> That and.. I am also extremely burnt out. > Working too much during the week for the last 2 years was normal for me We need to stop normalizing working beyond a 40 hour work week. I can accomplish far more and with greater clarity of purpose, mental acuity and motivation in an actual 40 hours, than I could if I attempt to push myself to 10-12 hours a day.
I agree, but I think part of the issue as well is that many times there's just very little direction on a weekly basis so much of the work is wasted in the sense that it didn't need to be done that week. Overworking yourself (sprinting) to do work that didn't need to be done that moment is one of the most discouraging and demotivating things IMHO.
There have been times where I've worked and it was extremely clear what needed to be done at every stage and I worked 80 hours and wasn't burnt out at all.
TLDR: Spinning the wheel mindlessly is bad and I think accelerates burnout, in general it's not necessary to work more than 40 hours a week.
Re: Leaving Mozilla
#33Gotta say that Emily comes across as a HUGE grifter and part of the reason identity politics have swiftly crept up into tech. It's obvious (and apparent from her past tweets) that she joined tech because she'd have an advantage as a female (can play the diversity card), and the $$$. I mean look @ the suggested article after this post: "Going Viral as a Woman in Tech". That was her edge, she made her money, and now will potentially move back to the east coast and be with her rich family. If any of you actually feel bad for her you're getting played. Now I'm sure her next move is to be a consultant to other women or move out of engineering entirely. This will probably get killed, but someone needs to expose these charlatans for who they really are. Good riddance.
Re: Leaving Mozilla
#34> The cherry on top was being specifically targeted for harassment that same week after the release by unhappy users of Firefox looking for someone to direct their frustrations at. Thats lovely.
I was curious about this, and went searching, and it's fairly difficult to figure out exactly what is being referenced. There is a reddit thread that links to deleted tweets that appears like it might be related: https://www.reddit.com/r/browsers/comments/i8nuyb
Thanks for the link, always good to get more sides of a story.
Re: Leaving Mozilla
#35> That and.. I am also extremely burnt out. > Working too much during the week for the last 2 years was normal for me We need to stop normalizing working beyond a 40 hour work week. I can accomplish far more and with greater clarity of purpose, mental acuity and motivation in an actual 40 hours, than I could if I attempt to push myself to 10-12 hours a day.
At my old job i switched to 4 days a week. I'm pretty sure I got more work done overall and only got paid 80% for it. It should be a no brainer for employers
Re: Leaving Mozilla
#36> That and.. I am also extremely burnt out. > Working too much during the week for the last 2 years was normal for me We need to stop normalizing working beyond a 40 hour work week. I can accomplish far more and with greater clarity of purpose, mental acuity and motivation in an actual 40 hours, than I could if I attempt to push myself to 10-12 hours a day.
I'm on a personal quest to reduce the average American working week
idk if you're a millenial but I often think that this will be millenials' legacy - a 32 hour work week would be amazing
Re: Leaving Mozilla
#37> ...but the release just felt like a blip in our planned schedule before jumping into more sprints and fires and thinking about the next iteration. Welcome to agile ? I know the feeling, honestly, but in software engineering there's always more bugs to fix, more features to develop, more needs of the users that require your attention. Cutting a release should feel like letting go, and indeed at places it does, but u…
I have no particular data for her harassment, but I've read here and on other media outlets some pretty angry comments about that Android rewrite. I can totally imagine some people venting on Twitter, and even targeting parts of the team. Though I can't say I've seen that myself... just hypothesizing.
That's what I wanted to know. Was there targeted harassment like this from users? Was it just twitter flame? Did she get angry emails? I understand it has no bearing on the OP but I feel like it would add gravity to her experience if we had some context to empathize with.
Re: Leaving Mozilla
#38The amount of abuse she got on Twitter after the FF Android launch was hard to believe. I don't understand how somebody thinks that disliking an update to a piece of free software justifies shouting abuse at an engineer who worked on it.
Re: Leaving Mozilla
#39I still use Firefox. I’m sticking around. It’s becoming more annoying to use, but I’d rather support Mozilla than anyone else. The window into the internet shouldn’t be controlled by big companies. It’s a principle thing for me. To the author, thanks for your efforts.
I'm becoming more and more of the opinion that the web is dead and Google has won.
Same. But I’ll continue to use Firefox until someone turns out the lights...
Re: Leaving Mozilla
#40> ...but the release just felt like a blip in our planned schedule before jumping into more sprints and fires and thinking about the next iteration. Welcome to agile ? I know the feeling, honestly, but in software engineering there's always more bugs to fix, more features to develop, more needs of the users that require your attention. Cutting a release should feel like letting go, and indeed at places it does, but u…
> Welcome to agile?
Agile is not essential to software development. IMO Agile should be thrown in the trash heap of technology history ASAP. Does Firefox even need a "release schedule"? Why? There's rarely a good reason for fixed software schedules.
It's funny, Google had a pretty tight software schedule... until it came time to publish their App Store privacy details, and then they decided they didn't need a release schedule after all. Except it backfired because their software just assumed there would be frequent updates, and now the apps are showing warnings because they haven't been updated.
Death to schedules. Yes, there's always work to be done, but it doesn't have to be done by an arbitrary deadline.