{'fraction_non_alphanumeric': 0.02434782608695652, 'fraction_numerical': 0.0017391304347826088, 'mean_word_length': 4.76, '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}}
Part VI. Redesigning: Why and how: Learning from earlier systems: When redesigning to correct flaws, add capabilities, or update aging features, figuring out what to keep and why is as important as knowing what to change

The author explores how figuring out what to keep and why is as important as knowing what to change when redesigning to correct flaws, add capabilities, or update aging features. The design of the DC-3 airliner and other examples are briefly discussed. The value of keeping the basic structure is considered, and the redesign process itself is examined.