Using Claude Code as the orchestrator and Codex as the engine gives you the best of both tools: Claude's UI, Codex's depth, and minimal Claude token spend. The economics only work when the task is big enough to justify two layers.
The bottleneck in software engineering has shifted from typing to understanding. As AI handles implementation, engineers who thrive will be those who recognise patterns, curate guardrails, and connect technical decisions to business outcomes.
Hermes is an open-source AI agent that runs on a server, remembers across sessions, and builds reusable skills over time. The shift it represents: AI moving from something you summon to something that runs.
A customer support AI agent built in stages: shadow mode first, internal notes second, auto-send only after the data earns it. A walkthrough of the architecture, the knowledge base design, and the lessons that held up.
LLMs are no longer a tab you open. They're the interface layer between intent and every system underneath. This post maps what ambient AI, edge inference, and agent-as-infrastructure mean for how you design modern software.
Voice is where AI product differentiation is heading. This post walks through ElevenLabs voice cloning and conversational agents in enough detail to evaluate whether the technology is ready for your use case.
Most AI-powered customer support is optimised for deflection, not resolution. The problem isn’t bad agents, it’s architecture: no shared context, no real permissions, no escalation path that works.
AI removes bottlenecks until it reaches the one that doesn’t move: human cognition. The faster AI makes your system, the more your team’s mental capacity becomes the constraint. You can’t add more of it.
In 2010, every business convinced itself it needed a mobile app. Fast forward to 2025, and the script is identical, just with AI replacing mobile as the technology everyone insists they can't afford to be without.
The standard AI-assisted dev loop has created a new bottleneck: us. Peter Eysermans describes how deterministic orchestration via n8n, with GitHub as shared memory, gets the human off the loop without sacrificing quality.
When an AI agent gets a requirement wrong, the mistake lives in the test assertions, not the implementation. Domain knowledge catches it, not coding skill.
"Vibe coding" has become shorthand for bad engineering to some people, but does the label hold up? This post unpacks how a playful term coined by Andrej Karpathy became a verdict, and why that's costing teams more than they realise.
LLMs generate code fast, but knowledge debt accumulates quickly. The fix is living documentation, and this post shows how to turn your LLM into the partner that maintains it automatically.
In part three, we look at both sides of the AI contribution debate. A working patch, real demand, never submitted, rejected because AI was involved. But maintainers are unpaid volunteers, and AI halved the cost of contributing without touching the cost of review. Both sides have a point.
We smile at the 18th-century crowd for being swept up by a box with a man inside, yet today it's easy to hand ChatGPT a vague idea and treat the PRD it returns as gospel. Generative AI is genuinely powerful. We get the best from it when we bring both enthusiasm and a critical eye.
