
Why Data Work Needs a Different Kind of Agent
Agent-based tools like Cursor and Lovable are reshaping how developers approach software. But when it comes to data and AI development, the new “vibe coding” tools fall short. That was the focus of my talk at the Data Science Festival in London earlier this month.
Those tools work well for traditional software problems with clear inputs and clear outputs. Data work doesn’t follow that structure. It’s exploratory. You’re shaping questions, working with shifting schemas, and adapting to constantly evolving goals. That kind of complexity requires something different.
At Zerve, we’ve built for this reality.
Data work is not just code
In most software environments, agents operate within predictable patterns and tightly scoped tasks. With data projects, the path is less predictable. You work with changing schemas, shifting goals, and outputs that evolve over time. That makes standard code agents less helpful for data and AI development.
To work effectively, agents need access to more than the code. They need to understand your data, your environment, and your workflow. That’s where Zerve comes in.
Context-aware agents are essential
Zerve provides a development environment where agents operate with full context. They can see your files, your data sources, and your code blocks. This allows for better planning, execution, and iteration.
I demonstrated how planning agents create milestones and break them into tickets. Each ticket is assigned to a code agent that runs independently. Everything is cloud-based, and compute is allocated automatically. This enables parallel workflows without extra setup.
Agents are not replacing data scientists
This is important. Agents are not here to replace experts. They are here to help them work faster. People still provide direction, domain knowledge, and quality control. Agents write code, evaluate patterns, and handle repetitive tasks. But they need human input to stay on track.
I even shared how my mom, with no coding background, used Zerve to plan a vacation by prompting the agent and generating a travel plan. It worked.
A few reflections from the event
It was great to see how many young people are already working on real problems in data and AI. The energy in the room stood out. I also had some fun conversations about creative tooling. A few folks mentioned using CRIU for Docker, which I found especially interesting.
I don’t love watching myself on video, but in case you missed it, the full talk is linked below.
Let me know what stood out to you. And of course, try out our new Community tier.