🗓️ Session 2: April 10, 2026 at 5pm EST. (60-90 minutes) Check calendar for Session 2 and 3 dates and times. AI is getting closer to giving non-developers a real path to building full applications with natural language. Because one day, you may not think you’re writing software or workflows… but you will be. Maybe it looks something like: - Setting preferences for a fancy AI vacuum - Creating a daily brief from your favorite news and email accounts - Building a simple tool for your own workflow to improve a business process - And, yes, giving directions to your own personal humanoid robot. In any of these cases, learning how to speak to AI clearly will matter if you want practical and useful outcomes. 🎯 What This Live Series Will Cover: - I’ll be using Claude Code on Windows - We’re going to build the a simple task list app across three sessions, with a few differences - Each one will be built from scratch Session 1 — Vibe Code No planning. Just build. Minimal features. Session 2 — Vibe Code + Planning (April 10, 2026) Some planning. More structure and a few useful features. Session 3 — Skill Coding (Planning assumed) The most upfront planning. The most feature rich app. The most fun. 🏁 The goal is to help everyone, no matter their AI or programming experience (including zero) level, get a glimpse into the power of Claude Code. ❗ Beginners and complete newbies are absolutely welcome. It is to help people see what these tools can do, how planning changes the outcome, and why the shift to using natural language matters. We are getting closer to a world where more people will create software using natural language, where the quality of the idea starts to matter more than whether you have an engineering degree. At the same time, two things can be true at the same time - strong computer science fundamentals and great ideas will continue to compound for those who have both. @Matthew Sutherland @Nick Mohler @Usman Mohammed @Dena Dion @Mike AI Consultant

I built a meeting transcript scrubber using 🛠️ Claude Code for my AI consulting practice AI & Data Strategies. Every client meeting contains sensitive information that should never end up in an AI analysis. Employee names, personnel discussions, legal exposure, HIPAA-adjacent content — it's all in there mixed in with the good stuff. I got tired of manually reviewing transcripts before running them through analysis so I built a meeting transcript scrubber. 🔍 What it Does: The scrubber runs your raw meeting transcript through very specialized review lenses, using Claude Code Skills, before any analysis happens. Each lens looks for something different: - HR Review - Manager Review - Client Review - Sensitivity Review - HIPAA Review - Pseudo-Legal Review - Off-Content Filter - Noise Filter Each flagged line shows you exactly which lens caught it, why, and a severity level — ⚠️ Critical, Warning, or Advisory. One important discovery on the Noise Filter. While exploring and testing I discovered that removing too much from the noise filter actually dulls your sentiment analysis. 🎯 Short affirmations like: "mm-hmm", "right", "absolutely" and "yeah" feel like noise but they're actually sentiment signals. They tell you the listener is engaged, agreeing, or following along. Strip them out and your emotional arc analysis loses texture. 📝 So I narrowed the Noise Filter to only flag truly zero-value content: - Technical meeting artifacts — "you're on mute", "can you see my screen", "let me share my screen" - Failed audio references — "sorry you cut out", "I missed that" - Pure scheduling logistics — "I'll send a calendar invite", "let's find a time" Everything else — even one word responses — stays in the transcript because it carries some signal about engagement, energy, or attitude. 🔄 The workflow What I really like about how this turned out is the iterative scrubbing flow. You don't have to run all nine lenses at once. Run HR first, clean it, then run Client, clean it again, then run Legal. Each pass loads the cleaned version back to the top automatically. You're always working on the cleanest version of the transcript.

Let me paint you a picture. 🎨 First, a little context about me. I am a low code/no code builder through and through. Lovable? That's my comfort zone. Claude Code? Open Claw? No, really — These terminal-based tools are about as far from my natural habitat as you can get. However. I've just finished binge-watching four Claude Code videos from Nate Herk in AIS+ and I am 🔥FIRED UP! These videos a great, and I am excited to get started. My interpretation of Claude Code is it's basically like having a senior developer living inside your terminal, building apps for you while you sip coffee. And the skills, the loops, all the good stuff I picked up from those videos — I am READY to put it all to work. I want that life. I deserve that life. So I go to install it. What I thought would happen: Type one command. Done. Sip coffee. What actually happened: A 2-hour odyssey involving Git Bash, hidden folders, PATH variables, and at least three existential crises. 🤷 😂 🛠️ The Setup: Windows Is Not macOS Here's the thing EVERYBODY tells you upfront — Claude Code loves Mac and Linux. Windows? Windows gets the "bless your heart" treatment. The official docs mention something called Git Bash, which is basically a way to trick Windows into pretending it's Linux. Fine. I install Git for Windows. Straightforward enough. Then I try to paste a command into Git Bash. Ctrl+V doesn't work. Right-click. Paste. Nothing. 🫠 Turns out you have to use Shift+Insert to paste in Git Bash. A fun little secret the universe decided not to tell me. The PATH Problem (A Love Story) After installing Claude Code, I type claude into Git Bash and get: bash: claude: command not found🤦 It installed. I can see the file sitting there on my computer. But my terminal doesn't know it exists. This is the computer equivalent of your friend standing right next to you while you call their name and they don't respond.

Now let’s contrast story with strategy. When I named AI & Data Strategies LLC, I didn’t start with memory. I started with clarity. AI. Data. Strategies. Three words. Zero ambiguity. This wasn’t sentimental. It was intentional. Over the years, I’ve named companies differently depending on the objective. - InfiNet Marketing Group leaned more brand-forward. - Winning With Email was outcome-driven and descriptive. - 724Marketplace signaled availability and scale. - PresentItNow emphasized immediacy. Each one reflected where I was and what I was building at the time. 🎯 But as my work evolved toward enterprise and advisory, I realized something: Clarity reduces friction. When you walk into an enterprise conversation, your name does work before you even speak. A clarity-driven name answers the first question buyers have: “What exactly do you do?” Clarity-driven names optimize for: - Immediate understanding - Professional signal - Enterprise credibility - Faster trust cycles They don’t require decoding. They don’t require backstory. They don’t require interpretation. They position. And in AI — where confusion is already high — reducing friction is a competitive advantage. There’s already noise. There’s already hype. There’s already jargon. Clarity cuts through. 🎯 Now here’s the tradeoff. Clarity-driven names are rarely distinctive. They don’t create emotional pull. They don’t spark curiosity. But that may not be their job. If your audience is: - Operators - Executives - Enterprise buyers - Decision-makers Clarity often wins over cleverness. Clever gets attention. Clear closes deals. Next: 🎯 Part 3 — SEO-Driven Names (Traffic as Strategy)

@Michael Wacht Thanks for letting me share! Hey everyone! I've been getting questions from folks wanting to learn Claude Code but not sure where to start. So I put together a complete beginner's guide - and I mean complete beginner. Zero technical knowledge required. What's Inside: ✅ What Claude Code actually is (in plain English) ✅ Step-by-step setup (takes 15 minutes) ✅ Your first conversation (literally what to type) ✅ 5 simple things to try (copy-paste ready) ✅ What to do when you get stuck ✅ Your first week roadmap This isn't theory - it's a "do this right now" guide. You'll create your first file within minutes of installing. Who This Is For: - You've heard about Claude Code but don't know what it does - You want to learn coding but feel intimidated - You're curious about AI but aren't technical - You just want to see what this thing can do The Approach: No BS. No jargon. No assuming you know anything. Just clear, simple steps that anyone can follow. I walked through this with someone who had never coded before, and they were up and running in 15 minutes. If you can send a text message, you can use Claude Code. Download the Guide: 👉 [Attached: So_You_Wanna_Learn_Claude_Code-formatted.pdf] Read it, follow the steps, and then come back here and share what you created! I want to see your first projects, your questions, your "holy crap this is cool" moments. Questions? Drop them in the comments or the chat. We're all learning together here - that's what this community is for. No question is too basic. Let's do this! 🚀 P.S. - If this helps you, share it with someone else who might benefit. The more people using AI tools effectively, the better we all get.