Yeah, Santa Claus, the Easter Bunny, and the Tooth Fairy were all a sort of mini rite-of-passage when I was a kid, with everyone figuring it out at different times. Made us feel a little more grown up, especially among other kids who hadn't figured it out yet. And for some reason I don't remember us spoiling it for them - instead we were in on the secret to make the holiday more fun.

If we're still talking postgres, it doesn't update in-place. Update is implemented as delete+insert (where delete is updating metadata so the row is still around for still-running transactions but invisible to future transactions).

I ran a small experiment on co-workers around a decade ago and learned that often enough they don't read code, more like they decipher it. Which all of a sudden the obsession with code linters and formatters suddenly made sense (though I still don't like them). And being unable to read code, I have to guess writing it was difficult too.

Afterwards one of them said it never even crossed his mind it was possible to read code like that.

Neither. In Amrican English we're fully pronouncing the "r" when we say "er" instead of "um".

> Obviously people can hear the difference between vocalizing with your mouth open and vocalizing with your mouth closed.

That would be "uh" vs "um", not "er".

That part is kind of their point - it doesn't have the distribution issues your other examples have.

For whatever reason this persists to touchpads even though they would seem closer to a touchscreen.

Looking at the individual changes in isolation, it's harder to see it doesn't match other conventions, duplicates code, removes or disables paths without cleaning up, etc. I'll bet there's also some crazy spaghetti code in there, from helping a co-worker clean up their Ai-generated code that they didn't understand.

The word for this is "infatuation", and it is well-studied.

The other one appears to be https://www.goodreads.com/book/show/15744759-three-worlds-co... (summary and review at https://www.reddit.com/r/CharacterRant/comments/up854p/three... )

The one they're pointing out (the short punchy sentences) also apply to things like politicians and news articles. Blog posts are a bit odd.

* And here I mean those literal exact words. People are also extrapolating to similar patterns that use different or more words than "it's not" and "it's", but those flow better and aren't what I'm referring to here.

I think they're right that kids (at least in the US) are generally treated as less capable than they are, and it ends up slightly delaying their development.

We did Bugzilla -> FogBugz -> Jira. Almost all the data was lost every time, no one bothered with migration except for the maintenance project. Worse, even on Jira we lose cases as teams end and hand off the code, and the Jira project is closed so no one else can access it.

We've also done cvs -> svn -> git. All the commits have survived migration.

I do keep including cases in the commits messages, if nothing else it'll help link things together in the future, but never rely on them for context a future maintainer might need.