hamstercat
Joined 10 years ago
Joined 10 years ago
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.
I just assumed all airlines did it.
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.
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).
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.
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.
I have only seen null vs undefined lead to 2 things in my experience: mistakes and bikeshedding.