I was just going through the gopher space and disovered this nice doc:

UNIX PRINCIPLES DOGMATIC

1. small is beautiful
2. make each program do one thing well
3. build a prototype as soon as possible
4. choose portability over efficiency
5. store numerical data as flat ascii files
6. use software leverage to your advantage
7. use shell scripts to increase leverage and portability
8. avoid captive user interface
9. make every program a filter

I found that in documents of gopher://bitreich.org:70/1/documents 

I've been thinking a lot about some of those points and will want to go on
exploring them systematically. I actually work on a computer and run a very
small company with a friend. Therefore I am able to use whatever solutions I
want. And so I've been focusing on the points 4 and 5 a lot. Portability of
formats. 4 and 5 are actually almost the same thing: just use text files when
possible. So for data I try to use csv and tsv whilst for text I try to use txt,
md. When pdfs are needed then they can be done via groff, latex, asciidocs, or
whatever. Sheets can be done with sc-im I guess, although that's the one thing
where I use ods as I need to work with others too. I use plain text in mails via
neomutt, I do accounting in hledger. Recently I discovered recutils from GNU for
creating plain text databases instead of using sqlite. I only make one db at
this moment but I am only beginning to learn it. Such a cool little software!  I
encourage people who want to have databases and they don't exceed thousands of
entries to try it. So if I can use it for work it is a feasable solution for
small to medium projects at least. You can take your text files and open them
with any editor you want. You'll be able to open them in 10, 20, 30 years and
read them.  They are easy to backup, store (such small space), archive, encrypt,
grep, sed, whatever you want.