Kiro.dev Changed How I Think About Writing Code (And I'm Not Going Back)
It's Not Just Another Copilot Clone - It Actually Thinks Before It Codes
Sherin Joseph Roy Co-Founder & Head of Products at DeepMost AI, Bangalore, India. What I'm Building At DeepMost AI, I'm focused on solving the trust gap in enterprise artificial intelligence. We build AI systems with contextual intelligence—technology that understands business context, organizational constraints, and when to admit uncertainty rather than providing confident but unreliable answers. What I Write About Through "Notes by Sherin," I share:
The reality of AI adoption in enterprises (beyond the hype) Product development in rapidly evolving markets Honest reflections on building a company in the AI space Human-centered approaches to technology development Lessons learned from both successful and failed implementations My Approach
I believe the most valuable AI systems will be those that augment human judgment rather than attempt to replace it. Technology should make us better thinkers, not do our thinking for us. This philosophy shapes everything we build at DeepMost. Background Before co-founding DeepMost AI, I spent years in product development and system architecture. I combine technical depth in AI with practical understanding of how organizations actually adopt and use technology. A Note on Names My legal name is Sherin Roy. Joseph is my baptismal name, which I use consistently across all professional contexts. Both names refer to the same person—me. Connect
Website: sherinjosephroy.link Company: DeepMost AI https://deepmostai.com Location: Bangalore, India
Writing for builders, founders, and anyone interested in creating technology that's meaningful over impressive.
Look, I've tried a lot of AI coding tools. GitHub Copilot, Cursor, all the usual suspects. They're fine. They autocomplete my code, sometimes they get it right, sometimes they don't. But Kiro? It's different in a way that took me a while to fully appreciate.
The "Aha" Moment That Got Me
Last Thursday, 11 PM. I'm staring at my screen, trying to architect a new microservice for handling file uploads with encryption. You know the feeling - you understand what needs to happen, but there's this gap between the idea in your head and the actual implementation. The mental overhead of figuring out the structure, the security considerations, the error handling... it's exhausting.
I wrote maybe four lines in a spec file. Just basic requirements, nothing fancy. What Kiro did next honestly caught me off guard - it didn't just spit out code. It wrote user stories. Like, actual product manager-level user stories with edge cases I hadn't even considered yet.
That's when it clicked for me. This thing isn't just another code generator.
It's Like Having a Senior Dev Who Never Gets Tired
You know what bugs me about most AI tools? They're reactive. You ask, they answer. You prompt, they generate. It's this constant back-and-forth dance where you're still doing most of the mental heavy lifting.
Kiro flipped that completely. I set up a simple hook - whenever I save a file, it automatically:
Generates unit tests (that actually make sense)
Updates my documentation
Checks for performance bottlenecks
Suggests security improvements
I literally forgot I had set this up until I noticed my test coverage had jumped from 40% to 85% without me writing a single test. The documentation that usually sits there getting stale? Always up to date now.
The Learning Loop That Actually Works
Here's something nobody talks about with AI tools - they usually make you worse at your job. You get lazy, you stop understanding what's happening under the hood. With Kiro, it's the opposite.
I've been tinkering with Terraform lately (cloud infrastructure as code, if you're not familiar). Normally, learning a new tech stack means hours of documentation, trial and error, and a lot of frustrated Googling at 2 AM.
With Kiro, I just... started building. But here's the kicker - it explains what it's doing as it goes. Not in that annoying, over-explained way, but contextually. It shows you patterns, explains why certain approaches are better, and lets you experiment without the fear of breaking everything.
Last weekend, I built a game. Me. A backend developer who thinks CSS is dark magic. Built. A. Game. And I understood every line of code.
The Spec-Driven Thing Is Actually Genius
I used to think specs were corporate bureaucracy. Write the code, ship it, move on. But Kiro made me realize something - specs aren't documentation, they're thinking tools.
When you write specs with Kiro, you're not filling out forms. You're having a conversation about what you want to build. And it fills in the gaps with stuff you didn't even know you needed. Security headers? Already there. Error boundaries? Implemented. Accessibility features? Yep, those too.
It's like Kiro has absorbed the collective knowledge of every best practice blog post and actually applies them without you having to remember them all.
Real Talk: What Actually Happened to My Workflow
Before Kiro:
Monday: Plan the feature
Tuesday-Thursday: Write code, debug, rewrite
Friday: Scramble to add tests and documentation
Following Monday: Fix the bugs I missed
After Kiro:
Monday morning: Write a spec
Monday afternoon: Review and tweak the generated implementation
Tuesday: Ship it
Rest of the week: Actually work on interesting problems
I built a secure file-sharing app in two days. Not a prototype. Not a "it works on my machine" version. A production-ready app with encryption, proper error handling, and comprehensive tests. Two. Days.
The Part That Nobody Mentions
You know what really sold me? Kiro doesn't make me feel stupid.
Every developer has those moments where you're stuck on something that feels like it should be simple. With other tools, you're still stuck, just with fancier autocomplete. With Kiro, you can literally ask the "dumb" questions. How do I structure this? What's the best pattern here? Why isn't this working?
And it just... helps. No judgment, no "as an AI language model" nonsense. Just solid, contextual help that makes you better at your job.
Why This Matters (Beyond Just Writing Code Faster)
Startups die because they can't ship fast enough. Senior devs burn out because they're doing the same repetitive tasks over and over. Junior devs struggle because the gap between tutorials and real-world code is massive.
Kiro addresses all of this. It's not just about writing code faster - it's about thinking about code better. It's about having the mundane stuff handled so you can focus on the problems that actually need human creativity.
Look, I'm Not Saying It's Perfect
Sometimes it generates something weird. Sometimes you need to guide it more explicitly. It's still software, not magic.
But here's the thing - even when it's wrong, it's wrong in interesting ways that make me think differently about the problem. And when it's right (which is most of the time), it's not just correct, it's good. Like, senior-developer-who-actually-cares-about-code-quality good.
The Bottom Line
I've been coding for years, and I can count on one hand the tools that have fundamentally changed how I work. Git. Docker. And now Kiro.
It's not just another AI assistant. It's more like having a really smart colleague who never gets tired, never judges your questions, and somehow knows all the best practices you keep forgetting to implement.
If you're tired of AI tools that just autocomplete your thoughts instead of elevating them, give Kiro a shot. Worst case, you'll write some good code faster. Best case? You'll remember why you fell in love with building things in the first place.
P.S. - No, they didn't pay me to write this. I'm just genuinely excited about a tool that actually delivers on the AI hype for once. Also, my test coverage is still at 85% and I still haven't written those tests manually. Just saying.
