By Kevin Azijn


Are you still writing code line by line, or are you engineering solutions? Werner Vogels, Amazon's CTO, coined the term "renaissance developer" to describe the modern software engineer who combines deep technical expertise with broad systems thinking and architectural vision. But many developers fear AI coding tools will replace them, question their value, or simply don't see how these tools fit into their workflow. In this session, we'll address these concerns head-on and explore what it truly means to be a renaissance developer—and why this evolution is an opportunity, not a threat.

We'll spend the first half discussing: Why developers distrust AI coding tools and why those fears can be alleviated by proper guardrails, specifications to reduce ambiguity and human review The perceived lack of value in AI-assisted development and the reality How the renaissance developer mindset makes you more influential, impactful, and productive Why spec-driven development amplifies your expertise rather than replacing it

In the second half, we'll demonstrate how Kiro, AWS's spec-driven agentic IDE, enables Java developers and architects to focus on what matters most: architectural thinking, strategic decisions, and delivering value. Through live demonstrations, you'll see: Assisted Code quality improvements: fixing +100's SonarQube (or other tool's) warnings Legacy modernization (Java 8 → Java 21) completed in hours instead of days Feature extension (adding GraphQL) without breaking existing systems Performance optimization (fixing N+1 queries) with systematic analysis

This isn't "vibe coding" or AI magic—it's transparent, reviewable, spec-driven development where you define WHAT needs to be built and Kiro handles HOW to implement it. The future doesn't belong to developers who write more code — it belongs to renaissance developers who engineer better solutions.

Jfokus

A conference talk introducing the 'Renaissance Developer' concept and demonstrating spec-driven development using the Kiro AI coding IDE. The talk outlines five mindsets for modern developers: curiosity, systems thinking, communication, ownership, and being a polymath. The demo shows how Kiro generates requirements, technical design, and task lists from a simple one-liner prompt, using the Spring Pet Clinic app as a base to add Amazon Cognito authentication. Key workflow elements include agent steering docs, MCP servers for documentation access, spec-driven context management, and hooks for automating repetitive tasks like changelogs and linting. The core message is that AI tools accelerate the 'quicker' part of development, but quality, safety, and ownership remain human responsibilities.

The Renaissance Developer: Building Better, Safer, & Quicker with AI-Powered Spec-Driven Development