Hacker News new | ask | show | jobs
by scarejunba 2503 days ago
Iteration speed and quality are directly related, not inversely. Iterative development allows exploring software design considerations fast which means you get to actually good software instead of getting it right the first time.

Fast iteration means you can kill ugly design. Slow iteration means you get stuck with a design choice because you discovered its flaws too late.

1 comments

That seems entirely subjective. People may go fast for meeting a deadline, or for iterating as you suggest.

Trying to determine what people do is likely a futile discussion.

Finally, by writing decoupled, modular software, you are always free to reassemble it later (discarding/rewriting undesired parts), no matter when it was originally assembled.

This is something that has actually been researched, so it's not accurate to say it's subjective. Higher release rates (i.e. an iterative approach) cause higher organisational performance. See Accelerate, by Forsgren et al.