Hey friends, I'm back with another post in what is turning into a bit of a "How I AI" series. I'm also finally making some of the prompts, commands, etc. I use public on Github, so follow along if that's of interest!

Full Posts

Project Brains: Organizing Complex Initiatives for AI-Assisted Work

A practical system for keeping AI conversations grounded in real project context. For any complex, multi-week initiative, create a dedicated folder with a standard structure—CONTEXT.md as the hub, plus subfolders for artifacts, decisions, research, and meeting notes.

The CONTEXT.md file answers the questions you'd otherwise re-explain every time: current status, stakeholders, decisions already made, and what's still open. The broader principle is that structure beats volume—a sparse, well-organized project brain is more useful than a folder full of undifferentiated docs.

Link Posts

• The A.I. Disruption Has Arrived, and It Sure Is Fun — Paul Ford acknowledges every objection to vibe coding—ecological cost, insecure output, cookie-cutter results—and then points to history: the web wasn't "real" software until it was, and that might be a good trade long term.

• The Father-Daughter Divide — Isabel Woodford's research-heavy Atlantic piece on why 28% of American women are estranged from their fathers, and why the rest often have relationships thinner than they'd like: daughters want emotional closeness, and many dads don't know how to offer it.

• The AI baseline has moved — Geoffrey Huntley argues that simply using AI tools is now table stakes for employment; the real differentiator is understanding the systems well enough to automate your own job function.