{'fraction_non_alphanumeric': 0.024255788313120176, 'fraction_numerical': 0.0, 'mean_word_length': 4.710691823899371, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Tell Less, Say More: The Power of Implicitness

Implicitness is a very practical feature of OO development, as distinctive as anything that is routinely considered part of the definition. It is the constant refusal to say more than what we strictly need to say. The double refusal (refusal to close, refusal to assert completeness) requires some intellectual audacity, but yields a productive development process. In the end, what resolves the contradiction is the release of the software. The release process (the process of closing what was until now open) is the process of equating each type with the Cartesian product of its properties. So when everything has been said, the objects are indeed what they have. But only at the end. Until then, you always leave room for more properties. Everything is open until officially closed; and by telling less now you retain the possibility of saying more later.