I Almost Programmed My AI With 15 Years of Bad Habits
I set out to build an AI-powered business. What I found instead was a mirror showing me exactly how I'd been running my company all along.
Intelligence / Category
I set out to build an AI-powered business. What I found instead was a mirror showing me exactly how I'd been running my company all along.
The most telling thing about the Codex plugin for Claude Code isn't the feature — it's what it reveals about where the gravitational center of agentic coding has already landed.
There's a specific psychological phenomenon that happens when you build a workflow that works. Everything outside it starts to feel broken. That's where I am with Claude.
When your entire organization is built from Markdown files and Claude agents, you stop thinking about org charts and start thinking about scope, authority, and information flow.
Getting better at prompting is a real skill with real leverage — until you hit the ceiling. Understanding what comes after prompting is what separates people building compounding systems from people building better one-offs.
The multi-agent vs. monolithic agent decision isn't aesthetic — it's architectural. The right answer depends on context coherence, failure tolerance, and the shape of the work.
APIs let software talk to software. MCP servers let reasoning agents talk to software — and the difference in what becomes possible is not incremental.
The context window isn't just a technical limit — it's a design constraint that should shape how you architect every system Claude is part of. Most people treat it as a ceiling. It's actually a forcing function.
When an AI agent can read, write, and run code in the same environment it's reasoning about, something categorical shifts — this isn't productivity augmentation, it's a new class of system.
When AI runs in the background — not waiting for your prompt, but working on defined tasks while you do something else — the structural implications for how work is organized are profound and underappreciated.
AI-assisted and AI-native sound like a matter of degree. They're not. They're structurally different systems with different ceilings, different failure modes, and different trajectories.
Most AI implementations are synchronous: you ask, it answers, you act. The agentic loop is something different — and it's the architectural primitive that separates AI-assisted from AI-native.
MCP servers aren't plugins — they're the architectural primitive that turns Claude Code from a capable assistant into the connective tissue of an entire operation.
There's a lot of hype around AI-built websites. Here's the unfiltered version — what AI actually does in our process, what the real limitations are, and what you should expect.
Twenty years of agency and consulting life led to a clear conclusion: the model was broken and AI was the fix. Here's the honest story of why I built VibeTokens.
Every major technology shift creates a window. The businesses that move during the window build advantages the late movers never close. The AI window is open right now.
Most service businesses hide their pricing. I'm going the other direction. Here's exactly how VibeTokens thinks about pricing — and why transparency wins.
The AI headlines are breathless. The reality for small businesses is more nuanced. Here's my honest take on what's actually working and what's still vaporware.
Building a payments security company from startup to Visa acquisition taught me things about business that no consultant ever told me. Here's the condensed version.
Traditional agencies charge high retainers, staff up with junior employees, and protect their processes like trade secrets. That model doesn't work anymore.
The AI consulting industry is full of people who've never run a business telling business owners what to do. Here's my contrarian take.