<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Sensus Plenior]]></title><description><![CDATA[Sensus Plenior]]></description><link>https://blog.felipe.app</link><generator>RSS for Node</generator><lastBuildDate>Wed, 29 Apr 2026 21:19:00 GMT</lastBuildDate><atom:link href="https://blog.felipe.app/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Books you should not read]]></title><description><![CDATA[Most modern self-help and business books should not be read. They seem to follow the same formula:

Come up with an overpromising title (e.g. the new science of X! a groundbreaking way of Y!)

Devote the first 100 or so pages to explain why your idea...]]></description><link>https://blog.felipe.app/books-you-should-not-read</link><guid isPermaLink="true">https://blog.felipe.app/books-you-should-not-read</guid><category><![CDATA[books]]></category><dc:creator><![CDATA[Felipe Scheidemantel]]></dc:creator><pubDate>Mon, 12 Dec 2022 00:43:50 GMT</pubDate><content:encoded><![CDATA[<p>Most modern self-help and business books should not be read. They seem to follow the same formula:</p>
<ul>
<li><p>Come up with an overpromising title (e.g. the new science of X! a groundbreaking way of Y!)</p>
</li>
<li><p>Devote the first 100 or so pages to explain why your idea is important. Do so by endlessly repeating success stories that exemplify your idea and by citing other books (mostly other modern self-help/business books).</p>
</li>
<li><p>Explain to the reader that the next section of the book will offer practicable, actionable advice. Break this advice into techniques (or steps, or whatever you want to call them) and add in more anecdotes and citations that prove that the techniques work.</p>
</li>
<li><p>Wrap up the book by adding 100 more pages of anecdotes that corroborate how important and life-changing your idea is.</p>
</li>
</ul>
<p>If you must read these books, skip the first section entirely and go straight to the section with practical advice. Skim through the anecdotes and try to find where the techniques are hidden. You will usually be able to find a few important insights in such books if you do so, but there are often other ways that yield the same result with much less effort.</p>
<p>I like to check the 3-star reviews on Goodreads first. If I see many instances of "this could have been a blog post", "interesting idea repeated endlessly" and "the book could be made 90% shorter", I discard the book right there. The book's core insights can usually be found in the TLDR reviews.</p>
<p>Another tip is to check the author's blog first. Try to read a few blog posts and check if it is realistic to expect that the book will significantly develop these ideas. I recently found a blog where the posts were much deeper than the $30 book the author was selling. It's almost as if the blog is a space where the author can explore her own voice rather than conforming to a standard set by publishers.</p>
<p>I am a voracious reader and usually hesitate to abandon a book, but doing so with these books has allowed me to invest much more time into good literature and technical, demanding books (SICP comes to mind).</p>
]]></content:encoded></item></channel></rss>