Designing systems & products, PLUS making them look good, was my specialty. Now I can build without having to lean on developers! This is great, I'm so happy! and in case anyone doubts my commitment to my craft, here's how I roll (see below). I can shift between setups in about 5 seconds, the mounts were almost as expensive as the monitors and it's a good thing my desk is made of cold-rolled steel, if anyone else tried this on some particle board nonsense, the whole desk would flip over and end them... that'd be an ironic epitaph written on your tombstone... killed by computer! 🤣🤣🤣

Hi everyone. Is there any rule of thumb on how many words in every layer of an ICM workflow? Im trying to narrow it down in a large repo with many canonical things that apply for every workflow and I have 1263 words in layer 0 and a context routing of 871 words.

Everyone says you can't build and ship a real app live on stream. Too fragile. Too many things break on camera. So that's exactly what I'm doing. For two days. And Fable is the clock on it. Fable, Claude's newest model, goes metered on the 7th. This marathon runs two days straight, right until the moment the meter flips on. It starts with Fable free and ends with the meter starts running. A proper send-off, live, as it happens. Here's the twist that makes it worth watching. The app eats the stream. I'm building Mist, an iOS photo app. Fable is the hands. I direct. And the one signature effect we ship gets tested, live, on a screenshot of the stream you're watching right then. The app develops photos of its own creation. Building and developing, same word. That is the whole show. The finish line is real. A green "Ready to Test" checkmark in TestFlight, landing on air. Not a staged demo. One hero effect, shipped for real. This isn't magic and I won't pretend it is. Live build streams faceplant because they put the fragile stuff on camera. Device gremlins, provisioning, signing. So I flipped it. The rule is simple. Pre-flight the boring, stream the real. Every tedious piece is proven before we go live, so only the creative build, the part worth watching, happens on air. If it still breaks, you watch me fix it live. That's the deal. And you're in it. Drop a photo in the Discord and it becomes test data, live. The community's photos are what teach the effect to see. Bring the ugliest, weirdest photo you own. The thing I actually believe, and the reason I'm doing this in public. Shipping live isn't a coding problem, it's a staging problem. The model can do the work. The craft is designing the run so only the survivable parts face the camera. Constraint is the skill. Two days. One effect. One real ship. A send-off marathon that runs right through Fable going metered, building something that photographs its own birth. Twitch: twitch.tv/ari_evergreen