The foundation is built. Now let's automate on top of it.

April was a lot.

Four weeks of cleaning, auditing, naming things correctly, and building maintenance rhythms that survive real life instead of just motivated weeks. We did the hard unglamorous work: the friction audit, the three-folder system, the notification triage, the fail-soft reset for days when showing up at all is the win.

And then Sunday April 26 we did it live together.

Both resources are now published and waiting for you whenever you need them — the March toolkit on coming out of rest mode and the full April spring cleaning hub with the workbook, NAA card, and event replay. Links are in the TLDR.

Now we turn the page.

May is about mindful automation — and I want to start with why this theme is personal for me before we get into any frameworks or tools.

In 2016–2017, chronic migraines put me nearly bed-ridden for close to a year. The smallest tasks felt impossible. The administrative loops of work had caught up with my body and I was stuck. I didn't get out of that by finding the perfect system. I got out one tiny script at a time — one macro shortcut, one small automation that reduced a decision I was tired of making. Those tiny wins compounded into enough energy and hope that a few years later I was enrolled in a software engineering bootcamp and landing at Zappos.

I built mindful automation before I had a name for it.

This month we're naming it. And we're expanding the framework that started as Y.O.U. into something that includes the people you're building for — not just yourself.

~3 min read

Here is what we built this month.

Week 1: Friction audit. Before fixing anything, you mapped where your workflow leaks energy. The Grit Framework check-in — Passion, Perseverance, Growth, Resilience — gave you a lens for whether a system is worth keeping. If it fails three of four, that is a design problem. Not a you problem.

Week 2: File systems. Three folders. One naming rule. Now / Soon / Reference plus YYYY-MM-DD-topic-short-context. Your file system should reduce decisions, not create them.

Week 3: Attention and notifications. You audited your channels, tightened response windows, and practiced friction-maxxing — the intentional inconvenience that gives your attention back to you before an app takes it.

Week 4: Maintenance rhythms. Weekly reset, monthly reset, fail-soft reset for low-capacity days. A system only counts if it holds when life gets loud.

That foundation is real. You built something that can hold the weight of what comes next.

What comes next is automation.

The Y.O.U. Framework grew out of my own story — understanding my brain (ADD and complex-PTSD discovered in my late 20s), observing where friction shows up in my work, and uncomplicating systems until they actually run.

But last year's arc was mostly about me.

This year we are adding R — and R is about youR clients, the people you build for, and the responsibility that comes with being the one who designs the system.

The Y.O.U.R. Framework:

Every week in May I'll run a consistent example through the framework — "Y.O.U.R. client." A fictional solo creative who registers for our May 31 event. We'll trace one layer each week: from registration confirmation to pre-event reminders to post-event follow-up to ongoing relationship. Because automation, done well, is hospitality.

The full arc kicks off Friday May 8.

You do not need to write code to work like an engineer about your context.

An IDE — that is what Cursor and VSCode are, an Integrated Development Environment — sounds more technical than what it actually does: it puts your folders, your text files, and a terminal window all in one place. Software engineers call a structured folder of files a repository. You may already have one. It probably just does not live in a tool that lets you see and interact with all of it at once.

That is the shift we are building toward this month.

When your notes, templates, naming conventions, and workflow documentation all live in one folder and you open that folder in an IDE, three things become available to you:

This is the foundation. Before AI tools, before automation scripts, before any subscriptions. A folder of Markdown files in an IDE window, with a terminal you can reach when you are ready.

One thing before you open a file for the first time: make the window feel like yours. Change the color theme. Update the font to something your brain actually likes. If you are neurodivergent or have any visual processing fatigue, your default monospace font is probably not helping — I wrote about exactly this at pythonessprogrammer.com/blog/accommodating-yourself-is-cute. A workbench you want to return to is worth five minutes of setup.

Each issue in May includes one concrete IDE move — something you can try in five minutes, no coding required. On May 8 I am also publishing a full beginner's guide — every panel labeled, every shortcut named, the theme and font setup with exact copy-paste instructions — plus a video walkthrough so you can follow along on screen. We start there.

Your tech struggles, reflected back. Got one? Send it in.

This week's prompt:

What is one thing you have tried to automate that kept breaking or falling apart — and what do you think actually caused it?

I am building a Y.O.U.R. client scenario through May and I want it to reflect real failure patterns, not idealized ones. Reply and tell me what broke. Bonus points if it was a tiny thing that somehow derailed the whole system.

You wrote something down in the TLDR. That task — the one that costs you more energy than it deserves each week — that is your starting point for May.

The Fire Horse does not research the perfect automation before beginning. It builds the smallest version that runs and charges forward from there. You already have the candidate. That is further along than most people get.

🔥 Charge forward with: Start with the automation that reduces one decision. That is enough to begin.

The arc opens Friday, May 8 — the full Y.O.U.R. Framework, your brain first. We'll also meet Maya for the first time: a solo creative who just registered for the May 31 event and is about to discover exactly how many assumptions a "simple" confirmation email can make.

If anything in today's issue landed for you, hit reply. I read every one.

See you Friday.

Amanda

The Pythoness Perspective is free, always. If it's useful to you, here are ways to support the work: