It's not all suppliers, Qualcomm is less likely to play that game. Valve was referencing specifically dram and flash memory suppliers, who are a cartel already and are now also looking at surging demands so they can perform a direct market shakedown by figuring out which customers still need to pay that much and which have been priced out.
They will keep going until the amount they produce no longer has customers, but until then they have not found the highest price for their goods, and the line must go up.
A computer can never be held accountable, therefore computers must never make a management decision.
Rules about submissions and determining if a pr helps a project is a management decision. AI or automated tools can reject a PR if it fails to meet a human made rule (like failing to compile or breaking code standards) but accepting a pr to merge? That should be a human.
Wine is no longer a vm, they switched approaches a couple years back and now perform translations from windows specific apis and commands into the nearest available Linux version. Slowly refining the process like a fine wine to reduce the differences. That's also why wine developers work closely with the dxvk devs (direct x 7-12 translated into vulkan regardless of platform) and other translation layer devs to be able to use their tools rather than duplicate the work.
I naturally sat at around 1000 ng/dL before transitioning and felt fine. Then was the fun game of trying to suppress that level since my body apparently runs on high t levels. A few years later and the solution was surgically removing everything that can produce testosterone.
If it's for cross gender hormones it's gender affirming care. Doing the same treatment but within one's assigned gender therefore should also be considered gender affirming, because it's focusing on one's gender as the basis for the standards. For potassium levels there isn't a gendered range of values, but for testosterone, there is a set of values for men, and a different set for women.
Syncthing with a push/pull across devices and multiple databases is amazing. I have a master db, a db of Netflix or similar that I can share freely with friends that can sync things back over, so that we can share accounts without fussing about changing passwords since it all syncs over quickly.
It's not even a few existing designs... There is an exact pattern called the eurion constellation that all printers block. Then the process for printing each countries currency just involves placing a eurion constellation and you get the protection.
Its a single pattern that is very rigidly defined, to the point that many counterfeit bills that pass inspection shift one mark off by about a millimeter to get it printed.
Granted having worked at a bank when I found out was that the bill didn't have the off color threads as well, but it almost was approved despite getting a close inspection.
Honestly the approach of telemetry for support makes sense. It's why for my Fedora system I have telemetry enabled to a decently high level that I would be alarmed at with windows.
Part of the reason is that it's so easy to enable/disable that I'm comfortable with more since I know how much I am sharing versus needing to "guess" how much is still open. Another is just that I have respect for software that respects me, so I'm more likely to send something back to help the dev.
The biggest tell for me in different areas is if data collection is presented as an opt in - even if it's a screen you have to see and answer before use - then to me it's a choice that I might want to make. If it's there by default, it's Spyware until proven otherwise, because I wasn't told and the process foe removing requires prior knowledge.
You know consoles arrive doa sometimes, right? People just don't mention it. Also this one was fixed by leaving it overnight, so not a complete failure either.
That is the "classic" approach, but dietician increasingly recommending varied strategies fire different people.
I've been trying to gain weight for years and the most effective method has been 2 meals a day and intentionally snacking on small candies throughout since those teens to make me feel hungry as an appetizer rather than full like other snacks did. If I needed to lose weight the recommended practice based on how I live would be 4 meals a day and never snacking.
The way gaining or losing weight works is simple, it's calories in versus calories burned. For some people snacking, so long as it reduces how much is eaten at meals, increases calories burned by a significant amount. Therefore keeping them at a lower weight. For others it doesn't have that effect, and usually it's because those people eat a consistent amount in their meals regardless.
Usually p hacking doesn't come from 1 constraint, especially a well explained one, but instead comes from adding a couple or completely unexplained constraints (like a team losing more if their coaches wife is in one section of the stands or another) because at that point it's decreasing the number of samples (times you have as a reference) to force a significant result.
So usually for sports p hacking is stats about 1 team only, rather than a general stat about the sport. Preferably a restriction on the other team, then a follow up game based restriction so it seems plausible to the viewer.
I mean what I have is multiple database files I mean I just have multiple databases in use for that. I have my accounts, a "shared with partner." and a "friends" database. It works decently well just have to set default for passwords to save on mine, and then use sync thing to sync between my devices to the home pc, and just Google drive for others.
To add to the other response - it is much more difficult to work with Ai to debug inconsistent issues or similar unless you can understand the code and step through with a debugger to check for race conditions or similar.
Recently I was working with an Ai tool for some c code that depending on machine ran wildly differently. The Ai was unable to identify any issues, and kept recommending fixes for hardcoding values or similar that I had to revert. The fix ended up needing to use valgrind to create a different enough environment to see how a race condition was made to properly have one async call delay for the other.
AI can be powerful, and humans can be dumb. But if the code was human made, I would not have needed 3 hours to find a problem, and I wouldn't have tried to turn to AI for a simple fix because I'd know what I was looking for to start with.
But you're forgetting the key difference that makes it so much worse - we can fix human mistakes especially if we can talk to the human to figure out how. With an llm we have no external reference, only poorly designed code where the comments are there to guide the writing, not describe what was written. So it's much harder to debug an output, and the llm cannot be trusted to clean it up either.
Having worked food service, it means your restaurants didn't get bad ingredients and such - I've had in receiving calls back and forth from the kitchen about what is 86 for now. Usually "salmon warm, 86 salmon" . Which would get a call back about what other stuff is supposed to be thrown out with it. "86 the peas they won't make next shipment."
How is it robbery if you net the conditions of a large corporation?
We don't tell the customer when we call the fraud department. That said in this case we would be calling the police via keywords.
5 minute response time so I'll play a game of needing each check to have a manual review of history to sign it over to them.
As a bisexual woman, yes. It works very well. I would also go from attempting to flirt with words to losing my voice.
It's not all suppliers, Qualcomm is less likely to play that game. Valve was referencing specifically dram and flash memory suppliers, who are a cartel already and are now also looking at surging demands so they can perform a direct market shakedown by figuring out which customers still need to pay that much and which have been priced out.
They will keep going until the amount they produce no longer has customers, but until then they have not found the highest price for their goods, and the line must go up.
A computer can never be held accountable, therefore computers must never make a management decision.
Rules about submissions and determining if a pr helps a project is a management decision. AI or automated tools can reject a PR if it fails to meet a human made rule (like failing to compile or breaking code standards) but accepting a pr to merge? That should be a human.
There's also Portland, which now in recent years has become the city of trans people. But that's only from the last few years.
Wine is no longer a vm, they switched approaches a couple years back and now perform translations from windows specific apis and commands into the nearest available Linux version. Slowly refining the process like a fine wine to reduce the differences. That's also why wine developers work closely with the dxvk devs (direct x 7-12 translated into vulkan regardless of platform) and other translation layer devs to be able to use their tools rather than duplicate the work.
I naturally sat at around 1000 ng/dL before transitioning and felt fine. Then was the fun game of trying to suppress that level since my body apparently runs on high t levels. A few years later and the solution was surgically removing everything that can produce testosterone.
If it's for cross gender hormones it's gender affirming care. Doing the same treatment but within one's assigned gender therefore should also be considered gender affirming, because it's focusing on one's gender as the basis for the standards. For potassium levels there isn't a gendered range of values, but for testosterone, there is a set of values for men, and a different set for women.
Syncthing with a push/pull across devices and multiple databases is amazing. I have a master db, a db of Netflix or similar that I can share freely with friends that can sync things back over, so that we can share accounts without fussing about changing passwords since it all syncs over quickly.
It's not even a few existing designs... There is an exact pattern called the eurion constellation that all printers block. Then the process for printing each countries currency just involves placing a eurion constellation and you get the protection.
Its a single pattern that is very rigidly defined, to the point that many counterfeit bills that pass inspection shift one mark off by about a millimeter to get it printed.
Granted having worked at a bank when I found out was that the bill didn't have the off color threads as well, but it almost was approved despite getting a close inspection.
Honestly the approach of telemetry for support makes sense. It's why for my Fedora system I have telemetry enabled to a decently high level that I would be alarmed at with windows.
Part of the reason is that it's so easy to enable/disable that I'm comfortable with more since I know how much I am sharing versus needing to "guess" how much is still open. Another is just that I have respect for software that respects me, so I'm more likely to send something back to help the dev.
The biggest tell for me in different areas is if data collection is presented as an opt in - even if it's a screen you have to see and answer before use - then to me it's a choice that I might want to make. If it's there by default, it's Spyware until proven otherwise, because I wasn't told and the process foe removing requires prior knowledge.
You know consoles arrive doa sometimes, right? People just don't mention it. Also this one was fixed by leaving it overnight, so not a complete failure either.
My first boyfriend was named Lance.... I might send him this joke.
That is the "classic" approach, but dietician increasingly recommending varied strategies fire different people.
I've been trying to gain weight for years and the most effective method has been 2 meals a day and intentionally snacking on small candies throughout since those teens to make me feel hungry as an appetizer rather than full like other snacks did. If I needed to lose weight the recommended practice based on how I live would be 4 meals a day and never snacking.
The way gaining or losing weight works is simple, it's calories in versus calories burned. For some people snacking, so long as it reduces how much is eaten at meals, increases calories burned by a significant amount. Therefore keeping them at a lower weight. For others it doesn't have that effect, and usually it's because those people eat a consistent amount in their meals regardless.
Usually p hacking doesn't come from 1 constraint, especially a well explained one, but instead comes from adding a couple or completely unexplained constraints (like a team losing more if their coaches wife is in one section of the stands or another) because at that point it's decreasing the number of samples (times you have as a reference) to force a significant result.
So usually for sports p hacking is stats about 1 team only, rather than a general stat about the sport. Preferably a restriction on the other team, then a follow up game based restriction so it seems plausible to the viewer.
I mean what I have is multiple database files I mean I just have multiple databases in use for that. I have my accounts, a "shared with partner." and a "friends" database. It works decently well just have to set default for passwords to save on mine, and then use sync thing to sync between my devices to the home pc, and just Google drive for others.
To add to the other response - it is much more difficult to work with Ai to debug inconsistent issues or similar unless you can understand the code and step through with a debugger to check for race conditions or similar.
Recently I was working with an Ai tool for some c code that depending on machine ran wildly differently. The Ai was unable to identify any issues, and kept recommending fixes for hardcoding values or similar that I had to revert. The fix ended up needing to use valgrind to create a different enough environment to see how a race condition was made to properly have one async call delay for the other.
AI can be powerful, and humans can be dumb. But if the code was human made, I would not have needed 3 hours to find a problem, and I wouldn't have tried to turn to AI for a simple fix because I'd know what I was looking for to start with.
But you're forgetting the key difference that makes it so much worse - we can fix human mistakes especially if we can talk to the human to figure out how. With an llm we have no external reference, only poorly designed code where the comments are there to guide the writing, not describe what was written. So it's much harder to debug an output, and the llm cannot be trusted to clean it up either.
Having worked food service, it means your restaurants didn't get bad ingredients and such - I've had in receiving calls back and forth from the kitchen about what is 86 for now. Usually "salmon warm, 86 salmon" . Which would get a call back about what other stuff is supposed to be thrown out with it. "86 the peas they won't make next shipment."