Learn about how the Kiro team evolved the spec-based dev workflow and artifact structure into a feature which they wanted to use every day. Do you treat specs as point-in-time snapshots of technical decisions, or do you treat them as an ever-syncing reflection of your source code? We've found that by distinguishing technical summaries and designs from requirements, we are better able to iterate on decisions made previously in a safe, reliable manner.
The team at Kiro went through 7 fundamentally different spec implementations and interfaces internally, and feel we've only just scratched the surface on an experience worth pursuing.
Al is one of the two founding developers on Kiro, and is the tech lead for the program. He has been building developer tools for the past 4 years, working on AWS Amplify, AWS AppSync, and most recently, Kiro. He brings over a decade of experience at Amazon building products to excite and delight customers, from Prime Video to Halo, and most recently working to deliver tools for developers to build webapps using the best primitives available. A burgeoning gardener, he lives in Seattle, and is desperately trying to keep his roses alive.
