From 375bedacec1297f294a32ce2424592f4d52ffca1 Mon Sep 17 00:00:00 2001 From: Alexander Goussas Date: Sun, 5 Apr 2026 21:04:00 -0500 Subject: [PATCH] fix typos --- posts/05-05-2026-how-i-read-500-page-books-in-a-weekend.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) 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. -- 2.43.0