Send us Fan Mail

AI and software development - the Real Problem with AI-Driven Software Engineering.
AI is dramatically accelerating software delivery — but speed alone is not the answer.

In this episode of Serverless CrAIc, we explore how AI is reshaping software engineering, platform engineering, architecture, and organisational design.

As code generation becomes commoditised, the real differentiator is no longer how fast teams can build software — it’s whether they are building the right thing.

We discuss:

why clarity of purpose matters more than ever
how AI amplifies both good and bad engineering practices
the growing importance of socio-technical systems
platform engineering and cognitive load
why North Star metrics still matter
how engineering leaders should think about AI adoption
the risks of accelerating poor organisational decision making

If your organisation is adopting AI into software delivery, this conversation is essential listening.

Chapters

00:00 Introduction
01:42 AI is changing software engineering
05:18 Why building faster is not enough
09:34 The danger of accelerating bad decisions
14:27 Why clarity of purpose matters
18:40 AI as a commodity vs differentiator
24:05 Platform engineering and cognitive load
30:12 Socio-technical systems in the AI era

Resources

🌐 Website: The Serverless Edge https://theserverlessedge.com/
📘 The Value Flywheel Effect: https://itrevolution.com/product/the-value-flywheel-effect/#o5a04b7992465
🎧 Podcast Playlist: Serverless CrAIc Playlist https://open.spotify.com/show/5LvFaitkSkg2q5MWqKLrXu
📰 Newsletter: The Serverless Edge on LinkedIN https://www.linkedin.com/build-relation/newsletter-follow?entityUrn=7066788643985596416

Serverless CrAIc from The Serverless Edge
Check out our book The Value Flywheel Effect
Follow us on X @ServerlessEdge
Follow us on LinkedIn
Subscribe on YouTube

Send us Fan Mail

Why Team Topologies Matters More Than Ever in the AI Era.
Are AI agents changing how software teams should be structured?

In this episode of Serverless CrAIc, David Anderson, Mark McCann, and Michael O’Reilly explore one of the biggest questions emerging in the AI era:

👉 Does Team Topologies still matter when AI agents can generate code, tests, and workflows at incredible speed?

The discussion dives deep into:

Cognitive load in AI-driven engineering teams
Socio-technical systems and AI adoption
Why human collaboration still matters
Stream-aligned teams in an agentic world
The evolving role of platform teams
Why enabling teams are more important than ever
AI agents as “team members” — myth or reality?
How engineering organisations scale safely with AI
Why guardrails, standards, and architecture matter more now
The balance between autonomy and control in AI-enabled organisations

One key theme runs throughout the conversation:

AI may accelerate software delivery — but the human systems around software are still critical.

As development speeds increase, organisations must rethink:

collaboration
communication
cognitive load
organisational design
engineering enablement
platform strategy
operational excellence

This is a must-watch discussion for engineering leaders, architects, platform teams, and anyone building AI-enabled software organisations.

Chapters

00:00 – Introduction
00:23 – AI, socio-technical systems, and Team Topologies
01:02 – Why cognitive load matters more in the AI era
02:07 – Drinking from the AI fire hose
03:20 – Shifting cognition from code to outcomes
04:32 – Why engineers are moving higher up the value chain
05:48 – DP1 vs DP2 organisational design principles
07:15 – Autonomy, mastery, and purpose in AI teams
08:50 – Are AI agents team members?
10:45 – Agent orchestration and organisational principles
11:44 – Why AI is not truly a “team member”
13:09 – Can you really pair program with AI?
13:52 – Stream-aligned teams in an AI world
15:34 – Jevons Paradox and accelerating software delivery
17:11 – The changing role of platform teams
18:46 – Security, governance, and AI platforms
20:31 – Why platform teams must stay ahead
21:08 – The critical role of enabling teams
22:32 – Coaching engineers to work effectively with agents
23:23 – AI anti-patterns and “We Jimmy” chaos engineering
24:54 – Complicated subsystem teams and deep expertise
27:20 – Does Team Topologies still matter?
28:06 – Constraints, guardrails, and organisational design
28:39 – Closing thoughts

Resources & References

📘 Books & Concepts Mentioned

Team Topologies — Matthew Skelton & Manuel Pais
Cognitive Load Theory
Socio-Technical Systems
Team Design Interaction Modes
Stream-Aligned Teams
Platform Teams
Enabling Teams
Complicated Subsystem Teams
Cynefin Framework
Jevons Paradox
Well-Architected Systems
AI Agent Orchestration

📚 Key Themes

AI engineering teams
Organisational design
AI agents and workflows
Platform engineering
Developer productivity
AI adoption
Engineering leadership
Team structures in AI
Guardrails and governance
Human + AI collaboration

🌐 Learn more:
https://theserverlessedge.com

Serverless CrAIc from The Serverless Edge
Check out our book The Value Flywheel Effect
Follow us on X @ServerlessEdge
Follow us on LinkedIn
Subscribe on YouTube

Send us Fan Mail

Is AI-generated code creating more value — or more liability?

In this episode of Serverless Craic, David Anderson, Mark McCann, and Michael O’Reilly explore why one of software engineering’s oldest principles is suddenly more relevant than ever in the age of AI:

“Code is a liability. The system is the asset.”

As agentic AI and code generation tools accelerate development, teams are producing more code, more tests, and more complexity than ever before.

But:

Does more code actually mean better outcomes?
Are organisations creating massive technical debt without realising it?
What happens when AI accelerates poor engineering practices?
And how do you maintain confidence, security, and quality in probabilistic systems?

This episode explores:

AI-generated code and technical debt
Validation, verification, and testing strategies
Observability and evaluation frameworks
Security vulnerabilities and unmanaged code
Critical thinking in modern software engineering
Why “lines of code” ≠ business value
The return of XP and foundational engineering principles
Chapters

00:00 – Introduction
00:24 – Old engineering principles returning in the AI era
00:51 – The return of Extreme Programming (XP)
01:43 – “Code is a liability” explained
02:46 – AI-generated code and growing technical debt
03:32 – Why engineers must review AI-generated code carefully
05:16 – The history of generated code and technical debt
06:28 – Why more code doesn’t mean more value
07:12 – AI hype, supply chains, and unmanaged complexity
08:30 – AI accelerates weak engineering practices
09:02 – Why teams still struggle with testing strategies
10:39 – Observability and deploying with confidence
11:54 – Evaluation frameworks for probabilistic systems
12:55 – System boundaries and verification
13:11 – Engineers are still accountable for AI-generated code
13:50 – Critical thinking in probabilistic systems
14:44 – Security vulnerabilities and unmanaged legacy code
16:27 – Commodity systems vs unnecessary custom code
17:25 – AI models finding security vulnerabilities
18:38 – Exploration, testing, and security charters
20:02 – Why code liability matters more than ever
20:24 – Engineering excellence as competitive advantage
20:44 – Final thoughts

Resources & References

📘 Concepts & People Mentioned

Ward Cunningham — Technical Debt
Kent Beck — Extreme Programming (XP)
Dave Farley — Continuous Delivery & modifiable systems
Dan North — Engineering practices & architecture
Elizabeth Hendrickson — “Testing = Checking + Exploring”

📚 Topics Discussed

Technical debt
AI-generated code
Agentic AI workflows
Evaluation frameworks (evals)
Observability
Continuous verification
Security scanning
Probabilistic systems
Platform engineering
Serverless architecture
Engineering excellence

Serverless CrAIc from The Serverless Edge
Check out our book The Value Flywheel Effect
Follow us on X @ServerlessEdge
Follow us on LinkedIn
Subscribe on YouTube