N.B. The following post reflects my personal opinion, built on analysis, research, and decades of watching the tech landscape evolve. I’ve been diving into the history of tech branding lately, and I came across the origin story behind who actually coined the term "Cloud Computing". I found out, the visual symbol of a cloud was used by telecom and computer engineers in network diagrams since the 1970s and 1980s to represent the hidden complexity of the internet. However, back in 1996, executives at Compaq drafted a business plan predicting that software would eventually shift to remote servers, and they picked up that word "cloud". It was meant to save space on an engineering schematic—never to pretend the physical hardware didn't exist. Fast forward thirty years, and that little whiteboard shortcut has backfired on public understanding. By turning an engineering symbol into a consumer marketing pitch, the tech industry convinced two generations that digital tools, internet searches, and AI exist in thin air. People genuinely believe data floats weightlessly in cyberspace. Now, look at what happens whenever a new facility is proposed. I was just reading an update on the 540-megawatt AI data centre proposed in my region on a repurposed 21-hectare former heavy industrial site. It's a huge 44,000+ square metre facility that will generate around 500 construction jobs and 250 permanent full-timers once operational, yet, the online pushback and local anger are shockingly frantic and it's all because of deception. When you tell the public for decades that technology is an invisible "cloud", showing up to build a massive, power-hungry concrete complex feels like a bait-and-switch. People panic because no one explained the physical plumbing behind their screens—or the fact that these projects actually bring major employment and repurpose old industrial land. I saw this reality decades ago while employed as a Data Entry Operator with Australia's Department of Finance, when we transitioned from Canon AP360 electronic typewriters to our first desktop towers. Running that network required an entire cold room floor of a government building packed with reel-to-reel data banks. Digital power was never weightless—it was heavy metal, refrigerated air, and high voltage. The scale has simply grown to match AI.

For the next couple of weeks I'll be dedicating my time to getting my Shopify store finished and live, and wrapping up the pilot episode of The FYG Grid. I just wanted to drop a quick note so I didn't come across rude by suddenly going quiet in the threads. (I won't be able to stop myself from having a sticky beak and "liking" everything though) Catch ya's! 🙂. P.S. Hope all your own projects are coming along great! Bye for now. ✌🏼.

Igor Pogany’s recent breakdown on "AI Theatre"—the gap between flashy showpieces and the unglamorous backend systems that actually save time—triggered a core memory for me. Back in 1991, I was working for an industrial pump company. The mechanics out in the workshop needed a way to quickly order parts and track tools without fighting complex, text-heavy computer software. To solve it, I built them a visual database behind the scenes. Instead of typing codes, the mechanics could click an icon of a nut and bolt to bring up the exact parts list for a specific pump. Click an icon of a spanner, and it took them straight to the tool allocations. It was simple, intuitive, and kept the workshop floor moving. I also knew human nature. I added a bright red button on the screen with bold text that read: PLEASE DO NOT TOUCH! Predictably, curiosity won, and people clicked it. When they did, the computer speaker blared a loud warning siren. It scared the living daylights out of them every single time! It gave the workshop a great laugh, but more importantly, the mechanics loved the system because it wasn't built to look clever. It was built to eliminate friction for the people actually doing the work. Reflecting on Igor's post, I realised my approach to technology hasn't changed in over thirty years. Building backend automation with AI today isn't about staging flashy demos or engaging in "AI theatre." It is about doing what I was doing in 1991—building quiet, practical backend systems that handle the heavy lifting behind the scenes. The software has evolved, but the principle remains identical: build systems that remove friction and protect the energy required for actual execution. 🔢👩🏻‍💻🔩🔧🟥

Has anyone been in the situation I'm in right now? I've got everything ready to rock and roll: ✅ The new laptop is set up. ✅ Three years of planning are done. ✅ All the materials needed to make the lightshades are waiting in the workshop. ✅ Target audience databases complete. ⚠️ The next step is to set up the Shopify account and launch. ❓So why aren't I doing it? I can't even explain it properly. That just popped into my head AGAIN and just thought, I'll find an answer in Skool for sure, hence this post and I'm really starting to get annoyed with myself. I could have built my Shopify store dozens of times by now so what the?? I am definitely not overthinking... I am absolutely 💯 procrastinating AND even Gemini came to that conclusion! 🆘🆘🆘

Hello Fellow AI Pioneers! Recently I replied to Igor Pogany’s breakdown on why AI makes a bad second opinion if you just ask it for passive validation. In that thread, I mentioned my strategy of instructing the machine to act as a strict auditor to stress-test my plans. This week, I took that theory out of the comments section and put it into brutal practice. Having finally transitioned from a mobile-only setup to a proper desktop rig, (my new Lovano Yoga AI Powerhouse), the backend automation for my Shopify store is finally under construction, so a critical operational truth had to be firmly established in my workflows... standard commercial metrics like aggressive revenue scaling simply do not apply to this enterprise. The mission here is a profound legacy project, honouring my father, a two-tour RAAF Vietnam Veteran. Building a platform that holds exclusive permission to feature official ADF Tri-Forces insignia demands absolute respect, placing dignity above pure speed. We are tracking toward a late September launch to process custom orders ahead of Remembrance Day 2026. Taking Igor’s specific advice to explicitly ask the AI to argue against a decision, I prompted my co-pilot to play Devil's Advocate and tear apart my current operational strategy and the machine did exactly that!!! It delivered a precise, highly logical critique targeting three specific areas: 🚧 The Meta-Work Trap: Challenging whether building complex systems and digital grid layouts was acting as a shield to avoid physical manufacturing. 🚧 Bandwidth Bleeding: Flagging my habit of drafting dozens of custom responses for another founder's community, noting it drained executive energy and functioned as an unpaid management role. 🚧 Media Distraction: Questioning whether resurrecting a YouTube channel to document the journey was cannibalising the time required to physically build the business. Reading that output, the immediate instinct was defensive. The critique was technically flawless but contextually blind.