No, it's more likely that girls and women learned to mask symptoms early for survival reasons.

If you look at hunter-gatherer societies, ADHD is paramount to survival because it avoids over-harvesting. Too little ADHD produces cultures prone to driving plants and/or animals extinct. ADHD is a critical stop-gap that prevents this. Studies show ADHD gatherers will not only collect more, they will do so in ways that cause far less damage, resulting in a far better second harvest and far better sustainability.

Into more modern times, ADHD was a valuable survival trait. Too little and you became vulnerable to diseases, pests, crop blight, etc. If you wanted a stable population, right the way through to the industrial era, you needed a high level of ADHD in the population.

It is only when neurotypical bosses decided that they had to micromanage everything and decided who lived and who died on the streets that you see ADHD symptoms suddenly and massively suppressed. But masking changes nothing. The levels will still be the same, they're just hidden.

It isn't. The under-diagnosis of girls is astronomical.

You are assuming ADHD is a new thing. No, it isn't. It is a survival thing. ADHD was critical in a very large percentage of the population for the bulk of the last 350,000 years. Without it, humanity would have gone extinct. It's merely not appropriate in a world in which neurotypicals make neurodiverse solutions a "bad thing".

They might drop by a little, but honestly not by much. Boys are mildly overdiagnosed for the reasons you give (but few places still medicate), girls are however massively underdiagnosed.

I never got myself into the whole "masculinity" obsession, even back in the 70s and 80s. The result of this was a discovery that computers launched me head-first through far fewer windows and pelted me with far fewer rocks. So, yeah, I was definitely seen as disposable though my childhood and teen years by pretty much everyone. (It's one reason anyone looking back at those as "golden years" is unlikely to win me over.)

Escapism is pretty much all I had at the time, and these days remains pretty much all I have - reality has grown far worse over the years and knowledge by the neurotypicals has not come with empathy but ammunition. There is guilt and shame in playing with creative writing or inventing, and the demons have got really bad on occasion, but you're right, it's not doing anyone any harm.

Both. It's best thought of as a positive feedback loop.

The algorithm seems to have been failing to scale correctly, yes. On closer inspection, it looks like the billing software treated the bytes used as K used.

Did AWS use Grok to generate the billing sheets or the code for handling billing?

I'm serious. The errors reported look suspiciously like AI hallucinations or a signed integer being treated as unsigned.

These platforms are starting to let people bet on wildfire activity. What a fun way of incentivizing arsonists.

a human doesn't "train" on a novel, because training implies learning to duplicate its structure.

Wait until I tell you what's happening at thousands of college campuses across the nation!

What an amazing non sequitur. You might as well have said, "But humans have hair, and LLMs don't."

Most US population centers are in places east of the point in their time zones where the sun is overhead (or due south) at noon, and being a bit west is better than being a bit (or very, for New England) east. This means that DST is mostly the right UTC offset for the wrong reason: Boston should be on Atlantic Standard Time year-round, but Eastern Daylight Time is a name for the same clock setting that is already used there sometimes, so that's easier to legislate. Of course, the people who live west of their true noon line don't think permanent DST would be good, but the fact that we should have no DST and a different map is too nuanced for the position that there's got to be a single simple answer as to how to fix everything, regardless of the situation.

You're conflating your emotions with facts, in a field you very likely know very little about.

Always anonymous, always cowards.

Good question. Their POWER series of CPUs were not insignificant in capability, their chip designers were clearly technically sophisticated, and GPUs are just specialised vector processors with a few extra bells and whistles - stuff IBM is extremely familiar with.

It would not have been difficult to release a GPU or other LLM-specific processor to go along with the POWER11. They'd been working on the POWER11 for 4 years, they knew in 2020 that LLMs had a strong potential to be significant for Big Data processing - an area you use big iron for, they're not rank amateurs, they have plenty of reserve, they could have assembled an emergency team to build a vector processor that was custom-designed for just LLM work, and released an LLM processor card that could run circles around nVidia.

They didn't. Because, as has happened before, their management is simply too stupid and too slow.

What if...

Someone (say someone who was familiar with doxygen and GCC) developed number of comment types, where some stipulated preconditions that must be true for the function to run correctly, postconditions that must be true once the function has run, kernel facilities that the function definitely needs, and kernel facilities that the function definitely doesn't need. These would all be optional for any given function.

A static checker could then validate if the code meets the behaviour expected by the programmer. This is precisely what is done in SPARK, a fork of Ada for high-reliability code. Combined with existing static checker capabilities, this would greatly increase the number of bugs that could be caught with all kinds of tools, AI included.

It could ALSO build a full fine-grained mapping for any fine-grained mandatory access controls system. You'd also want includes that you could import for precompiled libraries. This would allow someone to verify if the code was making unanticipated/undesirable calls but would also make SELinux possible to develop for at the application level.

It would not be trivial. If it was trivial, it would have been done simply because it already IS done in other languages and that makes it "obvious" to anyone who has been programming for a while. However, it should not be massively complicated, simply because you can use AI as the static checker. Once it has a definite set of bounda that must be satisfied, it should be much more capable of knowing what paths would violate those bounds. Which means that the checker stage essentially is trivial today, leaving only the markup stage.