Being to blame is different than being actively trying to sabotage you. Many companies will be re-evaluating their relationship after this problem happened, but doing that while your systems aren't functional seems counter-productive.
Changing vendors and choosing one that's more reliable is a perfectly sensible outcome of this situation once your system are back up and you're no longer hemorrhaging money.
During an ongoing incident, when all of your operations are down, is not the time for it though. If you think there's even a 1% chance that the help can help, you should probably take it and fix your immediate problem. You can re-evaluate your decisions and vendor choices after that.
Most companies don't pay that, step 1 is identifying the companies that do and focusing your efforts on them exclusively. This will depend on where you live, or on your remote opportunities.
Step 2 is gaining the skills they are looking for. Appropriate language/framework/skill/experience they optimize for.
Step 3 is to prepare for their interview process, which is often quite involved. But they pay well, so when they say jump, you jump.
I'm not saying you'll find $600k as a normal pay, that's quite out of touch unless you're in Silicon Valley (and even then). But you'll find (much) higher than market salary.
It's actually more than that. Last I checked the US government spends much more per capita on health care than any other country on earth. And by a large margin, not quite twice the 2nd country spending the most but almost.
According to Google their market cap is currently 7.78B but I don't know what it was when they issued them so it's hard to say how big of a proportion it was at the time. The stock price did go up when they did it too, against all odds.
There are issues with issuing shares as described in the link you shared, I don't want to minimize that. And you're right about diluting existing shareholders.
My point was more that many companies do it and the money the company raises by doing so gets added on the balance sheet, which can be used to fund profitable ventures, or to burn. The main differentiator is whether they are raising money because they believe they can make more money out of it (ie Shopify) or because they have to in order to avoid bankruptcy (ie Hertz).
A public company can absolutely issue new shares, it's not the typical way companies raise money but it happens all the time. GameStop itself did it during the craze to capitalize on the increase share price did they not?
No idea why you think it would bankrupt the company, it changes nothing. The new shares is balanced by the new money on the balance sheet.
Historically sitting on cash is a terrible decision a majority of the time, it's not even close. Without knowing you, your chance of correctly timing the peak and the bottom of the market is simply abysmal. The market may crash tomorrow, but it probably won't.
Let's say by incredible luck you manage to time both of these events perfectly, then what? There will be other crashes in the future, that's a certainty. And you won't be able to time all of them.
The difference between null and undefined in JavaScript is something I wished had never been implemented. Other languages refer to null as their billion dollar mistake, but somehow JavaScript got 2 of them with slightly different but sometime identical behaviour. I would defer to eslint to prevent this particular issue if you care about it, this allows you to set rules in your own code without any impact to the outside world.
I have only seen null vs undefined lead to 2 things in my experience: mistakes and bikeshedding.
Balance is extremely important, and can usually only be appreciated with hindsight which makes it hard to judge when you're in the moment.
I'm in the same boat as the author as far as working too hard, but I've never done it on my salaried work, only on my own projects. Most of them went nowhere and a few gave something useful, but in the end I learned a lot. And it's easy to just drop whatever you're working on when it's just for you.
I can't say if it's out of principe or out of spite, but I actually despise the very idea of doing unpaid work for my employer. If they want more work they can pay me for it, or more likely hire someone else to soak the extra efforts. I work as hard as anyone else during my work hours, and I stay up to date so what more do they want of me. I've actually had managers, who were good managers otherwise, subtly told me I was not doing much (unpaid) overtime compared to other people during my annual review. Funny how things work out, I found another job right after that paid me 50% more and didn't care about my after hours work.
It's a business arrangement, not an emotional relationship. They backed her because they thought they'd make a profit, and they did. They owe each other absolutely nothing else.
Most people can't afford to stand up for themselves, I'm glad she's doing it.
You can disable remote login in the settings. It's the first thing I did when I got mine. So it's impossible to login to my router using my Ubiquiti account.
Can't comment on issues have been getting, but I only have good things to say about mine. It's not perfect and the learning curve can be steep, but it's miles ahead of any other routers I've used before. The only thing that came close was when I flashed dd-wrt on my old Linksys.
They had support for Bitcoin a few years back, merchants could accept Bitcoin in addition to whatever currency they already supported. The feature was killed because they didn't find Bitcoin useful for transactions (can read more about the why here https://stripe.com/blog/ending-bitcoin-support).
I'm using the Reeder app on iOS, it syncs with a bunch of services. Before I was using Fiery Feeds, but they switched to a subscription model and the app I had paid for wasn't supported anymore.