The AI Engineering Skills Map for Knowledge Workers

**Nathaniel Whittemore** (0:00)
Knowledge work is being totally transformed by agents right now.
After years of promise, agents are actually here, and they are changing the way that knowledge work gets done. Broadly speaking, we are increasingly moving from doing our work to managing agents that do our work. But in that transition, what are the key skills that matter? Five that stand out to me are one, AI capability mapping, two, context and harness management, three, problem and product prototyping, four, new opportunity identification, and five, rapid new skill acquisition. When you combine these with a foundation of domain judgment, you get a type of knowledge worker that is more capable and more powerful than ever before.
The AI Daily Brief is a daily podcast and video about the most important news and discussions in AI.
All right, friends, quick announcements before we dive in.
First of all, thank you to today's sponsors, KPMG, Section, Blitzy and HyperAgent. To get an ad-free version of the show, go to patreon.com/aidailybrief, or you can subscribe on Apple podcasts. And to learn more about sponsoring the show, send us a note at sponsors at aidailybrief.ai.
In the world of AI, nothing is safe as everything gets rebuilt. The latest reminder of this comes from Cursor, who are taking on GitHub with their new repo hosting platform Origin. The pitch is pretty straightforward. Take Git hosting and add better integrations for the coding agents you're already using. Origin allows developers and their agents to access the codebase from the same surface they're already working in. That makes it easier to run natural language queries across the codebase or use agents to handle comments and commits without context switching or using connectors. Still, maybe their biggest pitch is around platform stability. GitHub service has been widely perceived to be degrading over the past year, with frequent outages and issues. As if on queue, right around the time that Origin was announced, GitHub experienced a 6-hour service degradation.
Matt Palmer, a Dev Experience staffer at SpaceX AI, nodded to the issue, commenting, We were going to ship this earlier, but GitHub was down.
Vercell CEO Guillermo Roche piled on, saying, You can now host your repos in Cursor Origin and deploy to Vercell via Cursor Origin, which is itself hosted on Vercell. And unlike GitHub, it's online.
Now at this point, complaining about GitHub is basically just part of the experience of being a developer or increasingly, being a not-developer who works with code thanks to coding agents. Still, as we've seen so many times in the past, major switches like this ask a huge amount of users, and it's not clear whether a promise of better platform stability and AI integration is enough to drive users to switch. GitHub has incredibly strong lock-in, given how painful migrating code-based infrastructure is. And while there were plenty of people ready to immediately crown Origin as a GitHub killer, many questioned the premise.
Scott Dolinsky, a content creator focused on dev tools, wrote, I'm going to be real. GitHub's outages are super annoying. I just don't see myself moving all my stuff to Origin. Maybe some of y'all moving your stuff there will take the pressure off GitHub servers for me, though. Kush, a software developer at Cursor, used the opportunity to highlight one of the key design decisions with Origin, commenting, We get it. Moving your code is extremely hard. That's why Origin supports mirroring. Leave your code where it is and let us sync it so you can always access it performantly through Cursor, agents, pull requests, local, et cetera. And if you end up liking Origin, you can make the decision to detach from GitHub later on. This means, in other words, that GitHub can remain the developer's system of record, theoretically minimizing the risk of breaking production workflows.
Others weren't sure that Cursor was really in a position to actually promise better long-term platform stability. Veteran developer Michael Cove wrote, I don't trust them. Not that Cursor is a bad company. They are not. But that they don't have a proven track record of security and infra-opsec. Because obviously, it's a new offering. I like Cursor as a coding harness. I think they have a truly innovative product, and I do trust that my code is not going to be used in training. But a code repository store, that's a bit of a different concern. Ultimately, where Cove landed was to say that he would be happy trying out origin for personal projects, but that he's going to need to see a longer track record before moving customer projects over. The launch itself is happening as an early preview to existing customers and some were disappointed about that decision. Still, most felt that the inevitable early teething issues made that call completely understandable.