> And the people they're both making money from, are people who think they have enough expertise + exposure to function as superforecasters — and who probably could function as superforecasters, in a market with fewer "sharks" in the pool — but who lose out simply because they were slightly less well-calibrated than whoever they were trading with.
This seems like a complicated way to say "suckers". Of course they don't usually self-identify as such and think they act rationally.
In 2008 I was in high school and wrote a TI-BASIC tutorial in German [0] on my blog that became by far the most popular thing I wrote - maybe on par with my post about how to fix a quest bug in Skyrim by teleporting Delphine.
I was a bit mad back then that people for some reason appreciated those posts more than many very deep teenager ramblings about politics/philosophy :D
I have to say that intuitively I wasn't at all surprised that duplicating a single layer didn't do much good, but I had never expected that you can identify and so clearly visualize these relatively short circuit blocks (and of course it's around the magic number 7! /jk). Super cool research and really well explained!
The response you link to was published on September 30, 2025, so it's not the response to gem.coop? I'd say gem.coop is the response to Ruby Central's actions?
If it weren't effective, large businesses and interest ("lobby") groups wouldn't spend millions on trying to establish certain words.
Calling it "sideloading" instead of "installing" software successfully cements the notion that it is somehow not a completely normal thing to do. That's problem solved for the Googles and Apples of the world.
You are looking at LLMs for code generation exclusively, but that is not the only application within software engineering.
In my company some people are using LLMs to generate some of their code, but more are using them to get a first code review, before requesting a review by their colleagues.
This helps getting the easy/nitpicky stuff out of the way and thereby often saves us one feedback+fix cycle.
Examples would be "you changed this unit test, but didn't update the unit test name", "you changed this function but not the doc string", or "if you reorder these if statements you can avoid deep nesting".
Nothing groundbreaking, but nice things.
We still review like we did before, but can often focus a little more on the "what" instead of the "how".
In this application, the LLM is kind of like a linter with fuzzy rules. We didn't stop reviewing code just because many languages come with standard formatters nowadays, either.
While the whole code generation aspect of AI is all the rage right now (and to quote the article):
> Focus on tangible changes in areas that you care about that really do seem connected to AI
If you don't break hard enough, it might still be the recuperation doing its work.
Car producers can and do resolve this, e.g. iirc Audis don't use recuperation for the first breaking of the day. That way you don't have to remember to use the no-recuperation/break cleaning mode or break unnecessarily hard every now and then.
We are talking about national gold reserves, not some household items.
They exist for the reason to liquidate them in case of national emergencies/severe economic crises.
It's easier to liquidate these reserves when they are stored in trading hubs. That could be New York and London, or maybe even Shanghai, if China wasn't a systemic rival.
Storing all of them at "one's place" is a larger risk than splitting it up and storing them in several places, each with a different risk profile.
Heh, given the title I initially thought SentinelOne was addressing the Chris Krebs situation, and the adversary would be the current administration.
But it's about different nation state actors.
They answered your question "are there any issues that you think should be decided by men only?"
In this sentence, you are looking at different parts of the equation depending on case 1 and 2:
> Apparently men ought not to get a say in "women's issues", but it is also right that men be forced to put their lives on the line.
No, in the first case it could be argued that men shouldn't have a say, and in the second it could be argued that women shouldn't have a say. In the first case women are (potentially/allegedly) negative affected, in the second (young) men.
> Can you think of a female equivalent where females are ordered by the government to put themselves in harm's way?
Anti-Abortion laws in the US would be such an example.
"Don't piss off Poland?!" There won't be a large scale war against the Eastern EU started by Russia that does not involve Poland. The EU has stronger mutual defense clause than NATO article 5+6 (of course, it doesn't have anything close to the military might of the combined NATO countries). Once there is an all out war, Finland would mobilize its army, threatening Russia's northern flank. The Baltic would be closed. The black sea would be closed. All out war would be terrible, but the deterrence is still too strong in my opinion, as the price would be too high.
The problem / question is what would the EU (or NATO) do, if Russia starts a small scale hybrid war against Estonia or Latvia. Creating a small "local" insurgency, that takes over a majority Russian speaking town on the border. If the military alliances do not react united in such a case they are done.
If I interpret [1] correctly, then they still have a criminal record?
"Please also be aware that if you were to be granted a presidential pardon, the pardoned offense would not be removed from your criminal record. Instead, both the federal conviction as well as the pardon would both appear on your record."