992 karma · joined November 2, 2010
The compose view looks like this: https://imgur.com/a/qULeL5a
"In 2018 she received a total of $2,458,350 in compensation from Mozilla, which represents a 400% payrise since 2008.[14] On the same period, Firefox marketshare was down 85%. When asked about her salary she stated "I learned that my pay was about an 80% discount to market. Meaning that competitive roles elsewhere were paying about 5 times as much. That's too big a discount to ask people and their families to commit to."[15]
By 2020 her salary had risen to over $3 million, while in the same year the Mozilla Corporation had to lay off approximately 250 employees due to shrinking revenues. Baker blamed this on the Coronavirus pandemic."
There is no incentive to do so.
I installed FreeBSD on it last night and apparently everything was detected and seems to be working fine.
The FreeBSD wiki has a Laptops page: https://wiki.freebsd.org/Laptops
Says the guy checking email every 3 minutes who unlocks and jailbreaks his phone just to have a mobile hotspot.
If you are in a position to choose/offer to work remotely, make sure that everyone you have to interact with is communicating in the same way, at least for work stuff. If half of your team is in an office and they aren't making an effort to communicate equally with the both local and remote team members, it will not work well. Having a remote team means an overhead in the communication for the local team.
Anyways, here is a great collection of resources on working remotely: http://www.wideteams.com/
So I'm going to build a crappy car, demo it using a Ferrari engine and tell I was trying to simulate the engine feature in my car. Doesn't sound like an apology to me.
Hence I try to divide my projects into lots of application agnostic code (the libraries that need to be unit tested), and little application specific code (the glue code that needs to be integration tested).
It means you should try to understand the libraries you're using instead of arbitrarily picking packages. Devise (https://github.com/plataformatec/devise) is a great example of that as they explicitly tell people not to use it unless they have a good understanding of the Rails framework.