Oh. Undo tuna I’m on mailbox.org and I was looking for a mobile and desktop client rather than a provider. But yeah I’ll definitely consider them the next time I’m looking to move mail provider.
"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."
Could someone clarify whether donations to Mozilla are earmarked for Firefox specifically? Or is it for unrelated initiatives, and Firefox is only funded through Google?
I assume the donation money can't legally reach Mitchell Baker, since it goes through the Mozilla non-profit, but the whole Mozilla Corp vs Mozilla non-profit structure and the handling of funds is still very confusing to me.
It's essentially the v model [1] for software development. It's commonly used in systems engineering and the industries that implement it, so military, avionics, medical, safety engineering etc. I work on industrial safety systems, and would echo the other posts here - it's a requirement of the industry, but it's rarely done well due to the cost to implement, and the difficulty in implementing tools like Doors.
NASA and the U.S. Military have good guides and white papers on it, which you should be able to find online with a bit of digging.
Unfortunately for you, I don't. I stay far away from the regulatory stuff - I really only enough to get my job done, mostly in the form of directives from my manager and our quality section.
That said, our software development process is really just a mild adaption of all our other development processes (like ones we use for hardware and reagent development). As I've described it above, it's a pretty standard engineering approach to design control, and there are all sorts of variations on them.
In fact, the FDA makes note of how broad the field of medical devices are, and does not actually enforce any specific design control process, but rather provides a framework for you to develop a process that meets your developmental and regulatory needs. As part of getting FDA approval, your design control process will be audited, as well as how well you followed it. In addition, medical devices are classified into 3 classes, corresponding to patient risk. Our product is currently classified in the lowest risk level, and so we can avoid a lot of additional requirements. As I recall from skimming through the standard (sorry, we only had a hard copy at work.. costs money apparently), higher risk devices with software components must have certain types of tests performed. In our risk class, we have total freedom to define our testing requirements - that said, the rigour of our testing is still under FDA scrutiny, it just means that there are no specific checkboxes to hit (like integration testing for example).
Sadly, the Thinkpad X230 seems to be replaced by the newer X240 now. Any idea if it's working just as well? I probably can still get a refurbished X230 somewhere, but the screen is a bit too bad :(.
X series laptops have historically had a lot of screen options to choose from if one wishes to upgrade. I have a X201s with an IPS from the tablet version I swapped in. 400+ nit outdoor panel, couldn't be happier with it.
I have only worked remotely in my career (as in by myself inside a home office), and I have worked in full remote as well as in mixed local/remote teams.
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.
