I always hate when authors waffle around instead of just getting to it.
Why couldn't:
> Today, in weird C code tricks, I want to show you a small example from Git’s source code.
> Recently, I was poking around the Git source when a directory name caught my eye, it was named “compiler-tricks”. I thought, “This is a promising name, let’s see what’s inside of it”.
> Inside this directory, there was a file called not-constant.c, and the whole file contained just this:
Have been:
> In the land of weird C code, there's an example in Git's not-constant.c:
The entire article is exhausting. So many "so why this" and "to understand this, x". Could have gotten the entire point across in perhaps 10% of the space.
It's the televisionization of the Internet. You should imagine it as a guy walking down a beach as the camera follows him looking sincerely and speaking to alleviate your loneliness and then there will be a shampoo ad!
That reminds me of an old project that I want to say was called "methbusters" that was a recut of the original mythbusters in which they cut all of the repetitions that came after every commercial break. Final product was something like 5 minutes an episode.
Why couldn't:
> Today, in weird C code tricks, I want to show you a small example from Git’s source code.
> Recently, I was poking around the Git source when a directory name caught my eye, it was named “compiler-tricks”. I thought, “This is a promising name, let’s see what’s inside of it”.
> Inside this directory, there was a file called not-constant.c, and the whole file contained just this:
Have been:
> In the land of weird C code, there's an example in Git's not-constant.c:
The entire article is exhausting. So many "so why this" and "to understand this, x". Could have gotten the entire point across in perhaps 10% of the space.