{'fraction_non_alphanumeric': 0.013821138211382113, 'fraction_numerical': 0.0, 'mean_word_length': 5.155, '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}}
Programming by semantic refinement

It is becoming increasingly evident that human programmers are not capable of efficiently producing reliable programs if they must be concerned initially with every detail of the final program. The approach described here is one of “semantic levels of programming”, which involves a graduated approach to the production of programs.
 A common but fallacious belief of some software implementors today is that the efficient execution of software systems should be a major concern in the initial system version. In fact, the primary concern in the initial version should be the reliable operation of the system, which is closely connected with the existence of a sound, overall system design. Assuming that we recognize that there is some reasonable time from the initiation of a software system implementation project to the availability of an initial version, the philosophy of semantic refinement is based on the belief that: “If a major concern in the implementation of the initial version of a software system is efficiency, then the initial version will be unreliable.” Many systems which are initially unreliable have a way of remaining unreliable for a discouragingly long period of time.