[ParetoOptimal]

> The problem I’ve run into is that when you’re iterating fast, writing code takes double the time when you also have to write the tests.

That was the time it took to actually write working code for that feature.

The version of "working code" that took 50% as long was just a con to fool people into thinking you'd finished until they move onto other things and a "perfectly acceptable" regression is discovered.

[discreteevent]

The reason someone is iterating fast is usually because they are trying to discover the best solution to a problem by building things. Once they have found this then they can write "working code". But they don't want to have to write tests for all the approaches that didn't work and will be thrown away after the prototyping phase.