Walt Disney is quoted with saying : It's kind of fun to do the impossible. With multiple folder architecture, this video kind of encapsulates how I went from fixing an IG profile look, to managing 8 workers who research, write, produce, create, and monitor. Along with a fun clip from a music video that the team made :) Thank you @Jake Van Clief! Without your course, this never would have materialized :)

Just build and pushed my first website. Took 2 days, build multiple workflows first 2 didn't get me the results I wanted. But the third build nailed it. Three tips I got. Use Tailwind css, for consistent design Train it on sections layouts give it guardrails without hardcoding Use opus for building the actual folder structure and workflow. Somehow made big difference vs sonnet. I felt like the first 2 builds where to detailed, kept it more simple the third time. Any feedback is welcome Here is the first build for a friend/client of mine https://innerbloomlodge.com/

Every cloud dictation tool sends your voice to a server you do not own. I dictate client names, half-formed ideas, things I would never want sitting in a log I cannot see. So I built my own. It is called Pushing Talk_. Hold a key, speak, release, and your words land as text wherever you are typing. The speech-to-text runs on-device with a local Whisper model. No cloud, no account, nothing leaves the Mac. It is free. Privacy is not a feature I bolted on at the end. It is the whole reason it exists. Your voice is data, and I wanted mine to stay on the box I own. This is the part worth stealing. I did not type it out by hand. 1. I brainstormed the outcome, then turned it into a plan. 2. Codex sessions ran in parallel, each building a tight slice. 3. Claude held the spec, handed out the slices, and reviewed what came back. 4. I made the calls. BUILD WITH CODEX, SHIP WITH CLAUDE. The models are the hands. I keep the judgment. This is not "AI built my app." I decided what "done" meant, I reviewed every slice, and I am the one who shipped it. The models accelerate the middle. They do not get to define the outcome. The system around the AI is the intelligence, not the model. Define the outcome, let the build run in parallel, and keep the taste human. It was not smooth. I declared it finished three times before it actually worked, and the worst bug was one I caused myself. That story is the deep-dive. Read the deep-dive: https://aris-space.com/documents/debugging/pushing-talk-finished-three-times What would you build if the models did the hands and you kept the judgment? Stop prompting, start defining outcomes. // A<3

A CEO of an MSP that I've been one on one consulting on ICM sent this article to me this morning. Microsoft's SkillOpt automatically upgrades AI agent skills without touching model weights Repo: https://github.com/microsoft/SkillOpt The short version: instead of fine-tuning model weights, it treats your markdown skill files as the trainable parameter. It runs your agent against benchmark tasks, analyzes what went wrong, proposes bounded edits to the skill doc, and only accepts changes if held-out validation strictly improves. The deployed artifact is a single best_skill.md file — no extra model calls at inference. They're reporting +19.1 points on Claude Code benchmarks. That's output quality — the agent getting the right answer more often — not token savings. When I first started building skills in my ICM, they were bloated. Long, unstructured, burning tokens. If you're letting Claude build your skills for you (which is the natural thing to do), you're not necessarily getting an optimized artifact — you're getting whatever Claude thought was thorough at the time. The question SkillOpt is trying to answer: is the skill actually performing, or is it just big? Where I'm less sure it translates: most of the benchmarks are coding tasks, where "correct" is binary. I have three copywriters — Cash, Clyde, and Wradley. Scoring whether a piece of copy is better is a different problem. Harder to define, harder to gate automatically. Is this a layer worth putting on top of nuanced specialist work? Has anyone here dug into it?

With very little experience a week ago, I created a project outline to brand out the cover images on Instagram profile grid. In less than 30 min, after going through the foundations i had it completed. Claude code executes with just two words and can make as many cover on demand as i wish and output them neatly as PNG files in a folder. Jake - super thanks! I learned so much in less than a week 🙏🙏🙏🙏 See before and after :)