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.
Ever wanted to build your own Google Docs-style document service? This post introduces WOPI, the open protocol that lets web applications embed Office document editing directly in the browser, while keeping your app in control of storage and permissions.
A mobile app, past its usefulness, was days from being phased out. One email reversed the decision. No discussion. No input from engineering. This is what happens when decision-making drifts too far from the work.
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.
Developers don't skip standards because they're careless, they skip them because there are fifteen things to remember and the code was the hard part. The real question isn't which tasks your LLM handles well. It's what's still slipping through ungated.
The AI wave is here, and the industry is already splitting into two: those adapting fast and those falling behind. The gap is widening quickly.