I usually buy brand name over generic stuff because it is quantifiably better to me in some way. Cereal that tastes better, garbage bag doesn't rip, etc.
2,829 karma · joined July 29, 2010
"Move to Boise. There aren't too many people yet!"
If you don't understand how to interact with people, you don't understand. You need help to figure it out, or you need help to realize you don't need help.
But you're not wrong. If you wanna figure out what works for you, you'll have to experiment for yourself without a medical professionals help. That's true for any over the counter (OTC) medication in your local pharmacy, too.
Does anyone here have a preference for using Python to tackle concurrency-related issues? If yes, I'd love to hear your thoughts on the matter.
Aren't customers on the hook regardless? PG&E gets it's money from customers, which would imply that customers are paying would be the ones to pay down the debt. Maybe they mean customers are a captive audience, and rates could be raised to cover the costs of the debt without impacting PG&E's profits.
One of the following must be true:
- Fuchsia has perceived product value, and it's an investment
- Google doesn't have enough interesting work right now, the amount of interesting fluctuates up & down, and retaining expensive employees by having them work on "Fun Fuchsia" during the current down cycle is more efficient than hiring expensive employee attrition+recruitment
- Fuchsia has no product value, and Google has too many expensive engineers
For example, the word asshole. To me, asshole does not, and never really did, mean the hole in one's butt. Asshole means jerk. At least it did until I hosted someone from South Africa. He told me that in South Africa, my language would be considered very profane profane. To him, asshole ONLY meant (still means?) butthole. There was no overlap in how we understood the word.
So I recommend keeping your language as neutral as possible, relying on as little idiomatic wording as you can. Say jerk, not asshole. Say it's raining quite harc, not it' raining cats and dogs, etc.
Health insurance is cheaper when more people are in it, not fewer. If you start offering discounts to the healthiest people, it gets more expensive for unhealthy people. So let's say the sickest people no longer have insurance. Now there's a new group of unhealthy people in the insurance pool. So you raise prices for them, and they get kicked out, too. Eventually you get to the point where insurance is not useful, because nobody needs it at all, as the insured people don't get sick. Until they do get sick, at which point they get kicked off the insurance plan. Health insurance that doesn't insure is basically fraud.
If you want to drive down the health related costs of healthcare, reduce the things that make people sick.
https://blog.carbonfive.com/2018/03/19/lightweight-dependenc...
For context, Elixir (which includes Erlang) is a compiled language, but it doesn't/can't catch a lot of compile time type errors that you'd only uncover at runtime. For example, one process can send a message of any type to another process. There just isn't a great way (for the Elixir compiler) to catch that at compile time. It gives you more flexibility, but you can't have confidence that it'll work just because it compiled. Dependency injection with tests is a really helpful tool in Elixir.