Introduction

After two decades of writing software the “proper” way — specs, sprints, commits, and countless late nights debugging — I didn’t expect to find myself vibe coding. But that’s exactly what happened when I started using Kiro IDE. Somewhere between drafting intent in natural language and refining AI-generated code, I realised I was no longer dictating to the machine — I was collaborating with it.

As an experienced programmer, I’ve spent years translating ideas into structure, logic, and syntax. But Kiro introduced something different — a way to code that feels more like co-creation than command. Instead of focusing on implementation details, I began to describe what I wanted to happen, what the system should feel like, and how the flow should behave. And the results? Surprisingly coherent, elegant, and aligned with my intent.

That’s when it clicked: this wasn’t a shortcut for beginners. It was a new creative layer for experienced developers — a shift from code-first to spec-first, from logic to vibe. In this piece, I’ll share how spec-driven development inside Kiro transformed my workflow, what “vibe coding” really means in practice, and why I believe it’s the next natural step in how we write software.