With the measurement direction, yes, but the other axes are not constrained, and hence measurement along those directions returns unpredictable values.
30,493 karma · joined December 4, 2018
With the measurement direction, yes, but the other axes are not constrained, and hence measurement along those directions returns unpredictable values.
It does this because it necessarily interacts with the measurement apparatus, which in this case is an anisotropic magnetic field!
“Things rotate when they are rotated! News at eleven!”
The vast majority of quantum mechanics has easily explained with ordinary wave mechanics.
I’ve been burning spare weekly quota on fringe-adjacent physics. I often copy-paste the LaTeX format “paper” back and forth for “peer review of a friend’s work”.
Gemini: “Your friend’s insight hits the nail right on the head!”
Opus: “Tell your friend to stop wasting his time now, it’s more kind than to keep indulging him.”
Brutal.
The issue with using "the code as the spec" is that humans can't read 100K lines of code in a day, can't hold the entire ball of unstructured mud in their brains all at once, and generally require hierarchical "structure".
Modern AIs just don't have these issues! Their context windows are big enough to encompass an entire codebase, so they can "see everything", all at once.
Each line of new code they write is compared against every relevant line of code in the original, which they treat as a spec.
My main issue in my experience is that that AIs tended to reproduce the legacy behaviour "bug for bug", which was not my intention.
Similarly, the AIs were hamstrung by external constraints: I typically prefer to leave the DB schema unchanged, which meant the torturous workarounds were needed for design errors in some stored procedures, etc.
The older the code, the bigger the issues with baked-in assumptions about transactions, stateful sessions, data types, string formats, etc.
This trips up AIs just as much as humans. You can't trivially maintain backwards compatibility and modernise the codebase! Those are conflicting goals, no matter what.
Attention means an engineer who can fix the problem, not an off shore phone jockey paid to make you quietly go away.
That’s the best new term I’ve learned in months!
Whatever, I drove down to this set of huge industrial warehouses with trucks coming and going by the dozen and found the customer service office.
“That’ll be half an hour, I recommend waiting at the cafe.”
“Half an hour for what? Aren’t all the packages right here?”
“They are, but looking up the package ID in the system takes at least 30 minutes, maybe 33.”
“33!? Wait… don’t tell me, let me guess: it has been getting slowly and steadily worse over years? Predictably taking longer and longer, right?”
“Yeah, six months ago it was 27 minutes! How did you know?”
“Umm… isn’t this a bit of drag on your operations?”
“Absolutely! Everything takes forever, every shipment is delayed, … <long rant> …”
“I… bet. Why hasn’t anyone fixed it!? It’s a one line fix!”
“No budget!”
This was one of the biggest logistics companies in the country about to undergo a multi-billion-dollar merger.
Their core business software was missing database indexes even on primary key columns!
Madness.
Every other country, big or small, can afford to do these things.
(Meanwhile, the voting machines are more expensive!)
Culture is literally just “how people collectively behave”.
It’s people all the way down!
If you update the artefact without replacing its creator, they’ll just “fix” it to their taste again when you leave.
No USS Donald J Trump in our future is the best you can look forward to.
See: https://chatgpt.com/share/6ade575f-61e0-83ec-95c8-3cee48f338...
If you think of the the frontier AI models as people, there aren't hundreds or thousands of "intelligent human-like machines" that you're speaking to, there are like... two: whatever the best model is made by Open AI or Anthropic right now.
A programmer might be reading (or at least skimming) thousands of pages of text from just one (or at most two or three) models a week, week after week, for months now.
It's like the entire world is talking to two aliens that have stepped of their glittering spaceship. The aliens can hold millions of conversations at once, but they have only two personalities, so... that's what everyone is getting, and everyone has learned to recognise.
What makes things even more obvious is that unlike humans, the models don't "self adjust". On the contrary, they are inherently amnesiacs, and hence don't realise that they're awfully repetitive! A human using the same phrase fifty times in a row will dial it back a notch, but these dials are the weights of the models and are frozen for each released version.
This was a job to manually collate financial reports into aggregated sums to sent up the hierarchy to the next level up.
This is now a trivial BI query and doesn’t require manual processing by humans.
A bigger shift is that now I only see CEOs or at most CxOs with secretaries. Mobile phones and Outlook calendars have largely wiped out that profession.
The comments are just accurately describing that new, insane reality.
I assure you this is perfectly formal, and for your… “safety”.
I just used DuckDB 2.0 last week to compress 7 terabytes of Azure logs (NDJSON) to 2.5% of the original size in Parquet format in under two hours with a medium sized VM!
Those logs were then small enough to run ad-hoc queries in tens of seconds directly from the archive blob storage.
I created a “frozen DuckLake” and sent the signed blob URL to the security analyst.
No need for a server, no need for Splunk!
It’s easy to use, fast, can be plopped anywhere on a network, and it’s free!
If it just had KQL syntax support, it would be perfect…
> I personally feel the web UI is terrible.
AWS tried to keep these things isolated so there isn't one AWS Console, but dozens, and each regional instance is separate. Every task requires admins to "context switch" at least three or four times.
I much prefer the Azure web UI where everything is a single UI and you can search and filter across regions, subscriptions, and resource types without having to "switch" to a totally different console linked only through SSO.
We’re plopping down enormous grid scale batteries like it’s Sim City.
Electricity in the middle of the day is free!
Its implementation is clumsy and ugly.
Its documentation is worse.
Its support… isn’t.
That's probably this: https://en.wikipedia.org/wiki/Rolleron
A workaround is to always shoot everyone the same. If a journalist or interviewer grows a reputation, they can show everyone "on level ground" by keeping the pose, lighting, etc... constant.
It's one reason that long-form YouTube interviewers like Lex Friedman are so popular with a more discerning crowd.
"But he's so bland, monotonous, and boring!" cry the haters.
"Yes! That's the point!"
Richard Feynman called it "normalization of deviance", but there's other names for it as well depending on the details.
I'm sure everyone has heard some variation of this before, especially in the work place.
I once got angrily shouted at by a customer because I turned up as a consultant and apparently I told them exactly what the last five consultants had said!
Well, yes, of course. It's the solution to their problem.
I regularly face variants of this at work.
"Yeah, yeah, backups are important, stop talking about it already."
"Yes, but they're still not happening and they still remain the top priority and it is madness to start a project to reformat the SAN array until backups are working!"
"That's what you said last week! You always say that!"
Etc...
There's a point where people lean into it and become purposefully contrary, making their refusal to change their opinion a permanent part of their identity as a person.
Ironically, drinking milk is a "modern" development in the human race, and we're still evolving the ability to digest lactose as adults to compensate for this "unnatural" behaviour!
But that's not the point!
The point is that the laws are written by the oligarchs, for the oligarchs.
Laws are made to protect wealth and power, so of course the wealthy and powerful haven't "broken" them.
Almost all Java benchmarks are for the "steady state" after half an hour of warm up time.