undefined | Better HN

0 pointsytoawwhra921mo ago0 comments

The point is that sometimes you don't know the spec is wrong until you've built the software and it's being used.

0 comments

9dev1mo ago

Still though, that cycle can be iterated many times in a single day. Write a spec, let the agent build it, use the software, evaluate results, repeat.

ytoawwhra92OP1mo ago

Yes, that's agile software development.

9dev1mo ago

No, not quite. The specifications we use for agents make any ticket written before them pale in comparison. That enables a hybrid workflow that is both spec-driven and "agile", in the sense that you're doing very rapid development cycles.

1 more reply

zelphirkalt1mo ago

Until the agents start touching things that already worked well before and break them.

jeremyjh1mo ago

They do need a competent developer operating them. That has nothing to do with whether nor not specs have value.

j / k navigate · click thread line to collapse

0 comments

9dev1mo ago

Still though, that cycle can be iterated many times in a single day. Write a spec, let the agent build it, use the software, evaluate results, repeat.

ytoawwhra92OP1mo ago

Yes, that's agile software development.

9dev1mo ago

1 more reply

zelphirkalt1mo ago

Until the agents start touching things that already worked well before and break them.

jeremyjh1mo ago

They do need a competent developer operating them. That has nothing to do with whether nor not specs have value.

j / k navigate · click thread line to collapse