How AWS Lambda Powertools enable Serverless teams to move fast with safety

An introduction to AWS Lambda Powertools for python showcasing the developer experience and how it simplifies writing code for processing Lambda events and provides developer guardrails for Instant success at scale
Ref Jones / AWS CB

Serverless Scalability Unleashed

You’ve built your application, deployed it with ease, and it’s humming along. As your user base grows and event volumes soar, soon you see performance bottlenecks, throttling, and chaos.

This session prepares you for those invisible barriers. Drawing from my experience using AWS Lambda to build high-scale, event-driven systems, explore a real system failure and hear practical strategies and patterns to help you overcome scalability challenges.

Whether you’re building greenfield applications or optimising existing systems, leave this session with the knowledge and confidence to unleash your serverless scalability.

Presented at re: Invent 2024 and Serverless Days ANZ (New Zealand) 2024

Serverless: Not just for startups?

Panel discussion
Hear from some of the most experienced minds around the business Value of Serverless. This is a leadership session targeted at getting buy in for the serverless mindset in the enterprise.

Maximise your VIBE with Powertools and Amazon Q Developer

"The hottest new programming language is English", but what happens when AI gives you code that works but isn't what you'd actually write?

I started frustrated with generic AI-generated serverless code and ended up discovering something that completely changed how I work with AI assistants. Through live demos, you'll see why "vibe coding" might be holding back your projects - and what comes next.

Walk away with a new perspective on AI pair programming and practical tools to level up your development workflow immediately.

Presented at AWS Summit Sydney 2025 in Dev Lounge as a lightning talk (20 minutes)

Forget the VIBES, Enter the Flow

Developer Experience is evolving faster than ever.

AI coding tools are fundamentally changing how we build software. But the dominant approach - "vibe coding", where developers make broad, hopeful requests to AI - is creating a new kind of technical debt. You receive code that works, but it's generic, hard to maintain, and lacks your context and standards.

Is there a better way?

This is a lightning talk to suit approx. 15 minute slot.