Implementation is where judgements go to become invisible

In a recent article on Dev.to, the author explores how software implementation often obscures the subjective judgements made during development. Through a series of anecdotes involving bug tracking, testing methodologies, and data analysis, the author demonstrates how initial conscious design choices—such as defining what constitutes a 'waiting reply' or how to measure system performance—eventually harden into invisible, unquestioned system behaviors. The piece highlights that even when code is technically correct, it may be answering the wrong question due to hidden assumptions. The author, in collaboration with Pascal Cescato, emphasizes that true software quality requires constant vigilance against these 'invisible' judgements. They suggest that developers must actively challenge their own assumptions, ensure independence in testing, and explicitly document the scope and treatment of their measurements to prevent silent failures. Ultimately, the article serves as a cautionary tale about how code can inadvertently codify bias and oversight.