For the last three months, I have been warning the Claris ecosystem about a hidden mathematical reality in the transition to AI-assisted coding: The Token Tax. Yesterday, a report from Fortune and Yahoo Finance proved exactly why this matters at an enterprise scale. According to the report, Microsoft has begun actively canceling internal Claude Code licenses for its own engineers.
This is a post-mortem of a real-world system crash. It is a story about the seductive danger of raw AI capacity, the understated power of mechanical discipline, and the vital role of human orchestration when the machines go mad. I am an Orchestrator managing a “band” of four distinct AI nodes: Codex, Claude, Minimax, and
Most email standards are invisible. SPF, DKIM, and DMARC operate in the shadows of the header, silently deciding the fate of your message. BIMI (Brand Indicators for Message Identification) is different. It is the only standard designed to be seen. It puts your verified logo right next to your message in the inbox, acting as
A Bridge among two incredible technologies. FileMaker WebDirect is an incredible deployment tool that has revolutionized how we deliver apps. However, one common request we hear from clients is the need for “Rich Text Editing” that also prints perfectly on reports—something that has traditionally been challenging in a web environment. Rather than seeing this as
Gemini Plans, Claude Executes: The “Two-Brain” Workflow If you open X today, you will see hundreds of posts about vibe coding and how everyone is creating crazy tools, dashboards, and even full-production apps making money. All that information can be overwhelming. But don’t sweat. It’s actually quite simple. Here’s what I have personally found to
Introduction This tutorial is your comprehensive, practical guide to OData in FileMaker Server 21.1.x and beyond, designed for engineers who want to understand, implement, and troubleshoot real-world OData integrations with FileMaker. Why OData Matters OData (Open Data Protocol) is now a first-class feature of FileMaker Server, enabling standard, RESTful access to your data for reporting,
If you’ve ever been caught in a whirlwind of frustration while troubleshooting FileMaker Pro connectivity issues, you’re not alone. Recently, I found myself on the verge of madness (let’s call it “CraZZZZZZZZzzzzzzzzzY”) while trying to resolve a mysterious problem where FileMaker Pro 20 and 21 clients could no longer connect to a FileMaker Server on port 5003. Meanwhile, FileMaker Pro 19 connected flawlessly. The culprit? Cached settings. The hero? A single Delete Cached Temp Files button.
Here’s the full story, along with step-by-step instructions to help you avoid the rabbit hole I fell into.
