Doesn't this assume that people (in the west, at least) "perceive" paintings from left to right? That doesn't strike me as particularly true.

I thought I'd be unimpressed by the mirrored version, but I can say that for myself, it really did have a different feel to it.

I've always pictured the boats moving right, sliding down, as if surfing the wave.

The mirrored version makes it clear that, no, they're going against the wave, which makes it that much more of a scary situation!

Now, having noticed that, I see how the position of the rowers in the boat would be enough to deduce that. But still, it goes to show that (at least for me, personally, in this specific case) the mirroring really did bring a more intuitive feel for what the artist was trying to represent.

This is taught in graphic design, how people typically scan information from left to right and top to bottom, in cultures where the written language flows in that direction. However, a counter argument could be made that people perceive paintings differently from the way they read written text. There have been studies about how the Japanese perceive images and sounds with the same area of the brain that processes language, in contrast to other cultures where they're processed separately. [citaion needed]

Look up “spatial agency bias” and “glance curve”

Doesn't strike me as particularly true either.

Given how much Google lives to mash their offerings together, and then sunset them, I live in fear of them killing Google Youtube Music (or whatever it's called), in favor of combining functionality with this, and having my music cycle between my actual library, and bespoke AI-generated stuff.

If I were a PM at Google trying to connect those two products, the far more obvious approach is the end of the creation pipeline having an "Upload to YouTube Music" button.

YouTube already hosts significant factories of programmatically generated music; just look for Creators with the 3-hour or 10-hour or livestreams. For YouTube Creators, and also for Photos editors (that's everyone with an unrestricted Workspaces account), they provide a menu of background music that is "royalty-free" and so you can attach it to a montage or your own videos, to avoid awkward silences, or set the mood to vaguely sorta what you were hoping for.

So it's an evolutionary step in my view, rather than a revolution.

Down for me, but Internet Archive grabbed a copy: https://web.archive.org/web/20260424151739/https://buttondow...

I play D&D once a week with local friends.

We all met, and picked a day that was likely to work for us regularly, going forward - for us, it's a Tuesday. That way we know, and can plan ahead for the foreseeable future, that Tuesdays will be D&D nights. People with kids can get babysitters, or get spouses/grandparents to take care of them. People with other obligations can keep that night clear. Etc., etc.

I used to prefer the whole "let's schedule the next session at the end of the night", but that has 100% led to campaigns falling apart. Consistency is key.

(Also, it helps to have a big enough group - either for D&D or boardgames - that the absence of any one or even two people doesn't tank the night.)

Doing things virtually is also a good suggestion, but I'm pretty burnt out of staring at people's faces on a screen, so I hate playing D&D or other games over a screen - but your mileage may vary.

I distinctly remember Spyfall having cards...

Seconding this. It's somewhat challenging to learn, but a lot of fun once you get it.

> After all, you can still just review the diffs

anonu has explicitly said that they've wiped a database twice as a result of agents doing stuff. What sort of diff would help against an agent running commands, without your approval?

Hah I run my agent inside a docker with just the code. Anything clever it tries to do just goes nowhere.

Agent does not have to run in your user context. It is easy mistake to make in yolo mode but after that it's easy to fix. e.g. this is what I use now so I can release agent from my machine and also constrain its access:

    $ main-app git:(main) kubectl get pods | grep agent | head -n 1 | sed -E 's/[a-z]+-agent(.*)/app-agent\1/'
    app-agent-656c6ff85d-p86t8                          1/1     Running     0             13d

Agent is fully capable of making PR etc. if you provide appropriate tooling. It wipes DB but DB is just separate ephemeral pod. One day perhaps it will find 0-day and break out, but so far it has not done it.

My dad had one of these, to support his farming hobby. (He used to joke that we ate fifty dollar cucumbers, and a hundred-dollar ear of corn.)

It came in handy living in the country, when occasionally someone would get bogged down on a dirt road, and this thing would come to the rescue.

My grandpa was a high school principal to support his love of farming, not because he wasn't dedicated, but because they wanted to survive

Did your dad grow up with subsistence farmers? I also encountered plenty of hobby farmers who joke about the cost of their hobby which used to get me confused a bit since it was very much a food on the table thing for my grandparents and at least a small financial bonus to me.

Then again I don't buy much new other than seed. Everything feels like a ripoff nowadays.

That part was genuinely the least plausible part of those books to me.

I think about half the IDEs I've ever used just had this as a feature. Right-click on function, click on "change signature", wait a few seconds, verify with `git diff`.

I actually still like LLMs for this. I use rust LSP (rust analyzer) and it supports this, but LLMs will additionally go through and reword all of the documentation, doc links, comments, var names in other funcs in one go, etc.

Are they perfect? Far from it. But it's more comprehensive. Additionally simple refactors like this are insanely fast to review and so it's really easy to spot a bad change or etc. Plus i'm in Rust so it's typed very heavily.

In a lot of scenarios i'd prefer an AST grep over an LSP rename, but hat also doesn't cover the docs/comments/etc.

Shouldn't the LLM have some tool that gives it AST access, LSP access, and the equiv of sed/grep/awk? It doesn't necessarily need to read every file and do the change "by hand".

I linked this elsewhere but, the agent could have a skill to use https://ast-grep.github.io/ to perform such mechanical code changes

That's correct, though you'll still end up needing more than AST/LSP/etc for the same reason AST/LSP/etc isn't enough for me (the human lol), ie comments/docs/etc.

yeah, and this has the advantage of both being deterministic, and only updating things that are actually linked as opposed to also accidentally updating naming collisions

Arguably its only a matter of making lsp features available to the coding agent via tool calls (CLI, MCP) to prevent the model start doing such changes "manually" but rather use the deterministic tools.

Part of why I'm not terribly fond of CLI harnesses, and prefer ones built into editors like zed. They can (but sadly rarely do) access structured information about your codebase, that's more sophisticated than looking for all strings that match