arthurdenture

This is way more pleasant than the kazoo version by famous children's author Sandra Boynton. https://www.youtube.com/watch?v=U14IBek-wNU

There's also a Youtuber who did this type of journey from San Francisco to Seattle (https://www.youtube.com/watch?v=7OQwA95sMbg) and to Los Angeles (https://www.youtube.com/watch?v=S-Jdfkuy9Ik).

> Something that surprised me is that [1] is of a minor key, but the solfege marks are for the relative major

Major and minor keys use the same shapes / solfege system. The major scale is "fa, so, la, fa, so, la, mi, fa", while the minor scale uses the same syllables but starts on la. This means that the shapes always represent the same intervals (i.e. pattern of whole and half steps) whether a song is in a major or minor. It's hard to describe but makes sense when singing.

One limitation is that the shapes are really only useful for singing, not for instrumental music. They also would not be meaningful for music that switches keys or that isn't tonal (i.e. isn't in a particular key at all). So they are a very good fit for what you might think of as "church music" (at least written before the 20th century), but for other settings they would be either meaningless or a hindrance.

That's one reason shape notation never caught on; another reason is that the notation was introduced by publishers of American sacred music and not by, say, music conservatories.

Is it possible that many of those uses predate the current zoning? There are numerous buildings in Chicago that would not be permitted by their current zoning.

I asked imagen 2 to generate a transparent product icon image, and it generated an actual grey and white square pattern as the background of the image... https://imgur.com/a/KA2yWHp

Extremely useful .gitconfig snippet:

  [alias]
   git = !sl

catches e.g. `git git status`, which I run shockingly often.

That was the case many years ago (extremely customized perforce server), but after that there was a full rewrite as a distributed system built on Bigtable etc. - https://cacm.acm.org/magazines/2016/7/204032-why-google-stor... is an overview. It wasn't a ship-of-Theseus type situation where they incrementally replaced components.

You're comparing regional rail terminal stations, which serve many lower-frequency lines, to subway platforms, which typically serve a single higher-frequency line. (2-10 minutes between trains.) That's the scenario where a mezzanine is less useful.

I completely agree with the more general point, that consuming external data requires a validation layer. But oh boy do I have feelings about class-validator.

Here's what it looks like to correctly annotate an array of objects with with class-validator and json-schema annotations:

  @ApiProperty({ type: Foo, isArray: true })
  @ValidateNested({ each: true })
  @Type(() => Foo)
  @IsArray()
  items: Foo[];

It's not just that you have to define everything in triplicate, it's that the failure mode for forgetting any of the above is to silently not validate your data. Unless you're very careful, you don't get the safety benefits that were the whole point of using class-validator in the first place.

If I were starting from scratch, I would instead consider either io-ts or a solution that involves a code generation step, where this entire category of risk is avoided.

The alternative would be to write a side effect inside your `render()` function, which is illegal -- it breaks the new Concurrent mode rendering, which can call render() speculatively.

I mean, I see why it's intuitively unappealing to you, but there are perfectly good reasons for the design.

Interactions can be extremely negative without making the news.

That is very good to hear. I've used Emacs for a decade, but I recently switched to VS Code because JSX support in Emacs was such a mess.

That's great as long as the insurance company deigns to cover you. Before the ACA, that was not guaranteed.

For instance, the polonaise attributed to Kosciuszko might have been composed by someone else. Wikipedia reports the composition as fact, but https://polishmusic.usc.edu/research/dances/polonaise/ suggests otherwise.

Heh, be thankful you figured out the problem before taking it in for hardware repairs: https://9to5mac.com/2019/06/11/macbook-pro-problem/

Origin: https://tinyletter.com/data-is-plural

lit-html is context-aware and safe, just like JSX. It's not a raw string templating library.

https://lit-html.polymer-project.org/guide/template-referenc...

+1 to freetaxusa. I started using them a decade ago when I first had to file taxes, and I've been pleasantly surprised that they have remained a good choice this whole time. The product doesn't even feel like it has changed much (other than the never-ending tax law changes) over the years, which is a rarity for web-based products. It just does what it needs to do.

Eb is probably disproportionately popular due to the common practice of tuning guitars down a half step, making Eb instead of E the natural/easy root chord.

I'm not sure why F would be more popular than D and A. One hypothesis would be that it has fewer accidentals; it's not a fun key for guitars, but many contemporary pop songs aren't guitar-driven anyway.

No, if the majority of drivers want to drive faster than 35mph, the road is badly designed. It needs traffic calming devices, such as narrower lanes, curb extensions, and, yes, raised crosswalks. Enforcement (including automated enforcement) is a useful tool, but the start should be designing the road so that drivers naturally go at a safe speed.

Similarly, overly elaborate test code can itself be buggy. A specific instance of this anti-pattern is when the test code duplicates the same logic as the code under test, logic which turns out to be incorrect.

In test code, I am a lot more tolerant of straight-line repetition in the name of simplicity, in a manner that would be worth abstracting were it in non-test-code.

As someone with prosopagnosia, I definitely rely on cues like hair. (It works until someone gets a haircut or changes their facial hair.)

There used to be a great face blindness test online where it first showed you a bunch of full pictures of heads to memorize, then for the quiz it showed cutouts of just the face. I had no idea that I was relying on all these non-face features until they were dramatically removed for that test. (Which I bombed.)

> Do you think you suffer from prosopagnosia?

I do.

I once watched Up in the Air and had to ask at the end which one was George Clooney. (In my defense, I had previously seen him in Syriana, where he had a beard. Hair and facial hair are the crutches I tend to use to recognize people.) Needless to say, on the Famous Faces test I had trouble with anyone less memorable than, say, Barack Obama.

Wow. I scored 34% on the second one, i.e. no better than random guessing. The last part that added the random noise to the faces didn't make a difference, since I already couldn't do worse at the task.

"Famouse Faces" at https://www.testmybrain.org and http://facememory.psy.uwa.edu.au/ are both good.

It's also being kickstarted as a standalone card game: https://www.kickstarter.com/projects/1559002049/earworm-beco...

> Gently rolling a stop sign at a high-visibility intersection sounds like a safe and principled violation.

If you do this yourself, please reconsider. My experience is that drivers who do this (especially at 2-way stops) are watching carefully for perpendicular traffic while blithely ignoring pedestrians approaching the crosswalk that they are rolling through. As a pedestrian, I consider this the second highest threat to my personal life+limb, after left turners who (again) watch for cars and not pedestrians.

There's a BigInt proposal at stage 2, which might meet some of your needs: https://github.com/tc39/proposal-bigint

One thing to note is that the new version (v4) of the Sheets API can access the same fancy functionality that Apps Script can. So if gspread moves to that (which e.g. https://github.com/burnash/gspread/issues/435 alludes to), some of those limitations will go away.

(And the sync thing is neat!)