I worked temp jobs without benefits for more years than I care to think about.
Here are some additional costs you haven't mentioned.
Medical insurance
Elder/child care
Student loan payments
Life doesn't always proceed exactly as you planned.
Here are some situations that have happened to friends and acquaintances.
Husband became addicted to Oxycontin, sold most family assets to pay for it.
Wife moved to the opposite end of the country before the husband. She was told that she wouldn't have to work and to buy everything she needed on credit cards. He left the country with no forwarding address.
My answer to a lot of these questions is "If you write code like this and check it in to our corporate repository, I will cut out your heart and make you eat it."
Your blog article doesn't contain any code or empirical data so you can expect it to be rightfully ignored.
Here are some of the elements that would make it more compelling.
* Provide a reference implementation in a widely-used language. I would pick C or Rust. The code should be under a widely used open source license, have high test coverage, and be fuzzed.
* Write a specification and conformance tests. What happens when a word is not in the dictionary or the dictionary is corrupt?
* Provide size and performance benchmarks of real-world datasets. You assert that English words can be encoded compactly so try encoding Wikipedia, Project Gutenberg books, or the text files in the Calgary Corpus.
* Compare your proposal against state of the art compression algorithms like PPM or LZMA.
* Fork a text editor application and change it to use your reference implementation. What are the effects on editing latency and RAM usage?
* Shared dictionaries were tried in the 1980s (e.g. Spellswell Word Services) but failed in the marketplace. What's different now?
[0] https://en.wikipedia.org/wiki/Class:_A_Guide_Through_the_Ame...