I thought I had seen it before. Verified you can actually see the whole chapter in a nicer (book vs web) layout in Amazon's "Look inside" feature since it's at the beginning of the book.
This is a story of the women behind a successful man. But no. Gender doesn't matter. Look at some successful start-ups. You need a founder like Claude Shannon to come up with a successful idea and another founder like Betty to fill in all the gaps and implement it. Such partnership is, IMHO, the essential formula for success. It is rare to have both traits in the same person.
Same in git commit message, we need to put as much information as possible in the fewest number of bytes to make it useful. I am looking forward to an article name "committese"
I use these 7 git commit message style rules [1] to establish my foundation of "committese". Things like "Use the imperative mood in the subject line" give commit messages a succint, consistent style.
Everything after that is finesse, personal effort, and ability to express things succinctly (much like the personalized "headlinese" styles mentioned).
> They are not including any PII... while creating a new identifier for each installation. 13 bits of entropy probably isn't a unique identifier iff you only look at that header in isolation. Combined with at least 24 additional bits[1] of entropy from the IPv4 Source Address field Google receives >=37 bits of entropy, which is almost certainly a unique ID for the browser. Linking that browser ID to a personal account is trivial as soon as someone logs in to any Google service.
Now this is interesting. If without that 13 bits of entropy, what will Google lost? Is it because of this 13 bits then Google suddenly able to track what they were not? If the IPv4 address, user-agent string, or some other behavior is sufficient to reveal a great deal of stuff, we have a more serious problem than that 13 bits. I agree that 13-bit seed is a concern. But I am wondering if it is a concern per se, or its orchestration with something else. Of course, how/whether Google keeps those data also matters.
>Now this is interesting. If without that 13 bits of entropy, what will Google lost? Is it because of this 13 bits then Google suddenly able to track what they were not?
At the very least, having those 13 bits of entropy along with a /24 subnet allows you to have device-level granularity, whereas a /24 subnet may be shared by hundreds of households.
You missed one important point about Turbo C: The debugger. It has an amazing UI even at today's standard. If you need an all-in-one tool to teach programming (esp focus on the concepts), Turbo C is still a good choice.
Give you an example: A highway in my neighborhood is congested often but if you can put 3 people in your car, you are eligible to use the HOV lane and usually you can watch the cars next to you moving slowly while you can go in 50mph. Google won't know you are eligible for HOV lane and assume you are not.
Passing on the business to sons and daughters is the habit of the East Asia, as well as the reason for businesses to fail. I am from Hong Kong and we keep laughing at a handful of local banks of staying in the 1960s for this reason. Similarly in Japan, but they find a brilliant way to work around this tradition: Business owners adopt adults as sons so that they can pass on the company to the right hands.
