Writing
-
A head-to-head of pencil.dev vs Claude Design on the same markdown input. Claude Design produced the more polished deck and handled speaker notes; pencil.dev still wins for iterative UI work where direct manipulation matters.
-
A risky pattern is emerging: teams build products with AI agents, then forget to build the boring screens, logs, and manual controls around them.
-
Five types of documentation, five different AI leverage stories. The question isn’t whether to involve AI in your docs; it’s where each type belongs and how much maintenance you can hand off.
-
Since I started using Claude Code, I've wanted to build a truly autonomous agent: one that keeps working when I walk away from my desk.
-
Last week we had a message from a user asking about a Safari bug. The bug has been lingering for a while. I'
-
I learned this building an agent pipeline. An engineer agent would implement a feature, then a reviewer agent was supposed to check the work.
-
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.
-
Claude Code shipped a Teams feature. Give a group of specialised agents a task and let them tackle it together. An orchestrator coordinates, and
-
We used to put a lot of effort into even the smallest code change. Coming back to it afterwards was expensive. Coding is no
-
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.