top of page


What I Actually Built to Get Running by Day One
Last week's post was about how it felt. This one is about what's actually running underneath it: two scheduled tasks, no code, and the specific guardrails that kept it from falling apart the first two weeks. If you want to build something like this yourself, this is the version with the actual mechanics.

Amy Westlake
Aug 184 min read


I Was Running by Day One. Usually That Takes Weeks.
I started a new job about a month ago and braced for the usual rebuild, recreating every script and process I'd relied on before. Instead, I connected a few tools on day one. By week two, someone said a name I didn't recognize, and I already had a profile on them. This is what changed when the context showed up before I did.

Amy Westlake
Aug 113 min read


The Council in My Head
I used to send my status report after one AI pass and my own read-through. Now five personas argue about it first, the business partner, the executive, the chief of staff, and two more, each built around someone who actually reads the thing. This isn't really about status reports. It's a structure you can point at any output you produce.

Amy Westlake
Jul 115 min read


How I Used AI to Reorganize 100,000 Files (And Why I Let It Make Decisions)
My phone was 96% full and I was leaving for vacation in a few days. The reason I couldn't clear it was an external hard drive I'd been avoiding for years — 25 years of photos, buried in backups of backups, scattered across 30-plus folders. I gave myself the weekend and let AI do the heavy lifting. It recovered 2,101 photos I didn't know I had — including the full Morocco trip I thought was only 304 photos. The number that mattered most: zero deletions.

Amy Westlake
May 314 min read
bottom of page
