Half of today's AI best practices are coping mechanisms for temporary scarcity, not timeless engineering insights. Geoffrey Dhuyvetters traces the arc from SMS bundles to token limits, and argues the price curve only goes one direction.
After auditing 180+ SaaS companies, the same patterns keep showing up: a CTO who does everything, documentation nobody updates, a backlog from 2019. Here's what the bingo card looks like, and what AI is changing about it.
Five idle plugins can burn 55,000 tokens before you type a word. Here's how to diagnose token consumption in Claude Code and cut overhead through plugin management, profiles, and context hygiene.
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.
"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.
The fastest way to learn agentic development is to stop studying it: move in, extract repeatable patterns into skills, and reflect to compound.
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.