As someone with a partner who’s an accountant, I love seeing technologists be confidently wrong about accounting fundamentals vs. the type of technicalities that she has to deal with. Your comment highlights the absurdity of their confidence; kudos.
Give an example don't leave us hanging. I'm really curious how you can find an example of a temporary market liquidity move turning somehow into a long term adverse event for a company. Never heard of it
> To get the remaining 15%, which they are contractually obligated to acquire, they must purchase from the founder. As they are in violation of their contract if they fail to acquire the remaining 15%, the founder now has complete control to dictate any price they want.
This is not correct and I'm surprised this comment is upvoted to the top. The float is the float, nobody goes to buy shares that aren't available in the float.
Hey guys I rooted my humanoid and it killed my mom when I disabled the "slow limb motion" mode. It just wacked her in the head as she walked in the kitchen and she's not moving what do I do??
You should @linustechtips and hope he picks it up, then you have a good chance of getting a voucher for the funeral and getting a shout out in the manufacturers next demo when they talk about their new safety features.
You misunderstand, (continued) runtime is dependent on the ability to deploy. For instance: a vulnerability is realized or a customer needs something (availability, feature, who knows), you'll appreciate handles under your control. Service can easily degrade, without.
I've done this same thing, GHA as a control plane. It was for people who could wait; the actual operators regularly skipped the middleman. Preference or necessity, take your pick.
Runtime is separate from deployment. An incident in your deployment infra doesn't affect production. The fact that you may have to deploy to change what's live is what defines it as an incident, but it's still a different thing from a production incident.
From "nothing to do with" to "separate", I'd say we're making progress.
Deployment is how you fix problems with the runtime. Not just availability, shortcomings. I'm not going back and forth about this, there is a relationship here. Man architects, God laughs.
Here's a fun phrase to latch onto: 'escape', production is the test environment we all share.
GitHub goes down, yes, your service remains. For now. We chose to not wait, suggest others don't either. I agree in spirit with the GP. Misfortune is the fortune that never misses.
reply