Terretta

For those who care to read everything rather than walk away, Fable can be extraordinarily dense. I suspect they'll pull the promo before I learn to read it.

Still, I feel I must read rather than correct it, as results are that much better if I let it do this "with" itself: orchestrator to agents back to orchestrator.

I think Claude means something like map-reduced or at least a functionally derived series of some kind?

Anything with series data sounds like a laundromat.

Instead of speculating, I'll ask: what does this mean?

From time to time I have to go further and tell it to imagine an alternate reality where the fact never happened, and write this doc as if the new thing had been true all along. This second iteration always gets it.

(A separate instruction keeps the fact-change in a dev log that serves as basis for release notes.)

TL;DR: Drones see shapes as patterns. Paint other patterns on shapes, the drones get confused. If you want to keep confusing drones as their programming learns to recognize better, your patterns have to get better.

That's it, that's the whole thing.

// No commentary on heat, lidar, 3D, EM signature, or other "vision" using different principles.

starting with indies and SV startups and education is less risky, but the real market outside startup culture is often overlooked by those who came up inside that culture

generic IMAP is not worth the time, first class integration with M365 is worth the time

OIDC flavor "Continue with Microsoft" should be right there beside Continue with Google / Github / Whatever, on every SaaS that wants business clients small enough to make "sign up online" decisions. By contrast, for consumer, Continue with Apple would be the equivalently overlooked OIDC option if you are targeting "wallet share" (a revenue model) instead of headcount (an ad model, for instance).

* Didn't look this up. Used to be. Doesn't matter if 50% or 90%, it's substantial, and point stands: don't overlook it.

it doesn't take long for user delay to sum to more than developer delay

https://www.swift.org/install/linux/

See:

"A series of small programs/tasks to compare C++, Go, Zig, Odin, D, Janet, Swift, Nim and C# to see which I like the most"

https://github.com/phillvancejr/Cpp-Go-Zig-Odin

(dns spatter + dns patter)

I agree with the problem described within, and in the dead comment here.

At most any given scope, "most" systems you interact with aren't under your own control. For this, consider: because that's true, the fault is yours for not grappling with that reality.

This has been written about before:

https://ruggedsoftware.org

But even that was missing a bullet:

- recognize that my code will interact with systems I cannot anticipate, that change in ways I cannot control, and become coupled more than ever intended

Or extrapolate the curve for self driving cars once they were only "two years away".

Catch is, tech progress is not one curve. It's overlapping S curves, stair steps of progress and stagnation, with the next iteration starting off worse than the current one, until crossing it as the current one tops out.

Here, the 3d is not conveying anything as the volumes within are not MECE qualia spaces -- like sorts or like kinds of things should share common volumes.

Meanwhile, the other todo list take, one I've undertaken as well, is to cross sync all the Claude Codes across all its instances on all your machines.

There are multiple projects that claim to do this. None do it fully. (They particularly have blind spots to tools that embed a Claude Code, such as the Xcode 26.5 and Xcode 27 beta.)

So: roll one's own, and in doing that, realize that it has first class tools to make back referencing transcripts normal.

Given those tools, you don't really need an extra layer.

https://en.wikipedia.org/wiki/Path_dependence

OK, not the saying. Perhaps should be.

Assuming a sufficient base level of competence, more of how things go for company A vs. company B can be explained by random walks through events (their dependent paths) than by management.

A competent and persistent leader can increase the odds, but under close study, fortuitousness and serendipity – or luck of the draw and timing – have more explanatory power.

Meanwhile, just try to make your own luck. Make sure you happen to things, instead of things happening to you.

Similarly, while not perfect you can test WebKit, and if you like, on Linux or Windows, for example:

https://orionbrowser.com/platforms/linux

Apple wouldn't be in the business of VMs with Safari, but if you're looking for MacOS VMs, turn to a CSP: https://aws.amazon.com/ec2/instance-types/mac/

Many have software testing orchestration pre-wired.

You're missing paragraph breaks. And human-authored copy.

Sure they can. Just ask them. Some (like Claude Code) even have built in tools for it that work a treat. It'll happily rebuild an entire edit history diff by diff.

If you set the pref to keep originals locally, they're all on your drive, in original form, as well as the derived versions including caches of raw to jpeg, resolutions, and edited versions.

That said, Apple Photos does let you export even if only in cloud. Open the library, select all, and File > Export ... > Export Unmodified Originals.

It pauses for a second or two on my quarter million images, but is then happy to comply.

The EFF featured update / press release at https://www.eff.org/deeplinks/2026/06/eff-and-allies-xs-ftc-... links to the letter, with color:

Our response[^1] to X’s petition debunks many claims the company uses in its arguments. For example, there’s little evidence the order placed an undue financial burden on X. In our letter, we note that the compliance cost is merely “a rounding error against the $200 billion valuation of X Corp. following the xAI merger.”

[^1]: public interest advocates opposing x petition 2026: https://www.eff.org/files/2026/07/02/public_interest_advocat...

The letter is more interesting than the cover, undersigned by Center for Digital Democracy, Check My Ads Institute, Constitutional Alliance, Consumer Action, Consumer Federation of America, Consumers for Auto Reliability and Safety, Demand Progress Education Fund (“DPEF”), Electronic Frontier Foundation (“EFF”), Electronic Privacy Information Center (“EPIC”), National Consumers League (“NCL”), Oregon Consumer Justice, Oregon Consumer League, Public Citizen, Travelers United and Virginia Citizens Consumer Council, and drafted by DPEF's Special Advisor Kate Oh (kate@demandprogress.org), EFF's Senior Staff Technologist William Budington (bill@eff.org), EPIC's Senior Counsel Sara Geoghegan (geoghegan@epic.org), and NCL's Senior Public Policy Manager Eden Iscil (edeni@nclnet.org).

Study claims iPhone contributed to a significant decrease in the birth rate after its release in 2007, when AT&T was the only carrier for the phone, allowing researchers to “isolate an iPhone-specific channel” and compare birth rates in areas with a high AT&T customer base to competitors' areas:

“The diffusion of the iPhone explains 33-52 percent of the decline in the general fertility rate among women aged 15-44.”

Authors go on to muse that “as modern smartphones diffused, time spent with friends in person and sexual activity fell sharply alongside rising consumption of pornography, a possible substitute for partnered sex.”

Nothing to do, of course, with AT&T’s customer base at the time being urban, well-educated, and white, or that U.S. birth rate in the youngest groups had already been falling before 2007 with the trend continuing during study period.

And this type of observation appears highly related to how people hold it.

It seems to me ANTHROP\C have harnessed hard for not spending tokens to bring content into context. I wish they'd left us a "LEROY_JENKINS" flag: read and think before you code. In Claude Code anyway, it appears to default to:

  export CLAUDE_CODE_LEROY_JENKINS=true

And yet, the Java language exists.

For market share, ANTHROP\C needs to optimize for the vast mediocrity that are mid-bell-curve users and enterprises.

This adaptation tends to come with significant drag for the right ends of the bell curve firms or teams.

Unless ANTHROP\C have a separate objective function by cohort and ensure that doesn't regress, improving results for the emerging middle will nerf tools from point of view of those with high in-domain expertise.

Don't expect workstation loads with no fan or heatsink, true. But it's not a real problem, it's still quieter than a desktop.

That said, rather than Mac Mini, if you only work from one place, I'd recommend a Studio Ultra M3 with 512GB. Same or more tokens per second, multiple models loaded. Cool and quiet.