My first use of the internet was dial-up e-mail only exchange via UUCP to a local BBS that exchanged mail every 6 hours (might have been 4), and so to be as effective as possible, I'd prepare all my e-mails including mails to the e-mail<->web gateway at CERN so I could exchange a big batch right before the time slot. Often their exchange took long enough that if I sent the messages to the CERN bot first, I'd get the response included when I downloaded the replies after they'd exchanged with their upstream. Then I had a 6 hour window to figure out what to include in the next batch...
100% with you that how you access something can add constraints and stress - in my case there while we paid per minute, the big factor was the time windows. To maximise utility you wanted to include something useful in as many of the exchanges as possible.
With Claude Code as it is now, I often clear context more often than ideal because it will drive up cost. I could probably add a lot more details to CLAUDE.md in my repos, but it'll drive up tokens as well.
Some of it I'll still do because it affects speed as well, but it'll be nice not to have to pay attention to it.
100% with you that how you access something can add constraints and stress - in my case there while we paid per minute, the big factor was the time windows. To maximise utility you wanted to include something useful in as many of the exchanges as possible.
With Claude Code as it is now, I often clear context more often than ideal because it will drive up cost. I could probably add a lot more details to CLAUDE.md in my repos, but it'll drive up tokens as well.
Some of it I'll still do because it affects speed as well, but it'll be nice not to have to pay attention to it.