The Perot Museum’s new T-Rex exhibit is top notch, and packed with interesting info…but really needed a design editor. Two fonts throughout, with seemingly random decisions about which was for the headings and which body text, and whether heading were underlined…and, Lordy, why do I have to notice stuff like this!
Well, I finally had enough with MLB‘s blackout restrictions. Signed up for a VPN so I can watch all the blacked out games including them playing the Orioles right now which I can never watch. Now all I have to do is figure out how to get it working on the Apple TV.
@masukomi the first part also contradicts the second part. At first there's two sets of prints for each scene, then suddenly in the second part there's some scenes that only had one. So which is it?
Tonight's movie night movie will be, "Raising Arizona (1987)." This is another one none of us has seen for some reason. I guess it's time to remedy that!
Raising Arizona was amazing. It's like a manifestation of a feeling. It's a whole mood. I'm not sure how to mentally classify it, tbh. I think "a Coen brothers movie" is about the best I can do. They really have a gift of inducing déjà vu for experiences I've never had.
I love how in every Coen movie I've seen, the characters are seemingly dumb simpletons for the most part, but they all have a more varied and interesting vocabulary than I do. They're also all very deeply aware of their motivations in a way that I find almost envious. Everything the characters do makes perfect sense while being simultaneously absurd.
When I started CS in college (~1998) the first classes were C++. Of course I already knew some Pascal, C, VisualBasic, C++, Perl, JavaScript, etc. so I was way ahead. I didn't need to learn any of the "how to think in code" stuff so the classes were pretty boring.
Back then, I programmed by typing a few lines, hitting build to make sure it was syntactically good, typing some more, hitting build, etc. This was before IDEs did that for you (at least none I had used) by showing errors as you type.
This combined with already thinking in code meant I was really fast at finishing the tasks in the computer lab. The prof would come around and by the time she got to me I'd often be done.
Eventually she started taking a close interest and watching how I worked.
And I remember one time she says something like, "I see you're building all the time. The skill you're supposed to be developing is how to write the code correct the first time."