[0]: https://agelab.mit.edu/methods/agnes-age-gain-now-empathy-sy...
[0]: https://agelab.mit.edu/methods/agnes-age-gain-now-empathy-sy...
- Course web page: https://cs140e.sergio.bz/
- Accompanying material by the instructor: https://github.com/dddrrreee/cs140e-24win
Disclaimer: I've only worked through the course materials when it launched in '18, haven't actually taken the course physically, so YMMV.
Keep the button, but for goodness sake stop letting cars drive through crosswalks in the "walk" phase.
I get it, 3.11.0 is "final" in the sense of "definitive" from the development team's point of view, the final one of the pre-releases. But 3.11.9 is also called "the ninth and final 3.11 bugfix update" in the schedule [1], the actual final one from the maintenance team's point of view, in the sense there will be no more.
Can't we find better terms, that work for everyone? 3.11.0 stable? 3.11.0 actual? For anyone but the dev team, this is in no way a "final" release, this is the "first" release.
> A version identifier that consists solely of a release segment and optionally an epoch identifier is termed a “final release”.
^ for anyone who wants to go on a deep dive!
Speaking of surviving Fraktur ligatures, I’m sorry that a couple of others like tz didn’t make it to Roman. It makes poor ß appear lonely.
[0]: https://www.icao.int/publications/Documents/9303_p3_cons_en....
Blindly calling .ToUpper() on anything is a typical anglo-centric mistake. Just don't use .ToUpper(), shoutcase is ugly anyways ;)
See also: one of the many "100 fallacies programmers assume about natural written language" documents or such.
Brains are weird.