3 ms·
The point is that sometimes you don't know the spec is wrong until you've built the software and it's being used.
by ytoawwhra92 6mo ago
The point is that sometimes you don't know the spec is wrong until you've built the software and it's being used.
- 9dev 6mo agoStill 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.
- ytoawwhra92 6mo agoYes, that's agile software development.
- 9dev 6mo agoNo, 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.
- deleted 6mo ago[deleted]
- zelphirkalt 6mo agoUntil the agents start touching things that already worked well before and break them.
- jeremyjh 6mo agoThey do need a competent developer operating them. That has nothing to do with whether nor not specs have value.