←back to thread

Kiro: A new agentic IDE

(kiro.dev)
1016 points QuinnyPig | 1 comments | 14 Jul 25 14:24 UTC | HN request time: 0.234s | source
Show context
manbash ◴[15 Jul 25 00:05 UTC] No.44566625[source]▶
> 2. Technical design based on requirements > Kiro then generates a design document by analyzing your codebase and approved spec requirements. It creates data flow diagrams, TypeScript interfaces, database schemas, and API endpoints—like the Review interfaces for our review system. This eliminates the lengthy back-and-forth on requirements clarity that typically slows development.

This is nice for documentation but really having a design document after-the-fact doesn't really help much. Designing is a decision-making process before the code is written.

replies(4): >>44566645 #>>44566655 #>>44566676 #>>44567106 #
1. the_arun ◴[15 Jul 25 00:19 UTC] No.44566676[source]▶
I slightly disagree. Plans are really useful for enhancements. If we stick to original plans & patterns as we extend & add new features, we can slow down the decay process.