Morning thoughts, open ears and I wanted to briefly skip through yet stayed for most of the episode so far: "... And what local-first is, is a principle for designing this kind of collaboration software so that the primary copy of the data is not somewhere in the cloud, but on your own machine. You have a copy of the data locally on your own machine, which means that you can access it while offline, for example, and you can just keep using the software without an internet connection, and it'll just resync the next time you come back online again. ..." I haven't been listening to tech and software architecture podcasts that often recently but remembering rather well reading through the "Designing Data-Intensive Applications" book back then (which was a concise and great read, like most of the O'Reilly books used to be and maybe still are), speaker got my interest started and I remained there nodding again more often than I probably should. Talking making applications independent of particular cloud vendors. Talking making cloud services useful support tools that can be changed without being tied to them altogether. Giving users the autonomy and full control over their data, specifically also non-technical users. Spreading features absolutely familiar to software developers, such as the fully self-containing autonomy of git repositories, the change tracking and revision history, to other domains (such as social networks, talking ATProto / Bluesky again). Worth following up on.
infoq.com/podcasts/increasing-… #linkdump #podcasts #social technology #data architecture