ETL to QE, Update 39, My Two Root Problems are not good enough
Date: 2024-05-29
There is an interesting allegory that goes, A genius in a vacuum is not a genius. Or in other words, if someone discovered Einstein's theory of relativity on an island but never communicated it with the people around him in a way that would be preserved across time, they ain't so much a genius. I am pretty sure I am not a genius but this wiki I got here and the coding projects I work on definitely operate within a vacuum.
Every couple months I come back to the problem, What makes a scalable meme? yet I never really sit down and define what a Scalable Meme is.
I have my DDaemon - Two Root Problems which are as follows,
I am interested in two problems.
- How does one put all data they have personally generated into an single accessible API with RBAC(Rule Based Access Control).
- Once all one's data is all easily queryable what do you do with it?
- Ask yourself, what is Data For?
I currently use these two problems to orient and inspire myself to get work done. But if this DDaemon thing is ever going to be a protocol people use then I need to move beyond these Two Root Problems and come up with something more human story centric that people will remember, for example,
The other week I attended a data science meetup in person at a pub. As you would expect the topic of social media algorithms showed up. I made a comment about how TikTok and other platform's social media algorithms are this thing called "Algotainment"(Algorithmic Entertainment). Later in the night I noticed someone else in a separate conversation use the word Algotainment in conversation, and it took me a moment to realize they they learned it from me. Algotainment is not quite a scalable meme, but it is definitely a meme that can spread.
The concept of Google is definitely a scalable meme. The name of the company literally describes the act of searching for stuff on the internet. Many other companies have been turned into verbs including, Photoshop, Uber, Venmo, and Zoom. These phrases are now imbued into the English language.
There are similar companies that had taken over the English Lexicon that fell out of fashion including Blackberry, Kodak, Napster, and TiVo with each of them not exactly being replaced with a colloquial term.
What I really want to do is produce something like bittorrent for social media managed via modular knowledge graph using RBAC(Rule Based Access Control). Then create a medium for an emergent game like The Glass Bead Game as mentioned in Infinite Games for Infinite Teams for people to play for eternity.
Something like Google and Crackberry are relatively well defined concepts that have a easy to understand user journey backed in that the every day user can describe and understand intuitively. This ddaemon idea has its user journeys in Epic User Journeys but we still lack the capacity to follow them through via a data flow, user journey, or user experience design flow all we got is a bunch of half baked ideas.
One of these ideas Question Engine has been baking for a very long time, over a year in fact. Yet there is still no website my friends can go to to post whatever questions they have on the top of their head and control access to them via RBAC. The spec CGFS - Lite Paper should be pretty simple to finish and implement, it seems our greatest blocker is something psychological.