I spent a little time testing the new ChatGPT Images 2.0 for a branding use case. I wanted a new visual for my LinkedIn “The Daily Dose” series that felt clean, modern, professional, and aligned with my AI Bits & Pieces branding. My prompt was simple and straight forward: "I need to create a LinkedIn thumbnail for a post I'm doing called "The Daily Dose". I'm doing the Claude Code edition, and I need my logo in there for AI Bits and Pieces." In one shot, I had the base image: I uploaded my logo, it came back with a great design, it matched my colors, and was not overly produced. From there, I took the image into Canva to add my headshot, and I was done. It saved me hours today. ChatGPT gave me the creative acceleration. Canva gave me the final polish. That is becoming a very practical workflow for content creation: generate fast with ChatGPT → refine visually with Canva → publish confidently ChatGPT Images 2.0 helped me create the foundation. Canva helped me finish the job. Results below: 1) Tile shot 2) Original image from ChatGPT Image 2.0 3) Final image - After applying Magic Layers, offsetting the word "Daily" and adding my headshot in a frame it was done

I was commenting on a great question posed by @Girish Mohan, and I found myself thinking about it long after I responded.🤔 That reflection led to this post about the future of AI in a practical, real-world sense. The essence of the question: Is there a risk in becoming too dependent on one AI company, product, or tool set? I thought that was a smart question, because there is some real tension there. At this early stage of AI adoption, there is always a risk in overcommitting too soon. We have seen this before. During the eCommerce boom, a lot of companies looked like they were going to dominate, and many of them did not last. Early markets move fast. Leaders change. Sometimes you pick the wrong horse. 🐎 At the same time, over-diversifying creates its own problem. If you keep jumping from one tool to the next, you can lose the benefit of synergy. Some tools work better together. 🔗 Gemini and NotebookLM are a good example. When tools are designed to complement each other, the combined value can be better than chasing ten separate platforms that do similar things. There is also a practical reality that matters. One person cannot learn every AI tool coming to market. There are too many. At some point, each of us has to decide where we want depth, where we want breadth, and what kind of workflows actually fit the way we work. 🎯 That means some specialization is going to matter. People will need to find their niche instead of trying to master everything. But for me, the bigger point sits above all of that. We are moving into a very different communication model. 1) AI is shifting toward natural language. 2) More of the work will be handled through machine-to-machine interaction at machine speed, 3) All this be done without the user interface we think of today. 🛍️ My shopping AI may eventually interact with a retailer’s concierge AI. 🤖 Your scheduling assistant may work directly with mine. 🔄 Business systems will increasingly pass tasks, context, and decisions across platforms without the same kind of manual navigation we deal with today.

We’re planning upcoming live sessions and want to make sure it’s focused on what you want most. - What topic would you like us to cover? - Drop real use cases — we may build around them. 👉 We’ll run sessions on the top 2 choices first.

Welcome to the Out of the Box series — where I explore what can be built with no-code and low-code AI tools in 30 minutes or less. No manuals. No tutorials. Just curiosity and creation in motion. This time I revisited Sora 2 a few months later to see how the experience has evolved. App: Sora by OpenAI Time: Under 30 Minutes Category: AI Video Creation / Prompt-Directed Video Video Title: Move Over Rover, The Dog Days of Coding Are Over - Claude Code is The Cats Meow 🎥 What Is Sora? Sora is an AI video generation platform that transforms a simple text prompt into lifelike, cinematic scenes — complete with motion, lighting, and visual storytelling. Think of it as having a director, camera crew, and editor… all powered by a prompt. ⚙️ Experience 1 — The First Test A few months ago, I ran an Out of the Box experiment with Sora using a simple presenter-style scene. The results were impressive for early generative video, but the workflow still felt a bit like experimentation. The outputs were interesting, but not something that added much practical value beyond demonstrating what the technology could do. If you’re curious about that original test, you can see the full post here: 👉 https://www.skool.com/ai-bits-and-pieces/out-of-the-box-in-30-sora-2?p=e63f6633 That first experiment helped show what was possible, but the bigger question was how quickly the experience would evolve. ⚙️ Experience 2 — Revisiting It Today For the second experiment, I tried something completely different — a playful, high-motion scene designed to test character behavior and storytelling. Prompt theme: A cat driving a quad runner at high speed — Fast & Furious style — with a dog riding on the back howling and clearly terrified. The twist: - The cat is labeled “Claude Code.” - The dog is labeled “ChatGPT.” Experiment 2 Video: https://sora.chatgpt.com/p/s_69b4d4703dbc819180c914a61747c81f?psh=HXVzZXItQWI5dFRpa3JRS1RTSmhwbDY3VlFYaWxv.4nGp4ZY9Gsxo

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.