From f353d3f8ea2f2cd1afea38e901a149c9cbe3f471 Mon Sep 17 00:00:00 2001 From: Alexander Goussas Date: Sun, 5 Apr 2026 21:00:06 -0500 Subject: [PATCH] update first post --- index.html | 1 + ...ow-i-read-500-page-books-in-a-weekend.html | 48 ++++++++++++++----- styles.css | 14 ++++++ 3 files changed, 50 insertions(+), 13 deletions(-) create mode 100644 styles.css diff --git a/index.html b/index.html index e06660d..9130eec 100644 --- a/index.html +++ b/index.html @@ -8,6 +8,7 @@ + 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 9a08cc0..e1b23b2 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 @@ -1,22 +1,44 @@ - - - Alexander Goussas | Programming - - - - - + + + Alexander Goussas | Programming + + + + + + - -

How I Read 500 Page Books in a Weekend

+ +

How I Read 500 Page Books in a Weekend

There are two types of books that I can read in a weekend, no matter how large they are: programming [language] books and fantasy books that I'm hooked. The latter is self-explanatory, I think, but the former might require some explanation. -

- +

+ The thing is, most programming languages hide the same semantics behind different syntax. + For example, right now I am reading a Zig book. I am already fairly experienced with C and C++, + so I don't need to waste time reading how pointers and memory allocation works. I just need to know + how to do these things with Zig's syntax. +

+ Thus, I can skim/skip most of the content. Now, I do skim most of the times rather than skipping, because + there might something that I don't know, some way in which the semantics of the concept changes for + this programming language. So, I do read everything, I just do it super fast. +

+ 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. +

+ So yeah, the key to reading programming books fast is reading so many of them that you can skim/skip a lot. + And in terms of fiction or whatever you like reading, the key is liking the book and not having social life. +

+ diff --git a/styles.css b/styles.css new file mode 100644 index 0000000..ec02c07 --- /dev/null +++ b/styles.css @@ -0,0 +1,14 @@ +body { + width: 60%; + margin: auto; + margin-top: 1rem; + margin-bottom: 1rem; +} + +h1, h2 { + text-align: center; +} + +a { + text-decoration: underline; +} -- 2.43.0