Although your bill might only show one bundled price depending on who supplies and delivers your electricity, the cost of electricity in the US usually includes both a "supply" or "generation" charge and a "delivery" charge. Based on what I'm seeing on that page I think it's almost certainly only showing the electric supply rates, not the combined total of supply + delivery.
I don't live in California so the nuances are lost on me, but it looks like for SF county the residential delivery rate is about 19c/kWh, the supply rate ranges from roughly 12-16c/kWh, and "surcharges" are 0-1c/kWh, for a total of 31-37c/kWh. For San Diego county the delivery rate is 25-26c/kWh, the supply rate is 15-18c/kWh, and surcharges are 2-5c/kWh, with a total of 45-46c/kWh.[1]
It depends on the climate where you live though, right? Where I am there's plenty of congestion. There's also plenty of rain, snow, slush, and road construction. The snow removal and construction really take a toll on the lane markings, so detectable lane markings isn't a guarantee either.
I'm also in the northeast US (more specifically New England) and that's the issue I couldn't get around when I looked into it.
My AC unit is only 1.5 tons but my furnace is 40k BTU and, unlike the 75k BTU furnace it replaced, is appropriately sized for the space. (Why someone previously installed such a massively oversized furnace I will never know.) If I remember correctly a 1.5 ton heat pump is roughly equivalent to 18k BTU, so it might be useful in the all too brief cool but not cold periods in spring and fall but in winter I'd still mainly be relying on the gas furnace.
> A strange tip had arrived from Belgium’s gambling commission.
I can't speak to Belgium specifically, but in many areas one of the responsibilities of the gambling/gaming commission is ensuring "fair" gambling. So they probably care more about the impact of match fixing on the "fairness" of sports betting rather than the reputational (I assume that's what you meant rather than "repetitional") risk to any particular sport.
When betting is involved, I don't see match fixing as all that different from someone bribing a casino employee to use dice loaded in their favor or help them cheat in a game of cards. Or depending on who's involved, maybe it's more like the casino using dice loaded in the casino's favor.
In any case I think it basically amounts to fraud. The published odds are inaccurate because the outcome has been fixed, allowing the people aware of that to make money at the expense of the people unaware. Fraud is generally a crime, so as long as the match fixing isn't reflected in the published odds IMO it isn't all that surprising that it's a crime.
The languages it gets translated to aren't deterministic so I put the same sentence in 10 times. I was curious if a simple statement that has a conceptual equivalent in many cultures would tend to survive relatively unscathed so each time started with "I made a cup of tea".
1. "I made a cup of tea"
2. "I work a tree cup"
3. "I have prepared a cup of tea."
4. "I made a cup"
5. "I make a cup of tea"
6. "I made a cuppa."
7. "I prepared a cup of tea"
8. "Tea"
9. "I made a cup of tea"
10. "I have a cup of tea."
Better than I expected really. I'm kind of impressed that it veered into slang on the sixth try and still retained the original meaning.
>The FDA approved Tezpire as a breakthrough drug for asthma in December 2021. Tezspire excluded morbidly obese people from their efficacy trials.
This statement is very misleading because morbidly obese people were only excluded from the Phase 2 PATHWAY trial[1] and were not excluded from the larger Phase 3 NAVIGATOR trial[2]. The FDA approved Tezpire based on both trials demonstrating efficacy, not just the PATHWAY trial.
To me, a lot of this reads more like some sort of "Team/Company Values and Culture" document than the user manual of a single individual.
Things like "Default to action" are pretty dependent on team/company culture and what you're working on. Your coworkers won't start defaulting to action just because you prefer it if their boss, their boss' boss, etc prefer cautious consideration. There's nothing wrong with preferring to work somewhere with a "default to action" culture, but presumably by the time someone is reading this you've already made the decision that the culture is a good fit for you. (Ditto for "There’s life beyond work". If that isn't the existing culture, then as a reader all it tells me is that you choose to work somewhere that doesn't share your values and we may be in for a bumpy ride.)
Similarly, the way it's written now "Mind the channel" reads like a mandate about team/company norms and culture. Despite being under the heading of "How to efficiently work and communicate with me", rather than explaining which channels of communication you prefer in which contexts, it makes a broad statement about what the reader should consider when communicating with anyone. IMO guidance on how to communicate with others in general, rather than you specifically, belongs in a team handbook and not your personal user manual.
"Don’t give clues" on the other hand is a good example of something that does seem to belong in a user manual. It explains something about you and tells the reader how to more effectively communicate with you. It doesn't make broad generalizations about how they should communicate with others in general.
In the end, I wonder whether this should be split into multiple documents - maybe a user manual (for people working with you) and a separate list of what's important to you in a working environment and company culture (for yourself when job hunting)?
In any case, for the user manual I think it would help to replace broad platitudes and decrees with statements focused on you. If a statement would make sense in a team handbook or similar, I think that's a sign that it may come across as inappropriate/presumptuous in your personal user manual.
The requirement the GP was referring to comes from the combination of the Telecommunications Act of 1996 and the 21st Century Communications and Video Accessibility Act (CVAA) rather than the ADA. The Telecommunications Act requires "video programming distributors" to provide closed captioning for most televised video programming (televised being the operative word here). The CVAA extended the requirement so that it also applies to televised video programming distributed on the internet. But according to the FCC's consumer guide on the CVAA, it "does not cover programs shown only on the Internet"[1].
The CVAA doesn't apply to Teachers Test Prep any more than it does to Netflix. But Title III of the ADA includes a section on "Examinations and courses" that states "Any private entity that offers examinations or courses related to applications, licensing, certification, or credentialing for secondary or postsecondary education, professional, or trade purposes shall offer such examinations or courses in a place and manner accessible to persons with disabilities or offer alternative accessible arrangements for such individuals"[2]. That's what the Justice Department found them to be in violation of. The fundamental problem was that their courses were inaccessible; lack of captioning (or other "alternative accessible arrangements") was what caused them to be in violation but wasn't a violation in and of itself.
By how much and why the cost of labor has changed over time is an interesting question. I'd assume that the bulk of the cost of labor is wages, but there are some other direct and indirect costs that might contribute in addition to wage related factors.
Carrying workers' compensation insurance was not the norm at the turn of the 20th century; injured workers could instead sue their employer for negligence but usually lost. Legal challenges to state legislation that made participation in a workers' compensation program mandatory weren't resolved until the Supreme Court's 1917 ruling on N.Y. Central R.R. Co. v. White. In the modern day, Texas is the only state where workers' compensation insurance isn't mandatory.
In a similar vein, workplace safety standards have seen a lot of change. With the exception of a few states that passed legislation sooner, workplace safety was largely unregulated until the Occupational Safety and Health Act of 1970 established OSHA.
I know less of the specifics but consumer protection laws have also changed. Many states now impose statutory warranties on new construction that cover construction defects for a period of time. It seems plausible that builders had less liability for such defects in 1914.
Construction equipment and the cost of running and maintaining it is another thing that I would expect gets rolled into the cost of labor. I'd assume that equipment costs are usually offset by increased efficiency (paying wages for less time), so it wouldn't increase the cost of labor, but it would be interesting to see data on that.
As far as wage-related factors, while blue collar wages may not have changed in general there are some exceptions. Based on the sources you provided, plumbers in 1913 San Francisco worked 44 hrs/wk and made $0.75 per hour for an annual wage of $1716 (or $44.9K in 2020 dollars). The median plumber in 2020 San Francisco makes $110.9K/yr. (Since SF might be an outlier, in St Louis in 1913 plumbers made $1515 annually, equivalent to $39.6K in 2020, and had a median annual wage of $80.6K in 2020.)
It's also possible the number and types of workers required to build a home has changed. Constructing a new home might now require more "specialists" (like plumbers) who command higher wages to do work that was either not done at all or was previously done by general laborers paid lower wages. It would be interesting to see data on that as well.
I'd guess personal preference of the musicians themselves is part of the reason microtones aren't more common in "western" music. Most of the musicians that I personally know at least seem to prefer creating/performing music that sounds good to them. And compared to non-musicians, most of them are also more aware of and bothered by notes that are "out of tune", especially ones with "classical" training.
Someone who works in medical research once pointed out to me that some research is intended to be confirmatory (i.e. confirming a hypothesis) but other research is actually intended to be hypothesis-generating. This definitely seems to be the latter.
My read on this is that we really don't know what causes things like schizophrenia, so much so that we're not even sure what to study to try to determine the cause. But the authors of this study found that a specific diet in mice with specific genes causes something that looks sort of like human psychiatric disease. They also found similar brain changes in both the mice and humans with psychiatric disease and that aspirin prevented some of the symptoms and brain changes in mice (which possibly suggests the brain changes are related to the behavioral symptoms and not just coincidental). Based on these results further study of, for example, GLO1 deficiency and/or the brain changes they found might be justified. So basically the takeaways are questions about whether/how these finding relate to human disease.
In the end, like most hypothesis-generating studies this strikes me as vaguely interesting but probably only really meaningful to other researchers in the field.
After reading the actual submission by Apple that the article links to, I think the article (especially the title) somewhat misrepresents what Apple said.
The overview section of Apple's submission states (numbering in original)
> 1. Apple understands that the Commission has received submissions from certain app developers concerning their ability to engage with Apple in the app review process.
> 2. As outlined in our meeting of 23 February 2021, Apple is surprised to hear that developers have legitimate concerns about their ability to engage with Apple in the app review process in circumstances where the purpose of app review is to ensure the quality of apps on the App Store and Apple invests significant time and resources in engaging with developers directly to work together to achieve that shared goal.
> 3. Apple would therefore like to provide further information to the Commission to assist it in assessing the veracity of the concerns raised by developers in their submissions.
Personally I would paraphrase that not as Apple claiming to be "surprised" by developer concerns, but rather as Apple claiming to be surprised by "legitimate" developer concerns. Or to put a finer point on it, that Apple isn't actually claiming to be surprised at all and "surprised to hear" is just a euphemistic way to say that they don't believe the complaints the commission has received are legitimate.
Probably a smart choice of wording on Apple's part - I don't think it would have been a better look if the headline had instead been "Apple Suggests That Developers’ Complaints Are Just Sour Grapes".
In freight "backhaul" typically refers to transporting goods during the return journey. During the principle (non-return) journey, often the starting location is more central, like a distribution center, and the destination is a smaller satellite location like a store. So when something is backhauled, that tends to mean it's transported from the smaller satellite location to the central location.
I don't tend to experience hunger and, as a result, interrupting my activities to eat multiple times per day can feel like a bit of an inconvenience. So I've frequently fasted daily since before "intermittent fasting" entered the common lexicon. It's not really intentional though, I will quite literally forget to eat or otherwise just don't make it a priority.
In my experience, I'm not sure it's quite the panacea it's sometimes made out to be. Perhaps there are psychological benefits to intentionally fasting that I'm missing out on. In any case, quite often when I'm wondering why I feel like shit I end up realizing something like I haven't eaten in 24 hours or in the last 48 hours I've eaten less than 1000 calories. Oops. I'm trying to be better about regularly eating 2 meals per day because I really do feel better if I've been eating consistently.
I'm not sure it's doing my blood pressure any favors either. Despite regular fasting and having a BMI of 18.1 (technically slightly underweight, as the lower bound of a "healthy" BMI is 18.5), my blood pressure is usually around 140/95. But who knows, maybe it would be higher without the fasting.
I used to work for a small tech company in the suburbs outside of St Louis, which is definitely not a HCOL area. When I left (to move back to a HCOL tech hub), probably about half of the engineering staff were H1-B visa holders. This was because we often had trouble finding qualified candidates that were either already local or willing to relocate to the area. Visa sponsorship was a much more compelling reason to relocate than anything we could offer US citizens.
The office was near Mastercard's global operations headquarters and it seemed like they also employed a lot of visa holders. So I don't think we were particularly unique in our willingness to offer visa sponsorship in a LCOL area.
Assuming you're deleting the row because it shouldn't be used by read queries, constraints like you described prevent the problem of having orphaned records in the child table but also prevent you from achieving your goal. On delete cascade would allow you to achieve your goal and prevent the orphaned records but could lead to deleting more than intended (especially if the child table is also a parent table referenced by further foreign key constraints, its children could in turn have children, etc). Of course, with no action/restrict you could also manually cascade the delete, but if you actually don't want to delete a child row and there's not an appropriate alternative value for its foreign key then you're in a bit of a pickle.
So if you want to delete a user but keep the records of their orders and still know who made those orders, then some form of soft delete is probably your best option. I believe that's the point rm999 was making (in response to the article asserting that soft deletes are a "data model mistake"). Properly configured constraints can prevent an "oops" but don't really do anything to solve the problem of this sort of delete from some contexts but not others.
Did they make risk adjustments for any confounding factors? It seems like all they found is correlation so it doesn't necessarily follow that eating mushrooms was actually the reason for the reduced risk.
Not a doctor but I have seen a neurologist for migraine before and my understanding is that migraine causes a pretty unique constellation of symptoms. If someone has repeated episodes of moderate to severe throbbing one-sided headache that builds up over 1-2 hours, lasts 4-72 hours, is intensified by physical activity, is lessened by lying in a dark quiet room, and causes nausea, sometimes vomiting, and sensitivity to light and sound then they almost definitely suffer from migraines. Because pretty much nothing else causes that combination of things. Sort of a "looks like a duck, swims like a duck, and quacks like a duck" situation, if you will.
Of course the experience isn't exactly the same for everyone - personally the headache I experience during a migraine isn't throbbing, but it is very much one-sided and concentrated behind my eye (which is common for migraines). But I think basically from the diagnosis perspective, if connecting the dots (symptoms) results in a picture of a duck (migraine), then it is a duck. If connecting the dots doesn't result in a duck picture because there aren't enough dots, or if connecting some of the dots creates a duck picture but there are left over dots that don't connect - that's when from the doctor's perspective further work up might be needed because it's not clear what the cause is.
For me at least, how I distinguish between other headaches and a migraine is that with migraine the headache is just one of the reasons I feel terrible. It's similar to having a concussion in a lot of ways and more severe migraines can be a little bit like having the flu as well. I'm kind of dazed, struggle to remember things, and trying to think feels akin to running on sand. Sometimes music starts to sound like random noise without any musical quality. Beyond just physical activity making the headache worse, I feel physically weak and tired. During more severe migraines, I often experience rapidly alternating chills and hot flashes. Sometimes NSAIDs will help with only the headache and, even though my head doesn't hurt that much anymore, sitting upright can still be unbearable. Merriam Webster defines malaise as "an indefinite feeling of debility or lack of health" and that's the best description I can come up with for the feeling of having a terrible migraine even when the headache itself is better. All in all, during a migraine I get the distinct impression that my brain is not functioning properly.
If a lot of that resonates, then you're probably also experiencing migraines. And if not, then that's the difference between what you described and migraine. "Cervicogenic headaches" also might be a thing that can cause headaches similar to a migraine and sound kind of like what you're describing. But I believe there's some debate in the medical community about whether migraine-like "cervicogenic headaches" are actually a separate condition or if it's just a way that migraines can present.
Personally I like leading commas for the ergonomics rather than the aesthetics. When I'm developing or debugging a query the first column is typically the one I'm least likely to change. I tend to build up the query from there, so the last columns are the ones I'm most likely to change or to comment out. Plus I find it easiest to interpret the result set when columns that I'm using as a temporary reference are at the very end of the row. So for the way I work, I've found that with leading commas I don't have to do as much futzing about with commas.
My job involves a lot of ELT pipelines though and the queries I'm writing are often to transform a client's data from whatever ill-conceived data model they've been using to a standard data model that we use for all clients. Those queries require a lot more "detective work" to get right than the queries that run against our standard data model. If I was just writing queries against the standard, I'm not sure I'd spend enough time developing/debugging to really notice any ergonomic benefit.
I don't live in California so the nuances are lost on me, but it looks like for SF county the residential delivery rate is about 19c/kWh, the supply rate ranges from roughly 12-16c/kWh, and "surcharges" are 0-1c/kWh, for a total of 31-37c/kWh. For San Diego county the delivery rate is 25-26c/kWh, the supply rate is 15-18c/kWh, and surcharges are 2-5c/kWh, with a total of 45-46c/kWh.[1]
[1] https://www.cpuc.ca.gov/RateComparison