Because your company makes you use Azure Virtual Desktop to connect to a VM and AVD's clipboard handling is as unreliable as anything else from Microsoft?
Jesus_666
Problem is, if your slang is too new it looks like gibberish. Of course you could try something else that stands out. Like badly translated idioms.
But it's probably jacket like pants. Even if you tear your ass open to make your writing look less 08/15 that doesn't mean everything's in butter. It's probably only a matter of time until LLMs will copper off that style as well and your clever plan turns into a zero number. And that's where the hare lies in the pepper: Your clarity goes over the Jordan and it ain't itching the LLMs' bean. It'll get trained on your stuff anyway and the cat bites its own tail.
Maybe bad translations aren't the solution either.
The same happens to people who write a lot and pay attention to their style, such as this gentleman. The way LLMs generate text is strongly influenced by what used to be considered a high-effort eloquent style. Varied sentence lengths, triplets, typographically correct punctuation, yada yada yada. Until recently, that stuff used to be the hallmark of professional writers (and Kenyans, apparently).
What were LLMs trained on? Professional writing, first and foremost. Books, scientific papers, op-eds, blog posts. So by default they take a polite, professional tone with all the flourishes and best practices that previously used to be de rigueur for authors and the like. So now what happens when someone used to "proper" writing writes something?
Everyone thinks it's AI slop because that's how LLMs talk. High effort now looks like low effort. And because tech bros immediately went on to develop "humanizing" tech, any other style will soon also look like low effort. And the same is true for art: Being able to produce highly detailed pictures with spectacular colors and shadows went from something impressive to evidence that you're just a random jackass with a ChatGPT subscription.
You can't really win anymore. Anything short of a live performance or a feature-length movie could feasibly have been generated by a fully automated content mill. That really sucks if you want to engage in creative expression of any kind and doubly so if you once thought you could make a living off of that.
I'm pretty sure that if a judge would grant that injunction there'd be one less a week later.
This would be a great time for an injunction to force the data center to shut down all of those turbines until the matter has been resolved legally.
Of course you need to be able to pay for a lawyer who convinces a judge to pass that injunction.
The diagram is not comparing between two standards but between two sizes within the same standard. Philips size 0 (PH0) has a slightly different shape than Philips size 1 (PH1) and up.
Note that according to hardware manufacturer Tekton, the differences are smaller than you think and especially the diagrams are highly misleading as they actually compare PH2 and PH0.
Just about the only major difference is the thread pitch and that is only different in JIS screws if they don't have the dot.
And if you went for the color depth because your graphics accelerator could do HighColor at 800x600 you had to decide between 15-bit and 16-bit colors.
Speaking as sometime from Central Europe, rain in winter is very much accurate. Typical Christmas weather is light rain at two degrees above freezing. When it does go below freezing in winter it's usually relatively damp air with no precipitation so there's no fun snow but a cold that becomes painful within seconds if you don't have much body fat.
Even a full week of 43 °C wasn't quite enough to make me like summer less than winter.
A business is under no obligation to ensure that employees in underperforming departments get the star treatment. If agriculture-oriented rural towns generated as much money as grifting the stock market with AI does they'd be treated accordingly. As it is they're a cost center and will be neglected or cut entirely.
That's not how a country is usually run but for a business it's very much on par.
I recently helped evaluate it for company use. My test considered of vibecoding an App that takes a Pipewire screencast and does some basic image processing on each frame. In C#, which doesn't have great options for talking to Pipewire. I did several runs with various iterations of Claude.
On the upside, it had few problems navigating DBus to negotiate a screencast handle. So that's one annoying API out of the way.
On the downside, all attempts at taking to libpipewire through P/Invoke failed, usually because Claude hallucinated parts of the API or set constants to incorrect values. I only got a working program when I allowed the use of a prerelease Pipewire NuGet package.
The generated code was of acceptable quality but I wouldn't allow it into a codebase without a refactor. The code has zero consistency and one time the whole solution didn't have any namespaces. The fact that the LLM writes and rewrites the code during a single prompt means that you can get mild spaghetti as an initial state.
Honestly, I can see it for something like rapid prototyping or implementing basic scaffolding for an annoying API. But damn is Claude bad at detail work.
They should've hired tea industry execs. If the tea industry can come up with grades like "Special Finest Tippy Golden Flowery Orange Pekoe", they can come up with something beyond Ultra High Definition.
Maybe like this:
Not that these grades would only apply to displays that don't support picture-in-picture or split screen. Displays with those features ("broken" displays) would use the following equivalent grades instead: