I'm souring on reading papers. 

For example, "Keeping CALM" is a really well written paper that introduces a new concept (monotonicity). But what can you actually do with this in terms of designing or evaluating a system like Farcaster or Ethereum?

Not much - it's just a well articulated restatement of some core distributed systems consistency principles that we've known for a while. 

Most CS papers don't really seem to do "Science" anymore - there are a few important ones, but the vast majority are publications for the sake of publications.

I'm souring on reading papers. 

For example, "Keeping CALM" is a really well written paper that introduces a new concept (monotonicity). But what can you actually do with this in terms of designing or evaluating a system like Farcaster or Ethereum?

Not much - it's just a well articulated restatement of some core distributed systems consistency principles that we've known for a while. 

Most CS papers don't really seem to do "Science" anymore - there are a few important ones, but the vast majority are publications for the sake of publications. 

https://arxiv.org/abs/1901.01930

I spent 7 years in the academic/peer reviewed paper world and have built a stack to replace all of that cruft.

Instead of LaTex or Markdown we use Scroll. Instead of arxiv, we have git backed ScrollHub http://hub.scroll.pub/.

Everything is 10x faster than the old stack already. Everything is public domain and open source. We will eat the whole paper publishing world.

It's also important to reemphasize that intelligence decreases as paper size increases [https://breckyunits.com/intelligence.html].

Watson and Crick; Einstein; etc. Breakthrough papers are short.

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun