DEV Community

loading...

Discussion on: When DRY Doesn't Work, Go WET

Collapse
lifelongthinker profile image
Sebastian

I agree, with one "but" (big but): The value of a software product usually hinges on all three of these criteria. The chain thus is only as strong as its weakest link.

If you make it work but fail to get it right or fast, the product holds only little or short-lived value.

Thread Thread
jrop profile image
Jonathan Apodaca

Definitely agreed. I believe the point that this mnemonic attempts to get across is not "don't make it right/fast", but rather to shift ones priority focus to getting a working solution first. Then, by all means, make certain that the program is correct, and then please, oh please, make sure it does not run in exponential time.

Thread Thread
lifelongthinker profile image
Sebastian

Very well said. The quoted version alone just makes me think of all the code where people stopped after the "make it work" phase. 😂😭