This is a new style as well that I'm testing and I'm talking about systems thinking a little bit more in it and how I think that you can do more as a company now, especially if you're a consultancy. If you're thinking of starting your own or already have one, this video might be huge value for you! It's on my YouTube so if you can go like it there and leave a comment that would be amazing I'll probably create a text companion and make a few more videos and add this to a new series called systems thinking In the classroom! We shall see.

Okay don't judge me on the title. It's actually what'll help you save up to 75% tokens while your using any Cloud LLM model. So as you can see in the screenshot below, there's this dev that made claude speak in "caveman" terms. Turns out that saves tons of credits for you. Tbh the more AI evolves, the more dumb and easier ways to save tokens arise, maybe soon enough the em dashes and 50 line answers would be eradicated by default? Anyways, here's the link to the post if you'd like to snoop around there: https://www.reddit.com/r/ClaudeAI/comments/1sble09/taught_claude_to_talk_like_a_caveman_to_use_75/

Fake Account pretending to be me, report and deal with it how you can. https://www.instagram.com/the_real_venceslau?igsh=cG9rbTN2M3Iyd3Rx

Hey All wanted to share something I was able to use today that helped me get something done in 20min rather than the usually 2-3 hours. I like to use Youtube a lot to learn new techniques and ideas to use in my work, but that takes a lot of time. I wanted to learn a specific granular synthesis patch to recreate a sound. Under normal conditions: watch the video, rewatch the confusing parts, look up GRM's modulation system separately, rebuild the patch by trial and error. Realistically 2–3 hours before I'm actually working. With this workflow: clipped the video, had Claude reconstruct the signal flow and give me step-by-step instructions, followed them, asked for timestamps twice when I needed to see something visual. I was building the patch within seconds. Here's the breakdown of the workflow pasted from my session summary from claude: --- ## The Problem YouTube tutorials are great but they also take a lot of time to watch and digest. A 45-minute walkthrough covers maybe 20 minutes of usable information, buried in real-time narration, visual demos, and the host's live troubleshooting. To actually *do* what you watched, you still have to reverse-engineer the steps or follow along. But if I'm hunting YouTube for a tutorial for something I need to do right now that's a time sink. --- ## The Workflow Works for any tutorial, any domain. **Step 1: Clip it.** - Use Obsidian Web Clipper to save the YouTube video as a markdown file. The clipper pulls the transcript and metadata into a structured note directly to an Obsidian vault you can work with directly in a chat. - If you store the Obsidian Vault inside your Claude workspace in a directory you can access it with Claude. **Step 2: Have Claude teach it to you.** - Ask Claude to read the transcript, summarize the technique and walk you through it step by step. - you can immediately start working or learning. **Step 3: Execute with Claude on standby.** - If you need calrifcation ask Claude for the timestamp to a specific step. It can point you back to the exact moment in the source video without you having to scrub through the whole thing. It will even give you a direct link to that point in the video.

1. Watch the intro video and introduce yourself in the intro post here 2. Start with The Foundation (free course). Concepts, folder architecture, prompting framework. Everything else builds on this. 3. Check in at the bottom of each lesson. Polls, discussion posts, other members working through the same stuff. Use them. 4. When you're ready to build real things, move to Implementation Playbooks (Level 2). When you're ready to build your own tools, Building Your Stack (Level 3). 5. Post your work. Ask questions. Help others when you can. What are you here to build?