We just crossed 600 members in AI Bits & Pieces. Consistent growth from day one, fueled by people trying to understand what AI actually means for their work and day-to-day life—and how it can help them stand out in the workforce, business environment, or executive ranks. That’s been the goal from the start. A place for: 🔵 AI Curious — figuring out what this all is 🟢 AI Enthusiasts — using it regularly 🟠 AI Practitioners — applying it to real work 🟣 Enterprise — thinking about scale across teams What’s been interesting isn’t just the number—it’s the mix of people and the conversations starting to take shape. Members are building small things. Members are asking in-depth questions. And members are starting to connect the dots between tools and outcomes. A special shoutout to each and every member, and the people who have supported me from the beginning: @Michele Wacht @Dena Dion @Debra Schmitt @Patti Hoekstra @Mark Zayec @Matthew Sutherland @Jason Hagen @Usman Mohammed @Nick Mohler @Eduard Friesen We have some exciting updates and new offerings for the community designed to help you win the AI game in life, at work, as a business owner, or as an agency. A heartfelt thank you. Michael

🗓️ 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’ve been cruising along lately, just loving life with Claude Code, but I recently got absolutely humbled by Cowork. I’ve actually made up a new acronym for the event: WTT. The reality is, I’m not quite productive enough on Code yet to justify dropping $100 or $200 a month in tokens. So, I’ve been managing my token "allowance" like a kid who gets $5 a week when candy bars cost $2. Everything was going great until a buddy asked me to show him the ropes on Cowork. Being confident (and perhaps a bit too proud), I said, "Sure!" I didn't mention I’d never actually run this specific workflow before. I figured—how hard can it be? I set up a scheduled task to roll through my Gmail account and give me a daily briefing. Awesome. Easy. Total "Pro" move. So, I’m showing off, doing this very impressive demo for him, and I hit "Run Now." I’m leaning back, like: "Look, you can see it thinking... it’s reading the email, producing the brief, preparing the summary..." DONK. 💥 OUT OF TOKENS! WTT (What the Token?!) And then it hits me: I cannot Code. I cannot Chat. I cannot Cowork. #WTT Thinking on my feet, I started to explain, "You see, managing tokens is just a sophisticated part of the LLM lifestyle," all while seething under the covers. So, that was yesterday. I decided to shrug it off, tough it out, and wait for the rolling reset while I slept. ☀️ The next morning, I was all fired up to get back into Claude Code to build my slick new app. I sat down, opened the terminal, and... DONK. 💥 OUT OF TOKENS! #WTT Then It hit me... 🤖 Claude Cowork had woken up before I did. It chewed through my entire brand-new allowance of tokens just before I was all fired up to "Claude Code.". I cannot Code. I cannot Chat. I cannot Cowork. #WTT The ultimate irony? I couldn’t even grammar-check this post in Claude. I had to go over and do it in Gemini! LOL. #WTT @Matthew Sutherland @Nick Mohler @Usman Mohammed @John Romano

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.

You don’t need to have the company name do all the work. That’s rarely necessary. In many cases, the name carries identity — and the tagline carries clarity. Together, they do far more than either one alone. Think of it this way. The name is the container. The tagline explains what’s inside. A strong tagline answers the question people almost always ask when they hear a company name: “What exactly do you do?” It clarifies your positioning. It reduces confusion. It strengthens your market signal. For example: AI & Data Strategies LLC Adopt AI with confidence. The name signals the lane. The tagline signals the outcome. Or take AI Bits & Pieces. The name carries story and identity. The tagline clarifies the tone and focus. AI Bits & Pieces Quick quips, quirks, and insights on people + AI Used together, they create signal. 🎯 What a Good Tagline Should Do A strong tagline usually clarifies at least one of three things: What you do Who you help What outcome you create For example: AI Education for Operators Agent Systems for Founders Adopt AI with confidence Short. Clear. Memorable. It shouldn’t feel like a paragraph. It should feel like positioning. 🎯 The Simple Test Look at your name and tagline together. If someone reads both and still asks, “So what exactly do you do?” It needs tightening. The goal isn’t cleverness. The goal is signal. 🎯 The Strategic Advantage A well-constructed name and tagline together give you: - Clarity - Story - Positioning - Flexibility - Longevity The name anchors identity. The tagline carries explanation. And explanation is where positioning lives. 🎯 Final Thought for the Series Naming isn’t about sounding innovative. It’s about signaling the kind of company you’re building. Some names carry story. Some names carry clarity. Some names optimize for search. Some names are built for longevity. The key is choosing intentionally. And then supporting that name with positioning that makes the signal clear. For example: