Post

I wanna hear the untold stories of the huge architectural and data migrations that go into the “smallest” changes like when Slack added the ability to add someone to a group DM and *move past messages* to the new conversation or how Amazon no longer asks which Kindle to send your library book to

you gotta assume that these were both enormous efforts that were probably years in the making. all to make it work the way it should’ve worked in the first place

twitch has “shared chats”??

wouldn’t be surprised if shopify had to rewrite huge chunks of the editor to enable copy paste x.com/r3ckoningid/...

I vaguely recall something from Notion about the challenges of some text editing operations when the document is modelled as editable blocks rather than a single continuous editor

well so here at Notion Labs Inc., we have the concept of a "block"

i have heard stories of a large mysql cluster, and a system wherein "the schema that we used is the schema for your account" pretty much forever the vast majority of the data is write once read maybe and so backfilling is a huge waste of resources, so it all gets adapted per storage unit

the thing is, once you hit a certain scale, your logical and physical schema inevitably diverge, and the notion that your data exists in one consistent layout just stops being true and truthfully speaking, data migrations aren't really an issue once that happens, the problem is doing it all at once