CtrlK
BlogDocsLog inGet started
Tessl Logo

ainativedev/aidevcon-2026-ldn

AI Native DevCon 2026 London — all conference sessions as interactive skills

70

Quality

88%

Does it follow best practices?

Impact

—

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

quote.mdtalk-foxwell-reinvention-dev-team/

Notable Quotes — The Reinvention of the Dev Team

All quotes verbatim from transcript.md. Speech-to-text artifacts preserved.

#TopicQuoteSection
1Talk framing"I'm going to be talking about agentic software development, but I'm not going to be talking about the tools or technology. We'll be talking about what it means for our teams and how we organize ourselves with these new capabilities."§1
2Velocity unlocked"The velocity that we've been yearning for is here. It changes everything. And for a lot of teams, we don't quite know what to do with it yet."§1
3Agentic maturity"I don't know many people who are operating at level eight and I certainly don't know anybody who can say creditably that they're doing this safely."§2
4The three anchors"we need to build something worth building. The second, I believe speed requires safety. And the third one… People matter."§3
5Outcome > task"we always, always must pursue the outcome and not the task… The code is how we solve. Our problem. It's not the what."§4
6Back pressure"the pace that we can address these problems in the development team creating what I call back pressure in product. The speed of decision making, the speed of analysis is actually not able to keep up with the pace of software development in a typical team."§4
7Forward-deployed engineer"a forward deployment isn't a sales engineer, they're not a speech architect. They're an empowered engineer that sits side by side with the users. And if they see a gap in the product, they are empowered to fix the product and deliver that value to that user."§4
8Product engineer"engineers that don't need to ask permission of a product manager go and improve the product. And this pattern works incredibly well if you're building products for software developers."§4
9Not advocating"I'm not up here advocating for any of these. I'm talking to you about what I'm seeing, people experiment with to unlock the velocity that agentic development gives them."§4
10Headcount"I don't think it's necessarily about reducing headcount. It's just making sure you have people in the right places doing the right work."§4
11Bib day one"on day one. We decided what we were going to build that week. And on day one, we finished by lunchtime."§4
12Ambition unlock"this unlocking of this velocity… makes us more ambitious and we have to be more ambitious. And so we had to relearn… instead of focusing on one thing, I must think bigger."§4
13Tapas team"I'm absolutely trashing the two pizza team… someone suggested that we start calling it a tapas team, which I really like the teeny tiny tapas tea, the small plates."§4
14Path to production"if there's any manual steps on that path of production for yourself where you're going to end up with a pilot, whether that be code reviews, whether that be your testing suite, you're going to end up with a bottleneck somewhere else."§5
15Day two cost"the cost of day two is always greater than day one to scale and maintain an application that has real users is going to cost you a lot more in the long run than just getting version one of that application into the hands of users."§5
16Invisible security"good security is invisible bad security is an absolute reputation killer."§5
17Bib after MVP"we have the first version of the product ready in two weeks. So what do we do after that? I can honestly tell you it looks hell of a lot like platform engineering, reliability engineering. Like there was not a lot of feature development."§5
18AI-authored code review"asking engineers to review thousands and thousands of lines of AI authored code is going to create a lot of very unhappy engineers."§6
19Ruscio quote"The mistake would be to treat unread code as a failure of discipline rather than a signal that the discipline itself must change." (quoting Joseph Ruscio)§6
20Minimum viable human"what is the most, the smallest team that you can have a sustainable encore road. And I think it's four people… you can't be on call more than 50% of the time… the minimum viable human like is going to be dictated by some of these roles."§6
21User empathy hire bar"If you hire someone like and they can't sit down with a user understand their problem and design a solution that solves that problem, then that person is going to become a bottleneck. They're going to be spoon-fed requirements and that has become normal in our industry. And I think that's a practice that needs to end."§6
22Close"experiment with empathy because it is not an easy thing. To change your discipline so fundamentally and at such speed."§7

talk-foxwell-reinvention-dev-team

outline.md

quote.md

SKILL.md

transcript.md

README.md

tile.json