Post History

Source: https://writers.stackexchange.com/a/48706
License name: CC BY-SA 4.0
License URL: https://creativecommons.org/licenses/by-sa/4.0/

# Text Compression

Compression of text is a lot like refactoring code. A lot of people here code, so maybe they'll appreciate this concept

## Abstraction

A complex idea can often be represented by a single word. When you have a lot of words, see if there's a more concise, well-understood, word or phrase that could replace everything else.

## Fuzzy Compression/Language

You may not need to actually express an idea. So if you are vague or point in a direction with your language the reader may assume the missing context. Like with JPEGs painting a rough picture may be better than spelling it out in detail.

## Assert By Reference

If the point doesn't need to be made in text, refer to something else instead of restating something else you've said elsewhere. Saying one thing and only one thing in a location gives you the power to write a thing once and be done.

## Remove Duplicates

Track each idea that a sentence conveys and determine which sentences achieve the same things and pick one to achieve that point/idea instead of doing it multiple times.

## Elimination

If you know what you want to say. (Potentially you have a list of points you want to make). You can judge whether any given sentence helps you achieve your point. You can eliminate sentences, paragraphs, chapters, or just clauses and words in this way.

# Summary

These have been some high-level abstract ways of describing a lot of the rules of thumb Amadeus posted. He has largely favored Abstraction & Elimination. And in my experience those two are usually enough. Your tool will often depend on your form and audience. And just like algorithms for compressing data there are limits to what you can achieve as the space gets smaller, so you may need to adjust your goals themselves in order to apply the Elimination tool enough to meet the restrictions of your form.

Original score: 0