Applying this "strict reading" would that mean the majority of chrome extensions are violating copyright. They would not be allowed to modify the DOM to translate web pages, to add price history, check for coupons, etc. as they all modify the original creator's "program"?

Yup. Copyright and intellectual property are utterly absurd.

It was created whole cloth as a legal fiction to prop up an industry that the legislature thought was worth propping up.

If you think about it, if search engines didn’t exist, and you invented and marketed one today, you’d be sued into oblivion. Same goes for public lending libraries.

Mine "thought" for 8 minutes and its conclusion was:

>So the “best possible” plan is: sit still all summer near a pole, slow-roll around the pole through equinox, then sprint westward across the low latitudes toward the other pole — with a peak westward speed up to ~1670 km/h.

Is this to your liking?

well no, thats where it gets confused. as soon as you sail across to the other pole you are forced to go up to a speed of 1670kmh.

when models try to be smart/creative they attempt to switch poles like that. in my example it even says that the max speed will be only a few km/h (since their strategy is to chill at the poles and then sail from north to south pole very slowly)

--

GPT-5 pro does get it right though! it even says this:

"Do not try to swap hemispheres to ride both polar summers. You’d have to cross the equator while staying in daylight, which momentarily forces a westward component near the equatorial rotation speed (~1668 km/h)—a much higher peak speed than the 663 km/h plan."

I don't really understand gpt5's reasoning? does its soln not cross the equator ever? b/c if you cross you always have to do it in daylight so it's kind of strange to say that no? or it means you have to cross it on boundary of daylight or something

oh like its solution is to stay in one hemisphere and just go in a circle following the day-night cycle i guess. but I don't see its reasoning as that rigorous that crossing must need this westward speed but probably i'm being dumb

I guess one has to check that if you are spinning around at 23.5-epsilon angle and then do the dash down the 23.5-epsilon angle in one day from the other side you cannot beat your speed of staying in one hemisphere. you could dash straight down in 12-hour timeframe and it'll need like 343 m/s or 1233 km/h which is much too high. and diagonally probably doesn't help too much? But I think it means at some tilt angle it's worth doing this? does GPT5-pro know this angle?

you include the tilt of axis I assume? Is the best solution of yours rigorous out of curiosity?

I found if you are tightly in the loop, keep the code highly modular, and are developing new functionality alongside tests, Claude works much better.

Yeah me too, keeping the code modular being a huge part of it. In the same vein is actually finishing feature flags and removing the old code, killing off truly dead code, tests, documentation… basically eliminate as much noise as you can, so that it reads as much exemplary code as possible.

Good point. I tell Claude in the claude.md to use a linter and formatter which helps it get rid of its own dead code while it develops.

So there is nothing one can do to increase their odds of success? If there is, they can't write a book about it?

Thank you for sharing this. It’s an angle I didn’t explore, and want to now.

I wonder if changing your language every 5-10 years and/or location would help in sort of forcing a dictionary change.

I really appreciate you taking the time to share your wisdom. This hits home because I often catch my mind thinking about a background problem (or anxiety) instead of being present. I would like to try being more present and see how it helps.