This issue of Pythoness Perspective was sent to newsletter subscribers. Browse all issues
Pythoness Perspective
Use the tool, or close the tab
- From
- Amanda Nelson · Pythoness Programmer
- Reply-To
- help@pythonessprogrammer.com
- Sent
- Authors
- Amanda Nelson

Sovereignty. Use / don't use. Audit residue in one container. Once you share the work, the experiment is not private.

Welcome back. If this is your first issue: hi — I'm Amanda.
Independence is the Fire Horse's other gift. It does not lease its memory to a vendor and call it a second brain. Charging forward is not the same as handing over the hearth.
Use the tool, or close the tab. Residue you never looked at is still a lease. Once you share the work, the experiment is not private.
August closer. We myth-busted last year. This month we practiced hygiene in containers: friction before you prompt, a named place for one job, desk before making. Last week, Hank Green was the public case study: the words can still be yours and the thinking still rented.
Today is sovereignty — the unsexy part, and the one that actually keeps you a person.
Three questions, asked on purpose:
When do you use AI, and when do you opt out?
What residue is still sitting in your containers — and when did you last look?
If you share the work, what did your audience just receive — and did they consent to the workflow?
Using these products is optional. Opting out is not a moral failure. Checking a container is not paranoia. It is the same muscle as July's tech boundaries: name the line, then look at it again.

~3 min read
This week: Sovereignty. Use / don't use. Audit residue in one container. Remember: AI use impacts others when you share, and it is not always neutral.
Try today: Open one AI tool you actually use. Find memory, custom instructions, project files, or "what I know about you." Delete or rewrite one thing that should not still be there. Then ask: would I tell a reader this was in the workflow?
Opt-out is a valid setting. Hands and messy art still win. How you spend time with the tool matters more than a purity pledge.
🔥 Fire Horse (Lead with Independence): You do not owe the product your inner life — or your audience a surprise.
Foundation: AI Myth-Busting
Hank, again: this is not a private hobby
We have had free public LLMs for about three years. Long enough for an unspoken rule to settle in: of course nobody serious is using it — except the people quietly using it for research, outlines, "just Gemini Notebook," just a summary, just a first pass.
It reminds me of trying to boycott Amazon. Factor in AWS and you have very little internet left. Even if the app is not on your phone, you still spend money there because they bought so much of the competition. Purity is a feeling. Infrastructure is a fact.
So I am less interested in a show trial about whether Hank "cheated" and more interested in the three things his week made obvious:
If you share the work, the workflow touches other people. Listeners, readers, clients. They came for your digestion, not the model's. A phrase that sounds slightly uncanny — Inc. noted the backlash started with I appreciate the pushback — can alienate them before you ever disclose a tool.
It is not always neutral. Research aggregation is still a point of view. Gemini Notebook (or any "eat these sources" wrapper) can hallucinate, flatten, and invent a confident sentence. Last year's Myth-Busting still applies: hallucination is not a cute bug. Verify. Or do not ship.
Outsourcing thought hinders creative processing — not only the rusty-skill problem of "I forgot how to outline." You skip the week on the desk. You skip the argument with the material. You skip the container that would have held the thinking at human speed. Kackie asked when we signed the contract that more, faster is what everyone wants. Artlust said the Luddites were defending process, not smashing looms for fun. I agree with both: the question is how you spend the time, not whether you can pass a detector.
Hank's own comment and video are worth sitting with. This is why the example belongs in AI for Everyday Creativity. We will remember it. Use it as a speed bump, not a pile-on.
When to enter a machine container — and when to stay analog
Choosing to use AI is choosing to enter a machine container. Choosing to walk away is staying in the slow world on purpose. Neither is a personality. Both are settings.
Enter it (maybe) when the job is sorting, naming, rubber-ducking, or checking a draft you already made with your hands. You still do the 3-question check: What am I asking? What do I expect? How will I verify? You still need last week's exit test: verb, target, context. If the sentence is still a blurt, you are not ready for this container. Stay on the sticky.
Stay analog when:
You are dysregulated, lonely, or bargaining with the box instead of sleeping
The thing you need is tactile (sketch, walk, dough, a note on the desk)
You cannot say the ask in one sentence yet — that is a desk container, not a prompt
The output would ship faster than you can stand behind it — or faster than you would disclose the workflow to the person reading it
You simply do not want a machine in the room today
Opt-out does not need a manifesto. Close the tab. Pick up the analog thing. That is the creative workflow. Independence is refusing to let generate-speed become the default pace of your mind.
Check the residue on purpose
These tools keep scraps — custom instructions, memory, uploaded files, old project threads. "It knows me" is a marketing line. What it actually has is residue sitting in a container you did not mean to keep open. Residue steers the next answer. Residue is also data.
A named thread is a wall around your attention. An unnamed mega-chat is fire going everywhere, still burning last March into this week's caption. Auditing is not neat-freak file management. It is looking at the wall and asking whether it still belongs to you.
A small audit (15 minutes, once a month — pin it next to July's boundary check-in if you want):
Open memory / custom instructions / "about you."
Ask: would I still write this on a sticky and stick it to my monitor? If not, delete or rewrite.
Close or archive threads that mixed projects. One job, one container.
Note who owns the data. If you cannot tell, treat that as a take.
You do not need to zero out your life. You need to stop letting last March's spiral write this week's caption.
Close the month with your hands
Your brain and your hands are still the most powerful tools you have. Physical, messy art is how you keep your feet on the ground. Using AI is optional. Staying embodied is not.
If August only leaves you with one line, take this one: philosophize your tech use — including the choice to not use it, and the honesty to say how you spent the time if you did.
Your tech struggles, reflected back. Got one? Send it in.
This week's sovereignty check:
When do you use AI, and when do you opt out?
What residue is still sitting in one container — and when did you last look?
If you share the work, what did your audience just receive — and would you tell them the workflow?
What analog thing will you make with your hands before September?
Hit reply. I read every one.

What's next
September is Back-to-Basics Tech Skills — passwords, files, knowing when to ask for help. Fundamentals, not hustle. Live returns later in the month (details in the first September issue).
This week: context audit + something messy in your hands.
Thank you for reading August.
— Amanda
Resources
| Resource | Best for |
|---|---|
| AI Myth-Busting Toolkit | Myths + 3-question check |
| Aug 14 — prompting | Friction + separate context |
| Aug 21 — chat vs desk | Three containers; verb–target–context; Hank as process warning |
| Hank Green video / his comment | Primary source |
| Kackie · Artlust · Inc. | Perspectives we sat with |
| Tech Boundaries | July's lines — same muscle as sovereignty |
| Free resources hub | Guides, no paywall |
Subscribe to the newsletter → pythonessprogrammer.com/newsletter/subscribe
Browse free resources → pythonessprogrammer.com/resources
Shop → stickyspells.etsy.com
Support → pythonessprogrammer.com/support
Forward this issue to someone who needs permission to close the tab
Philosophize your tech use. Tech that works, for people like us.

This issue was sent to newsletter subscribers. Sign up to receive the next one (weekly, march–november).
Pythoness Perspective
Weekly issues, March through November only. Each month is one arc—a deep dive through a tech sovereignty resource I teach, with practical steps each week tied to the same frameworks in my free guides.


