[Ensorceled]

> Has anyone else considered that producing code faster isn't necessarily a good thing?

This has been an relentless goal of the industry for my entire 40 year career.

> At a point you're more work for your self/organization because unless you get everything perfect the first time you're creating more work than you're resolving.

Nothing is correct the first time (or rarely). Accelerating the loop of build, test, re-evaluate is a good thing.

[threethirtytwo]

I think you captured yet. Not many people agree but the real world metrics speak the truth, and that is trying and failing faster gets you further then methodological planning and structured approaches.

There IS experimental evidence on this and anyones anecdotal opinion is instantly blown to smithereens by the fact that this was tested and producing code faster is provably better.