From: Alexander Goussas Date: Mon, 6 Apr 2026 02:04:00 +0000 (-0500) Subject: fix typos X-Git-Tag: v0.0.1~18 X-Git-Url: http://git.frustrated-labs.net/?a=commitdiff_plain;h=375bedacec1297f294a32ce2424592f4d52ffca1;p=frustrated-functor.dev.git fix typos --- diff --git a/posts/05-05-2026-how-i-read-500-page-books-in-a-weekend.html b/posts/05-05-2026-how-i-read-500-page-books-in-a-weekend.html index 35095fb..61660e9 100644 --- a/posts/05-05-2026-how-i-read-500-page-books-in-a-weekend.html +++ b/posts/05-05-2026-how-i-read-500-page-books-in-a-weekend.html @@ -32,8 +32,8 @@

Another point is that most of the times, if a programming book is 500 pages long, chances are most of its contents is not 100% relevant. The book I'm reading right now for example is full with the author's "humor." - Humor in programming books is welcome, at least by me, in sparse quantities. If I wanted to laugh I'd listen to - audios of americans speaking french instead. + Humor in programming books is welcomed, at least by me, in sparse quantities. If I wanted to laugh I'd listen to + audios of americans trying to speak French instead.

So yeah, the key to reading programming books fast is reading so many of them that you can skim/skip a lot.