3 ms·
Good enough is by definition, good enough. It's up to the team and customers to decide on that however. Database integrity is particularly important, so with
by mixmastamyk 7y ago
Good enough is by definition, good enough.
It's up to the team and customers to decide on that however. Database integrity is particularly important, so with limited information, I'd say you made the right decision. Therefore the first draft of the code was not good enough.
So, we should all be in agreement now, right?
- docker_up 7y agoRight, but who decides what "good enough" is? If I weren't code reviewing, then it would have passed as "good enough". And that's the point of why just saying good enough isn't good enough. There should be a threshold that no one fights over.
- dwild 7y agoHe gave the threshold in his comment though. > It's up to the team and customers to decide on that however. You said yourself: >the consequences of a dupe would lead to a pretty bad customer experience. I've seen many situation were a duplicate wouldn't matter to a customer. It would matter to me because like you, I'm a perfectionist, but at the end of the day, it's both the team and customers that decide together.