Verify: Retrying does not duplicate writes
Complex software engineering: Understand what a change affects
An engineering problem rarely lives in just one line of code. Requirements, validation, data flow and error feedback combine to determine behavior. Argon's engineering focus makes these relationships a useful subject for discussion.
Retrying a failed batch import, for example, involves job identifiers and the risk of writing duplicate records. Connecting the retry path to write constraints helps define the scope of a change. Reliability still needs testing in the actual project.