Retro pixel art illustration of a speaker named Jason presenting at the Data Science Festival, standing behind a podium labeled “DSF Data. Idols.” with a Zerve laptop, surrounded by pixelated space invaders on a starry grid background.

Why Data Work Needs a Different Kind of Agent

Zerve’s context aware agents help data teams plan, execute, and iterate faster while keeping humans in control.

Agent based tools like Cursor and Lovable are reshaping how developers approach software. But for 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 does not follow that structure. It is exploratory. You shape questions, work with shifting schemas, and adapt to evolving goals. That complexity requires something different.

At Zerve, we have 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 is 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. They need human input to stay on track.

I also 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.

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 a few conversations about creative tooling. Several folks mentioned using CRIU for Docker, which I found interesting.

I do not 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 our Community tier.

FAQs (Frequently Asked Questions)

Why do vibe coding tools struggle with data work?

Data work is exploratory and context heavy. Schemas change, goals evolve, and outputs are iterative. Tools that assume fixed inputs and outputs miss the reality of data workflows.

What makes Zerve agents different?

They run with context. Agents can read files, access data sources, see code blocks, and use results to plan the next step. This improves planning, execution, and iteration.

Do agents replace data scientists?

No. Agents accelerate work by writing code, evaluating patterns, and handling repetition. Humans provide direction, domain knowledge, and quality control.

How does Zerve support parallel workflows?

Planning agents split milestones into tickets that run independently. Compute is allocated automatically in the cloud, enabling safe parallel execution.

What context do agents need to be effective?

Agents need access to code, data sources, environment settings, and prior results. Zerve exposes these safely so agents can operate with intent.

How can a non coder benefit from Zerve?

Agents can translate goals into stepwise plans. Even without coding, users can prompt, review outputs, and guide the next step.

J
Jason Hillary
Jason is the CTO and co-founder of Zerve.
Don't miss out

Related Articles

Build something you can ship

Explore, analyze and deploy your first project in minutes