I launched my website https://dejv.pro few days ago. The goal is to consolidate my thoughts into (hopefully) understandable and comprehensive package. As I am locked "inside" i would love some outside perspective and feedback on: - What is overall feeling you get from the site/brand? - What is the message/association you get from a quick skim? - Do you find the content clear or do you feel confusion/ambiguity? - Any other insights! Any feedback is appreciated!

Everyone gets something wrong the first time. Vote below, then drop your mistake in the comments so others can learn from it.

Most people use AI coding agents the same way. Open one chat, type, watch it work, copy the output. The model is doing both the thinking and the typing. That's the bottleneck. The interesting move is splitting those two roles. One model holds the judgment. Other models do the typing. The judgment seat never touches a file. The typing seat never makes a decision. I call this the orchestrator pattern. If you've been here a while You'll have seen me developing a system for dispatching workers from within a single Claude Code session. Briefs going out, workers running in the background, results coming back to one main seat without me ever switching windows. I've been running it for months. I just open-sourced the harness. What it does Pushing Dispatch is a multi-model dispatch framework for AI coding agents. You sit in one Claude Code session as the orchestrator. From there, you write briefs and dispatch workers. Workers run in the background on whichever model fits the task. Opus for hard reasoning. Sonnet for steady execution. Haiku for mechanical sweeps. Kimi for long-context. DeepSeek for cheap parallelism. One harness. Many models. One judgment seat. How I use it Three patterns: Brief and dispatch. I write a brief in the orchestrator session, hand it to a worker, and don't read code while the worker runs. I review the output when it's done. Parallel fan-out. When ten files need the same kind of edit, I dispatch ten workers and review all diffs in one pass. Long-context to Kimi. When something needs the model to hold a hundred-thousand-token codebase in working memory, the brief routes to Kimi automatically. The point is never to type the code myself, and never to do the same kind of thinking twice. Quick start Paste this into a fresh Claude Code session: ———————————————————————————————————— Read SETUP_WITH_CLAUDE.md from https://github.com/PUSHINGSQUARES/Pushing-Dispatch_ and walk me through setup end to end.

🎉 Meet your new admin: @David Vogel Some of you have been watching this happen in real time. David has been quietly turning his "Show Your Work" posts into one of the most useful threads in this community for months. Resource roundups, deep-dives, honest takes on what's actually working in production. No fluff. No hype. 🛠️ So I gave him the keys. 🔑 David is now an admin of Clief Notes, and he has his own classroom: 🏛️ David's Corner. Go check it out. AI Acronym Overload? Here's the Cheat Sheet - Davids Corner 📂 What's in David's Corner He started with the resource post a lot of you bookmarked last week and has been steadily expanding it. As of right now you'll find: 🔥 Must Have Resources - 🎨 Looking for design inspiration? - 🧠 AI Acronym Overload? Here's the Cheat Sheet - ⭐ Some of My Favorite Resources 📚 Learning for Everyone - 🥊 Obsidian is BLOAT! Batter Up - 💰 Flip the Script — It's all about the $$$ - 👻 Do You Have a Soul? - 🔄 My AI Workflow Evolution 👨‍💻 Developer Resources - 🕵️ LEAKED: Ten Prompts from Experts - ⚡ Introducing the Hermes Stack 🎯 David and Jakes Picks (this one's going to grow) Plus he's curating trusted YouTube channels and a running list of favorite community posts on resources inside the corner. So if you wrote something good about a tool, a stack, or a workflow, that's where it might end up. 👀 He's adding more weekly. If something stops delivering, he wants to hear about it. That's how the corner stays sharp. 🔪 💡 Why this matters The Vault and The Drawing Room give you my methodology. David's Corner gives you a second lens. Same standards (battle-tested, no theory, no marketing slides), different angle. He's been in the trenches with tools and stacks, and he writes about them honestly. ✅ What you can do 1. 🔖 Go bookmark David's Corner in the classroom 2. 💬 Drop a comment under his posts when something works (or doesn't) 3. 📨 Got a resource that should be in there? Tag him. He's curating.

I created a scope of work, quotes, and invoicing system that suggests project pricing for me! Pricing things out for quotes used to take me a long time and now I just have to review for accuracy! I work with a lot of nonprofits, so it also calibrates for this if flagged 🌬️🔥