This is indeed one of the things I love about programming, in a private capacity. Sadly, it doesn't prevent programming managers and career climbers from arguing in advance over which pet methodology is more likely to lead to correct code, making power plays via engineering process proposals, and mounting all manner of blustering, persuasive, politically-motivated initiatives, usually without any actual data to back any of it up.

Then, when the code is done and testable, those people can credit/blame the successes/failures to whatever suits them.