<!DOCTYPE html>
<html>
-<head>
- <meta charset="utf-8">
- <title>Alexander Goussas | Programming</title>
- <meta name="author" content="Alexander Goussas">
- <meta name="description" content="Blog about programming">
- <meta name="viewport" content="width=device-width, initial-scale=1">
- <link href="https://cdn.jsdelivr.net/npm/
[email protected]/dist/cdn/beer.min.css" rel="stylesheet">
-</head>
+ <head>
+ <meta charset="utf-8">
+ <title>Alexander Goussas | Programming</title>
+ <meta name="author" content="Alexander Goussas">
+ <meta name="description" content="Blog about programming">
+ <meta name="viewport" content="width=device-width, initial-scale=1">
+ <link href="https://cdn.jsdelivr.net/npm/
[email protected]/dist/cdn/beer.min.css" rel="stylesheet">
+ <link href="../styles.css" rel="stylesheet">
+ </head>
-<body>
- <h1>How I Read 500 Page Books in a Weekend</h1>
- <p>
+ <body>
+ <h1>How I Read 500 Page Books in a Weekend</h1>
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.
- </p>
-</body>
+ </p>
+ <p>
+ 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.
+ </p>
+ <p>
+ Thus, I can skim/skip most of the content. Now, I do skim most of the times rather than skipping, because
+ there <i>might</i> something that I don't know, some way in which the semantics of the concept changes for
+ this programming language. So, I <i>do</i> read everything, I just do it super fast.
+ </p>
+ <p>
+ 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.
+ </p>
+ <p>
+ 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.
+ </p>
+ </body>
</html>
projects / frustrated-functor.dev.git / commitdiff