Pondering: Do you have to know all the features to effectively use none of the features? 

 Years ago, I gave a talk about being locked in a vault and having to analyze a bunch of C++ code in a legal case.   I used some Python.

One thing I didn't mention in that talk is that I also looked at a lot of "prior art" which mostly consisted of 1970s assembly code.   That code, in contrast, was readable and understandable. It had flow charts.  It was a small stack of paper when printed.

Anyways, rock on Voyager! 

 A novel idea for a future science fiction show and hear me out here.... A two hour arc. 

 Whereas seeing Star Wars as a kid inspired me to see more sci-fi movies, I think I'll be fine if I never see another sci-fi film again after watching Dune 2.  Coupled with the trailers for upcoming attractions at the start,  maybe it'd be fine to never watch another movie again actually. 

 Well, it seems I'm back inside on the bike trainer now.   The cold is just hell on my hands so I'm not dealing with that.    Honestly though, the trainer is probably a better workout given the total lack of hills around here. 

 I think my main problem with the Apple Invasion TV series is that all problems seem to be solved through some kind of overwrought yelling and screaming. 

 Elderly woman getting personal care product ahead of me in line. Clerk explains that the "discount only applies next time." She walks away empty handed.  Meanwhile, I'm thinking "I'm so sick of this kind of bullshit." Slow. Clap. Walgreens. 

 All the whimsical stories and flights of fancy, finally silenced by endless focus on proper sentence structure. 

 Hard for me to believe that the Brown PL course is almost a third done already.   I feel like I'm in some kind of different time-space dimension with it.   However, I'll be back to my own courses again in December. 

 It's really too bad that "anti-pattern" typically means bad code as opposed to being opposed to a pattern for some reason--like having good taste.