Kiro: A new agentic IDE

(kiro.dev)

1013 points QuinnyPig | 1 comments | 14 Jul 25 14:24 UTC | HN request time: 0.321s | 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 #

p1necone ◴[15 Jul 25 00:11 UTC] No.44566645[source]▶

>>44566625 #

The Eisenhower quote comes to mind: "Plans are worthless, but planning is everything."

replies(2): >>44566662 #>>44566671 #

1. Twirrim ◴[15 Jul 25 00:15 UTC] No.44566662[source]▶

>>44566645 #

If you don't start with approximately the right destination, you're definitely never going to end up there, even if you have to take some detours and compromise on some choices.

It gets really frustrating reviewing people's designs at times, when it's crystal clear they're a) working backwards and b) haven't really considered the customer experience at all.

One of my favourite tell tale signs of a) is when the chosen option 100% fits the specifications, doubly so if there's no cons associated with the pros. Sometimes it's genuine, but very rarely.

↑