Tooling migrations don't have to take weeks anymore
I used to block out weeks for tooling migrations. Now I let Claude Code run in the background, check in when it's done, and pair with it to understand what changed.
I'm love to help product engineers ship better code, faster. To that end, I work on developer experience. I spend my days improving linting and TypeScript configs, wrangling bundlers, speeding up CI pipelines, trying to improve css architectures, and building out design systems.
I used to block out weeks for tooling migrations. Now I let Claude Code run in the background, check in when it's done, and pair with it to understand what changed.
Frontend technical debt doesn't just slow down developers. It undermines your entire business through user attrition, legal risks, and revenue loss. Here's how to spot and communicate these hidden costs.
How I used Conductor and Claude to streamline my team's Dependabot review workflow — and how a colleague turned it into a GitHub Action
If everyone's shipping faster with AI, nobody has an advantage. The real edge is platform work.
Instead of starting a migration by rewriting code, set up backstops first. A lint rule that prevents new code from using the old pattern stops the problem from growing, even if the migration stalls.
How I'm using Claude Code to build a full-stack app while maintaining architectural understanding