Anthropic posted a reel today of one of their designers showing off their workflow for working with Claude Slides. But I fell in love with the little room graphic, and had to make it my own! More to come on this for sure! 🫡

I took a hand-drawn dragon reel I loved (animation by Karlotta Freier, on IG) and tried to rebuild the *style* using only code: no AI image or video generation, no hand animation. The dragon, the story and the music are our own; her reel was the bar to measure against. Here's how it came out: https://youtu.be/hPW_uHlBakI What I learned: 1. Threejs can be use for animation 2. Side-by-side with the reference helps with consistency 3. Credit the creator, make the thing yours. It took 8 versions to get here, and it's still not her level. That gap is the lesson. 📅 I'm back this Saturday for Vibe Film Session 4, 2:30–4:30 PM MT, same Zoom link as always. We'll get into memory: how to keep your character, props and world consistent across every shot. https://www.skool.com/cliefnotes/vibe-film-saturday-sept-5-430-pm-et?p=dd094a57 What's one thing you've tried to copy recently that turned out harder than it looked? Throw it in here and I might use it in the session!

We just crossed 50,000 members 🎉. Today. Not a projection. Not a “coming soon” slide. That number broke because Jake showed up with ICM and actually shipped it into a room that doesn’t treat people like leads. The welcome here isn’t a drip sequence. It’s people answering questions, sharing the folder, and sticking around after the first win. Most communities rent attention. This one compounds it. Jake’s ICM didn’t land in a vacuum - it landed in a stack that already preferred transparent workflows over vendor theater. Members didn’t just buy. They stayed, tested, and pulled the next person in. From empty chairs to a milestone that pays people back. Stop chasing the next shiny cohort. Start owning the room that keeps grinding after the launch email dies. If you’re in, say what you got out of it. If you’re watching, the door’s still open.

Hopefully all of us here are past this, but I still feel obligated to make a reminder when I start to see things like what I reacted to in this video. So many people are still on the vicious cycle of drifting to every new release out there and spending more time on the news cycle than curating their own context layers. Focus on yours and your own expertise. Not what specific tool you are using. Your journey will lead you to what you actually need along the way.

Sandboxing means you run the code in a locked room that can't touch the rest of the house. Most of the time you download a script, an agent, or some half-baked tool and just hit run. If that thing is sloppy, malicious, or just broken, it can read your files, phone home, burn CPU, or rewrite your stack. Sandboxing is the fence you put around it first. The process gets its own little world: limited files, limited network, limited memory, limited permissions. If it goes feral, the damage stays inside the fence. Think of a new rescue dog. You don't hand it the run of the house on day one. You put it in a crate or a fenced yard. It can bark, dig, and chew the toys you gave it. It cannot open the fridge, shred the couch, or bolt into traffic. Same idea. The app gets a crate. Your real filesystem, credentials, and network stay on the other side of the fence. That's why containers, VMs, and browser sandboxes exist. Not magic. Just isolation you can inspect. You decide what goes in, what comes out, and what dies when the session ends. No shared memory with the host unless you explicitly open a door. Practical version for the grind: - Untrusted script or agent? Run it in a container or a throwaway VM, not on the bare machine. - Give it only the folder it needs. Mount nothing else. - Kill the network unless the job actually requires it. - Tear the whole thing down when you're done. No leftover processes, no leftover state. Stop letting random code roam your machine. Start giving it a crate. #sandboxing #ownyourstack #deterministic #stoptherunawaycode