Using Vibe Coding in Real Data Projects

Overview

In this episode of The Dashboard Effect, hosts Brick Thompson and Landon Oaks pull back the curtain on what it actually looks like to use AI coding assistants like Claude and GPT inside professional data engineering work. The conversation is grounded, candid, and refreshingly practical.

Yes, AI has dramatically accelerated how quickly code gets written. But as Brick and Landon make clear, writing the code was never the whole job. The bulk of this episode explores where AI genuinely helps, where it still falls short, and how the Blue Margin team is building systems, not just prompts, to make AI a durable part of their workflow.

The tools are getting better. The real question is whether your data infrastructure is built to take advantage of them. Learn how Blue Margin’s Managed Data Service gives your team the foundation to move fast without cutting corners.

What This Episode Covers

Vibe Coding in Data Projects (0:15 – 1:27)

The team reflects on the rapid maturation of AI coding assistants. Early experiences felt like “whack-a-mole,” but recent model updates have made them genuinely reliable for tasks like API integration.

Building API Connections (2:15 – 5:00)

AI is being used to build data pipelines and connect novel APIs, even when documentation is poor. The team introduces “skills”: modular AI instructions that encode best practices and target architecture standards, helping maintain consistency across projects.

The Hidden Work (5:00 – 7:00)

The biggest insight of the episode: hands-on-keyboard time is not the bottleneck. Establishing data access, managing permissions, and coordinating with clients still demand significant human effort that AI cannot automate.

Synthetic Data Generation (10:00 – 13:00)

Landon explains how AI generates rich synthetic datasets for client demos, simulating seasonality, customer behavior, and complex business scenarios without exposing sensitive data.

Future Efficiency & Automation (14:30 – 17:00)

A forward-looking discussion on AI-monitored pipeline failures: automated bug detection, AI-suggested pull request fixes, and the team’s evolving vision for self-healing data infrastructure.

Who It’s For

This episode is worth your time if you are a data engineer or analytics professional curious about how AI tools fit into real project workflows, a team lead evaluating where AI can realistically accelerate delivery, a developer new to AI-assisted coding who wants an honest take on what production use actually looks like, or anyone delivering data products for clients who needs to handle sensitive data responsibly while still producing compelling demos.

Why It’s Worth a Listen

Most AI content oscillates between breathless enthusiasm and skepticism. This episode is neither. Brick and Landon speak from direct, ongoing experience, the kind of grounded perspective you only get from practitioners who’ve shipped real work with these tools.

The discussion on “skills” as modular AI instructions is particularly worth attention for any team trying to scale AI-assisted work responsibly. Rather than reinventing the wheel on every project, the Blue Margin team is building reusable, architecture-aware building blocks that keep AI outputs consistent and production-grade.

And the look ahead toward AI that monitors its own pipeline failures and proposes fixes autonomously offers a compelling, near-term vision of what intelligent automation in data engineering could actually look like. Not science fiction. Next quarter.

“`

Get Expert Insights in Your Inbox

To subscribe, submit the short form below.