jbrains

Of the ones I tried to read, Atlas Shrugged, and it's not even close.

Never program a computer you can't unplug.

Canadian. Didn't see this option yet. Anyone else?

As a young person with an interest in languages and an eye towards working professionally as a computer programmer, I found this story especially delightful. It was one of the ones that led me to read more Clarke.

And the parenthetical near the end hit me even harder than the last line did.

Chronologically LOST.

Write comments that explain why the code isn't obvious just by reading it. Why did you do things the long way? What did you need to work around? Why didn't you do the thing that anyone reading the code would expect you to do?

Also write comments that explain the purpose of the functions you use, in case the names of those functions don't make it clear on their own.

I find it uncomfortable not to understand. It has taken me decades to make peace with the notion that being different is not only acceptable, but good. Many people don't get me, but the ones who do become friends for life. Many people find things interesting or enjoyable that would make me cry from boredom.

I've chosen to find it charming.

You might be able to do that, too. If not now, then one day. It took me a long time.

Peace.

APL is Ithkuil.

The Handmaid's Tale

We

Nightfall

The Terminal Experiment

The fact that the loop is doing "find first driver matching these strange criteria" seems most obviously obscured by the pattern of assigning a value, then killing the loop or not. This strikes me as the part that makes the algorithm tedious to test, since it forces us to use a collection to test the intricacies of the inner conditions.

Once we isolate "find first driver matching condition" from computing the condition for each driver, I consider the rest a question of personal taste. Specification pattern, composition of filters, something like that. Whatever you find easier to follow.

Only if temperature distribution is a continuous function.