Tooling

ElevenLabs: voice cloning, agents, and what they mean for your product

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.

"Good news, I built it in Lovable.": an engineer's guide to surviving that sentence

Business users love Lovable. Engineers tend to panic. A real-world case study of how to wrap an AI builder in guardrails so non-technical teams can move fast without quietly rewriting the systems that give your product its edge.

Parallelise yourself with Git worktrees

The claude -w flag spins up an isolated git worktree in seconds, so you can keep coding while a long-running task occupies your main session. No conflicts, no context pollution, no waiting.

The SaaS audit bingo card: insights after auditing 190+ SaaS companies

After auditing 190+ 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.

Your Claude Code is burning through tokens: here's how to fix 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.

Nobody learned a city from a map

The fastest way to learn agentic development is to stop studying it: move in, extract repeatable patterns into skills, and reflect to compound.

Hosting shared document services - WOPI

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.

From opt in to default

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.

Three Claudes walk into a codebase

The machines aren't replacing developers, they're promoting them. You're no longer just writing code; you're managing agents, reviewing output, and setting standards. Three Claudes walk into a codebase, and suddenly you're a manager.

Running multiple Claude accounts without logging out

Managing multiple Claude Code accounts across machines gets messy fast. Jean-Claude keeps the useful parts in sync, separates account-specific config, and makes switching between personal, team, and client setups far less painful.

Technical debt lost its excuse

Technical debt used to justify meetings, trade-offs, and dedicated sprints. AI has changed that. Cleanup is now fast, cheap, and continuous. Teams that stop debating and start fixing unlock faster delivery and better outcomes.

Conductor: running multiple AI coding agents in parallel

Conductor by Melty Labs makes parallel agent workflows practical by running multiple agents with separate tasks simultaneously. The trade-offs are real but manageable, and this is where development is heading.

I'm using my engineering colleagues as my personal agents

A couple of months ago, I was copy-pasting prompts into ChatGPT. Now I'm shipping features, running tests, managing branches, and keeping documentation alive, with a team of agents doing the heavy lifting. All by myself.

Stop obsessing over the perfect prompt

LLMs are built for conversation, not incantations. The value isn't in your opening message, it's in the back-and-forth: clarifying, correcting, refining. Iteration is cheap. The conversation is the work.

Out with multitasking, in with orchestrating

The return of multitasking, but not as we knew it. Running multiple Claude Code instances simultaneously isn't the context-switching productivity killer we've been warned about for years; it's orchestration

Subscribe