The development environment is undergoing a radical shift at the intersection of software engineering and AI. No longer just about writing clean code, developer experience today is about crafting systems that collaborate with humans and increasingly with AI agents.

This was the central theme of a panel conversation titled “Investing in Dev Tools in the Age of AI” that featured Jesse Robbins (Heavybit), Peter Zakin (Codeium), Kenneth Auchenberg (AlleyCorp), and Ivan Burazin (Daytona) at the Infobip Shift Miami conference.

Speakers first reflected on how developer experience has evolved—from desktop to mobile, from static tools to dynamic, collaborative environments. But as Jesse put it, we’re now entering a new phase where delegation is the new automation.

Traditionally, improving developer experience meant offering excellent documentation, strong community support, clear APIs, and plenty of example code. But today, that’s not enough, Jesse points out:

If you’re building software now, you’re not just designing for humans. You’re designing for agents, too. And they need the same things—documentation, context, and clarity of intent.

Jesse compared the rise of autonomous agents in dev workflows to a new kind of SEO, where developers optimize their tools for discoverability and cooperation with AI agents. Whether it’s delegating tasks, workflows, or entire design processes, success now depends on how well tools can communicate their purpose to humans and machines alike.

Engineers as Fleet Generals

This shift is redefining what it means to be a developer. Kenneth described it in striking terms:

We’re all going from being software engineers writing code to model operators—code composers. It’s like being an art director, hovering over the shoulder of your agents.

He likened the future of development to managing a “fleet” of AI workers, where engineers must learn to orchestrate, debug, and direct multiple agents:

Every engineer is becoming a fleet general. You’re not just an IC anymore—managing autonomous contributors.

That may sound intimidating, but Peter argued that humans will continue to play a central, even irreplaceable role:

What remains when AI removes all the toil—the boring work? Humans are still responsible for the labor. We’re the backstop. We’re the audit log. And that’s not going away.

As the panelists agreed, there’s an emerging class of problems—ethics, oversight, accountability—that only humans can solve. Responsibility remains a human job even in a world run by autonomous agents.

Cursor, Windsurf, and the Agent Race

The latter part of the discussion focused on recent AI-native tools that are transforming the developer landscape—Cursor and Windsurf. Cursor, an enhanced version of VS Code utilizing AI agents, is now valued at $9 billion.

Windsurf, a similar tool, was just acquired by OpenAI for $3 billion. These figures raised a provocative question often heard in investor conversations: “What if AWS or Microsoft builds this?”

Kenneth, who was part of the original 12-person VS Code team, had a candid response:

Cursor and Windsurf aren’t really in the business of building a code editor. They’re using the VS Code base as a shipping vehicle. The real innovation is the agent.

Building an editor like VS Code from scratch is a massive endeavor, one only a few tech giants could undertake. But the opportunity now lies in building the best agent experience on top of that infrastructure, Kenneth points out:

We’re moving toward an agentic future where everyone will have agents on their engineering team. That’s the business. That’s the value.

This paradigm shift means the next battle in dev tools isn’t about IDEs—it’s about who builds the most effective co-pilot.

Open Source as the Foundation

Jesse pointed to the importance of the open-source ecosystem in enabling this transition. He’s an investor in Continue, an open-source plugin integrating VS Code and JetBrains tools to bring AI into developers’ everyday workflows:

Because of this open-source ecosystem, I started writing code again. It felt joyful. This moment in time makes that possible. You get prompted, and you learn.

It’s what I remember loving about development. Experiencing joy in collaborating with tools instead of fighting them may be the most important change of all.

The developer landscape is undergoing a seismic shift, driven not only by breakthroughs in AI but also by developers’ changing roles. Whether through tools like Cursor and Windsurf or evolving team dynamics that blend engineering with product thinking, the panelists painted a future where developers are not just builders but strategic decision-makers.

In an era where AI is both collaborator and competitor, the key challenge remains: staying adaptable, curious, and aligned with long-term value, regardless of whether you’re coding the next billion-dollar product or redefining what it means to build software.

The post The Future of Dev Tools is Autonomous, Engineers Will Become Fleet Generals appeared first on ShiftMag.

CSS Wizardry’s Consultant Performance Engineer, Harry Roberts, has been a professional developer for 14 years and says he finds it funny how old trends in technology have become new again. He comments on developers’ tendency to get distracted by new frameworks again and again, and tend to fetishize frameworks. Oh, and he does not love the fact that everything is going JavaScript and into the browser.

As a Consultant Performance Engineer at CSS Wizardry, Harry also helps companies improve website speed and optimize front-end development.

Roberts has worked with some of the most prominent and respected global companies and organizations, including Google, the BBC, the Financial Times, and the United Nations. His meticulous and analytical approach has made him a go-to expert in the field, and he regularly speaks at conferences worldwide to share his knowledge with the technical community.

We’ll also share Harry’s insights, including his perspective on choosing the right tools for you and your team and whether the market needs so many tools. So if you’ve ever wondered whether you need all those developer tools, keep reading – we’ve got you covered.

On working at big companies and impact

Harry: Honestly? Some of the most meaningful work I’ve done has been with much smaller companies where you can affect way more significant change. It’s probably not a very “rock and roll” and exciting answer, but some of the most impactful work happens on smaller teams. Because it’s a small environment, your impact is way more significant.

But working for BBC before the Olympics, was inspiring. It was stressful but exciting, and working with the UN – you know you’re doing something good.

On website speed issues impacting business in the millions of dollars

Harry: It varies dramatically for some companies.

Companies leave hundreds of thousands of dollars on the table yearly because they’re getting site speed wrong.

Harry Roberts, CSS Wizardry

Most companies aren’t aware of how serious it is. The way I try to describe it is – if the roof blows off the top of your house, you notice it immediately, and you fix it immediately.

However, if the insulation in your roof isn’t perfect, someone might tell you you can save 500 euros per year on your heating bill if you put in insulation, but for you, it kinda works well enough for now. So for companies, it’s that kind of thing. Their roof blows off, and they fix it immediately, but it’s harder to notice slowdowns that might happen for 12 months.

So I’ve worked this before, where a simple 300 ms speed up would have made them an extra 8 million pounds a year, and I’ve worked with a client this year where a 500 ms speed up would make them an extra 11,5 million euros a year. These numbers are enormous, but it’s all because of lost sales. It’s not like someone took 11,5 million euros out of a bank.

It’s a simple case of them earning that much extra. It’s not as urgent if you’re missing out. It’s critical if you’re losing money. So many clients don’t panic until they hear those numbers and see how big they can be.

On developer tools making life easier or more complicated

Harry: I don’t think it makes it more complicated, no. Most developers can pick the subset of tools that suits them and their day-to-day work, safely ignoring anything superfluous. The more significant fear is the obsession with frameworks rather than developer tools.

On favorite developer dools

Harry: 100% DevTools, in whatever browsers you’re working and testing in. Beyond that, a good command of whatever text editor you use and any useful plugins. For more peripheral development work (i.e., not actively writing code), solid foundational command line knowledge is constructive: Git, basic Bash/Zsh, etc. As a Performance Engineer, I also have tools like WebPageTest (a wrapper around DevTools anyway) that I couldn’t live without.

On developers being fascinated by every new framework and tool?

Harry: Firstly, don’t be! We fetishize frameworks, and they often get implemented on projects before they’ve stood the test of time elsewhere.

Everything old is new again, and we’ve already seen some of the largest and most prominent frameworks return to the ideas and solutions of yesteryear.

Some frameworks’ most significant initial selling points are now almost universally regarded as anti-patterns.

Harry Roberts, CSS Wizardry

U-turns at the scale are pretty terrifying. Instead, look at the problems you must solve and choose the most straightforward available tool. Focus on the fundamentals, and the rest will follow.

(Harry is not the only one highlighting the focus on the fundamentals, Kelsey Hightower said exactly the same in his interview for ShiftMag!)

On [disappointement that] everything is going into JavaScript

Harry: It used to be that a user visited a URL, their browser requested a page, and the server built the page and sent it back. It was the norm, and it worked very, very well. Folk decided to improve this for many reasons by shifting the workload to make it more like a user visiting a URL, requesting a near-empty page, receiving it from the server, asking for potential megabytes of JavaScript, running the JavaScript, and then building the page in the browser.

I mean, on what planet is that going to be faster?! (Note: not Earth, as we’ve learned.)

Developers made this a lot worse when they forgot that HTML exists and went to extraordinary lengths to rebuild native, accessible, fast browser features in woefully subpar JavaScript.

Harry Roberts, CSS Wizardry

That’s a lot of work (and code) to do a much worse job than we were five to 10 years ago! Thankfully, people have started to notice that this new way it’s better, and more considered solutions are slowly coming to the fore. That is reassuring!

On predicting tech trends

Harry: I’ve been thinking about this a lot. Trends move fast. And my career has always been based on something other than trends. In a way, I’m dull. Certain things are just fundamental to how the web works. So I’ve always bet on soft.

I’ve always gone with the reliable way things work. And I’ve felt like some miserable old man in the last five years.

Harry Roberts, CSS Wizardry

Everything’s really going JavaScript and into the browser, and I’ve always felt uneasy about that. But it turns out that the new trend is going along with the old ways but in a better way. I find it interesting that everything old is new again. And I’ve been a developer professionally for 14 years. I’ve seen a lot of changes and trends. They progressed fast, but they’re sometimes the right thing to do.

So over the next 12 months, we’ll see a bit of a return to, well, not necessarily basics, but more advanced ways of doing the old things. Developers have gotten more insightful and more mature. What I’m going to be focusing on, I have yet to learn! I need to start thinking about where I want to position myself in the next 12 months. But the industry is beginning to mature, so we won’t need to move as fast. Indeed, from a site speed perspective, the industry is moving as fast as ever, and I can’t comment on anything beyond my field.

On Shift conference

Harry Roberts is a long-time supporter of the Infobip Shift conference. A few years ago, he participated as one of the speakers, and is coming back to Zadar this September.

Shift stands out as a rare gem in a world of cookie-cutter tech conferences.

Listening to insightful talks from the brightest minds of today’s tech scene while surrounded by the enchanting history of a town built nearly two millennia ago, you’d be hard-pressed to find a more inspiring blend of past and future.
Oh, and it’s the most fun you’ll have all year!

Harry Roberts, 2019

The post On fetishizing frameworks and everything old becoming new again with CSS Wizardry’s Harry Roberts appeared first on ShiftMag.