Twenty-four days ago I posted about Jake's folder system video. This is what happened next. Same foundation — markdown files, orchestration prompts, clear roles. I just kept building. Fifteen named specialists. Each one with a soul file, guardrails, and a playbook. Duke orchestrates. Cash writes. Trace pulls the data. Hank runs the financials. Clint handles the MCP integrations. Behind each one is either a human counterpart doing the real work alongside them — or a role I can't afford to hire yet. Katie who's been with me for 18 years, now has her own orchestrator running the same system. Twenty-seven client folders. Twelve live MCP integrations. One shared repo. The folder system isn't replacing my agency. It becoming my agency. Jake gave me the unlock. This is how it's going.

Live calls, Teams meetings, I'm fine. Looking straight down the lens answering a question, no problem. Trying to record something for my landing page (new biz) and I genuinely cannot do it. Six hours in. Nothing is working. I've tried winging it from bullet points. I've tried a full script with a few teleprompter overlays. Both feel stiff and unnatural the second I hit record. Has anyone actually figured this out? Because it's low key denting my confidence and I know it's something I need to crack 🙏1

There's a thing that happens when you've been heads-down on a build for too long. You've been prompting for hours. Folders are set up, context is loaded, the model is doing exactly what you asked. And yet you hit a wall. Not a technical wall. A you-shaped wall. You just can't see it clearly anymore. Then you take a shower, go for a walk, or drive somewhere, and the whole thing restructures in your head. The thing you were trying to force out of 40 prompts appears in about ten seconds without any effort at all. There's actual science behind this. A meta-analysis of incubation research (https://gwern.net/doc/psychology/writing/2009-sio.pdf) confirmed that stepping away from a problem genuinely improves problem-solving. It's called incubation, and it's a recognised stage in the creative process that you can't shortcut. A more recent study in Scientific Reports (https://www.nature.com/articles/s41598-025-09736-y) found that greater mind wandering during those breaks predicted greater creative improvement specifically for the same problem being worked on. Not just rest, actual mind wandering. Neuroscience research more broadly points to the Default Mode Network as the reason: it activates when you stop actively trying, and it's where your brain makes the wider connections that focused, sequential thinking tends to block. And a Stanford study (https://news.stanford.edu/stories/2014/04/walking-vs-sitting-042414) found that 81% of participants improved their divergent thinking scores while walking compared to sitting. 🚶 What I find interesting about building with AI specifically: Claude handles so much of the execution load now. But the strategic insight moment, the "what if we approached this completely differently" thought, that still seems to happen in the same places it always did, and sometimes that's away from the screen.

Hi all, I learned how to create animations using the instructions we have available here. The example video attached is one sample of what I was able to create (it ain't much, but it's honest work, hahah). I see it as a win, but I was wondering how I can use Claude to add my face and voice in there. I'm alright in recording with my phone, but the trick for me is the editing part. Is there a way to edit it as I'm using it now (Claude+VS Code+Folder Structure)? For the animation, I used Remotion as well. I'm not trying to be a lazy bum, but the solutions I find are pointing to video-editing-career solutions and resources, and that drifts from the focus of what I do. Bonus question, like I didn't take much of your time already: How has premium been working for you? I'm tempted to sign up, but the Claude+VS Code+Folder Structure already feels like I got the most magical thing for what I do.

Man, I just started learning markdown! I can't keep up! ICM in HTML? "It started with Thariq Shipar, Engineering Lead on Claude Code at Anthropic. On May 8, he tweeted: “HTML is the new markdown. I’ve stopped writing markdown files for almost everything.” His argument: when AI writes the content, Markdown’s “easy to write” advantage becomes less relevant. HTML gives you richer layouts, interactivity, and visual hierarchy. Why he thinks HTML wins: Shipar backed it up with a companion site showing 9 categories where HTML artifacts beat Markdown: - Interactive dashboards - Styled code reviews - Inline SVG illustrations - Arrow-key presentations - Collapsible explainers Things that are impossible in a flat .md file become trivial when AI generates HTML. But there was pushback. Developer Kutis Redux published a direct rebuttal: “The Unreasonable Ineffectiveness of HTML” His argument: the switch to HTML creates visual gloss at the expense of source readability, security, ecosystem compatibility, and reviewability. His core point: HTML’s raw source is hostile to human eyes. Markdown stays readable whether rendered or not, which matters when you’re reviewing what an AI just wrote. Then Andrej Karpathy weighed in and went bigger. He called it an evolution: raw text → Markdown → HTML → neural interfaces His advice: Add “structure your response as HTML” to your prompts. He confirmed: “It works really well.” The endgame? AI outputs will not be static documents at all. They’ll be interactive simulations." Sources: - Thariq Shipar on X, May 8, 2026 - thariq.github.io/html-effectiveness - Kutis Redux on Medium, May 2026 - Andrej Karpathy on X, May 11, 2026