Background Coding Agents: Supercharging Downstream Consumer Dataset Migrations (Honk, Part 4)

This post details a case study of using the Honk background coding agent, integrated with Backstage and Fleet Management, to automate the migration of ~1,800 downstream data pipelines to new dataset versions. It highlights challenges with non-standardized data frameworks (Scio vs. BigQuery Runner/dbt), the necessity of comprehensive context files for agents without external skills, and the impact of missing build-time unit testing on automated verification. The successful migration of 240 PRs for BigQuery Runner and dbt pipelines is reported, with learnings emphasizing data landscape standardization and enforced testing requirements for future agent adoption. Future Honk roadmap items like context gathering and improved Claude Code capabilities are also mentioned.
More from the AI-Assisted Developer Productivity Platform trail
- Why Spotify Is Not Using Bayesian A/B Testing | Spotify Engineering
- Portal by Spotify cut my Claude Code token usage by 90% | Spotify Engineering
- AI Changed How Spotify Builds. What We Learned (and Fixed) About Quality at Higher Velocity
- When Can LLMs Replace Humans in A/B Tests? | Spotify Engineering
- Coding Is No Longer the Constraint: Scaling Developer Experience to Teams and Agents at Spotify | Spotify Engineering