home.social

#paradoxofemergence — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #paradoxofemergence, aggregated by home.social.

  1. @johannab

    > One of my biggest lightbulb moments in systems theory class was realizing that even humans who may never directly interact within the scope of your design are very much still stakeholders

    Exactly, very true. It is funny.. a couple years ago and inspired by @aral tooting about it, I started practicing avoidance of the word "user".

    This now comes very natural to me, to the extent that so many uses of the word really poke me in the eye with how artificial, unnatural, distancing, and yes.. even inhumane they are.

    #CodingIsSocial #people! We "social code the social code" of #society.

    "User" is a #tech word, same as "Reverse proxy" or "Factory class". And its a leaky #abstraction that serves to lose all #nuance, and is best avoided. Furthermore it implies an #ownership relationship between devs and their captivated audience, that doesn't, shouldn't exist.

    I'm behind schedule on a #ParadoxOfEmergence blogpost, may address this.. discuss.coding.social/t/sx-sus

    Ditch use of #user! ✊

  2. @johannab

    > One of my biggest lightbulb moments in systems theory class was realizing that even humans who may never directly interact within the scope of your design are very much still stakeholders

    Exactly, very true. It is funny.. a couple years ago and inspired by @aral tooting about it, I started practicing avoidance of the word "user".

    This now comes very natural to me, to the extent that so many uses of the word really poke me in the eye with how artificial, unnatural, distancing, and yes.. even inhumane they are.

    #CodingIsSocial #people! We "social code the social code" of #society.

    "User" is a #tech word, same as "Reverse proxy" or "Factory class". And its a leaky #abstraction that serves to lose all #nuance, and is best avoided. Furthermore it implies an #ownership relationship between devs and their captivated audience, that doesn't, shouldn't exist.

    I'm behind schedule on a #ParadoxOfEmergence blogpost, may address this.. discuss.coding.social/t/sx-sus

    Ditch use of #user! ✊

  3. @johannab

    > One of my biggest lightbulb moments in systems theory class was realizing that even humans who may never directly interact within the scope of your design are very much still stakeholders

    Exactly, very true. It is funny.. a couple years ago and inspired by @aral tooting about it, I started practicing avoidance of the word "user".

    This now comes very natural to me, to the extent that so many uses of the word really poke me in the eye with how artificial, unnatural, distancing, and yes.. even inhumane they are.

    #CodingIsSocial #people! We "social code the social code" of #society.

    "User" is a #tech word, same as "Reverse proxy" or "Factory class". And its a leaky #abstraction that serves to lose all #nuance, and is best avoided. Furthermore it implies an #ownership relationship between devs and their captivated audience, that doesn't, shouldn't exist.

    I'm behind schedule on a #ParadoxOfEmergence blogpost, may address this.. discuss.coding.social/t/sx-sus

    Ditch use of #user! ✊

  4. @johannab

    > One of my biggest lightbulb moments in systems theory class was realizing that even humans who may never directly interact within the scope of your design are very much still stakeholders

    Exactly, very true. It is funny.. a couple years ago and inspired by @aral tooting about it, I started practicing avoidance of the word "user".

    This now comes very natural to me, to the extent that so many uses of the word really poke me in the eye with how artificial, unnatural, distancing, and yes.. even inhumane they are.

    #CodingIsSocial #people! We "social code the social code" of #society.

    "User" is a #tech word, same as "Reverse proxy" or "Factory class". And its a leaky #abstraction that serves to lose all #nuance, and is best avoided. Furthermore it implies an #ownership relationship between devs and their captivated audience, that doesn't, shouldn't exist.

    I'm behind schedule on a #ParadoxOfEmergence blogpost, may address this.. discuss.coding.social/t/sx-sus

    Ditch use of #user! ✊

  5. @johannab

    > One of my biggest lightbulb moments in systems theory class was realizing that even humans who may never directly interact within the scope of your design are very much still stakeholders

    Exactly, very true. It is funny.. a couple years ago and inspired by @aral tooting about it, I started practicing avoidance of the word "user".

    This now comes very natural to me, to the extent that so many uses of the word really poke me in the eye with how artificial, unnatural, distancing, and yes.. even inhumane they are.

    #CodingIsSocial #people! We "social code the social code" of #society.

    "User" is a #tech word, same as "Reverse proxy" or "Factory class". And its a leaky #abstraction that serves to lose all #nuance, and is best avoided. Furthermore it implies an #ownership relationship between devs and their captivated audience, that doesn't, shouldn't exist.

    I'm behind schedule on a #ParadoxOfEmergence blogpost, may address this.. discuss.coding.social/t/sx-sus

    Ditch use of #user! ✊

  6. > I do believe we should state how we want people to use what we write and build structures that nurture the society we want to live in

    @travisfw I do agree, esp. on the last bit. As "we should state how we want" is a) yes, a good thing to do, but b) falls flat afterwards in chaotic "herding of cats" #grassroots environments, esp. at scale where the true "nurturing online society" takes shape. This happens by #emergence, which is my focus area with Social experience design. Truly fascinating stuff.

    PS. I'm curious which toot of mine inspired your reply, as its unattached. I hope to blog soon on #ParadoxOfEmergence and have created forum thread already: discuss.coding.social/t/sx-sus

    > I've been using the Peer Production License myself

    @lykso interesting, TIL didn't know about it. You may peek at #HedonicPeerProduction if you hadn't before: coding.social/blog/reimagine-s

    > Is this ☝️ the gist?

    Sort of. You may say that #SX is a holistic approach to foster a fair 'fitness formula' in a #commons.

  7. > I do believe we should state how we want people to use what we write and build structures that nurture the society we want to live in

    @travisfw I do agree, esp. on the last bit. As "we should state how we want" is a) yes, a good thing to do, but b) falls flat afterwards in chaotic "herding of cats" #grassroots environments, esp. at scale where the true "nurturing online society" takes shape. This happens by #emergence, which is my focus area with Social experience design. Truly fascinating stuff.

    PS. I'm curious which toot of mine inspired your reply, as its unattached. I hope to blog soon on #ParadoxOfEmergence and have created forum thread already: discuss.coding.social/t/sx-sus

    > I've been using the Peer Production License myself

    @lykso interesting, TIL didn't know about it. You may peek at #HedonicPeerProduction if you hadn't before: coding.social/blog/reimagine-s

    > Is this ☝️ the gist?

    Sort of. You may say that #SX is a holistic approach to foster a fair 'fitness formula' in a #commons.

  8. > I do believe we should state how we want people to use what we write and build structures that nurture the society we want to live in

    @travisfw I do agree, esp. on the last bit. As "we should state how we want" is a) yes, a good thing to do, but b) falls flat afterwards in chaotic "herding of cats" #grassroots environments, esp. at scale where the true "nurturing online society" takes shape. This happens by #emergence, which is my focus area with Social experience design. Truly fascinating stuff.

    PS. I'm curious which toot of mine inspired your reply, as its unattached. I hope to blog soon on #ParadoxOfEmergence and have created forum thread already: discuss.coding.social/t/sx-sus

    > I've been using the Peer Production License myself

    @lykso interesting, TIL didn't know about it. You may peek at #HedonicPeerProduction if you hadn't before: coding.social/blog/reimagine-s

    > Is this ☝️ the gist?

    Sort of. You may say that #SX is a holistic approach to foster a fair 'fitness formula' in a #commons.

  9. > I do believe we should state how we want people to use what we write and build structures that nurture the society we want to live in

    @travisfw I do agree, esp. on the last bit. As "we should state how we want" is a) yes, a good thing to do, but b) falls flat afterwards in chaotic "herding of cats" #grassroots environments, esp. at scale where the true "nurturing online society" takes shape. This happens by #emergence, which is my focus area with Social experience design. Truly fascinating stuff.

    PS. I'm curious which toot of mine inspired your reply, as its unattached. I hope to blog soon on #ParadoxOfEmergence and have created forum thread already: discuss.coding.social/t/sx-sus

    > I've been using the Peer Production License myself

    @lykso interesting, TIL didn't know about it. You may peek at #HedonicPeerProduction if you hadn't before: coding.social/blog/reimagine-s

    > Is this ☝️ the gist?

    Sort of. You may say that #SX is a holistic approach to foster a fair 'fitness formula' in a #commons.

  10. > I do believe we should state how we want people to use what we write and build structures that nurture the society we want to live in

    @travisfw I do agree, esp. on the last bit. As "we should state how we want" is a) yes, a good thing to do, but b) falls flat afterwards in chaotic "herding of cats" #grassroots environments, esp. at scale where the true "nurturing online society" takes shape. This happens by #emergence, which is my focus area with Social experience design. Truly fascinating stuff.

    PS. I'm curious which toot of mine inspired your reply, as its unattached. I hope to blog soon on #ParadoxOfEmergence and have created forum thread already: discuss.coding.social/t/sx-sus

    > I've been using the Peer Production License myself

    @lykso interesting, TIL didn't know about it. You may peek at #HedonicPeerProduction if you hadn't before: coding.social/blog/reimagine-s

    > Is this ☝️ the gist?

    Sort of. You may say that #SX is a holistic approach to foster a fair 'fitness formula' in a #commons.

  11. @nicol thank you! I'm really glad you liked what I wrote down.

    > it's a complexity that implies a friction to coding.

    Very complex, and mostly where sociosphere expands from technosphere into broader society where the technology must land well. Which makes these social dynamics all the more fascinating to me, as we have so little awareness how that actually works in practice.

    I intend to follow-up with a blog post that introduces the SEE model, for Sustainable ecosystem evolution.

    social.coop/@smallcircles/1164

    This model has a point on the value creation curve, which I dubbed the #ParadoxOfEmergence.

    Past this point all the Potential that had been 'arranged' thus far by Investment in the emergent design - but which remained invisible to others as it sat purely in emergent space - suddenly becomes readily apparent to anyone. Often to the extent that in hindsight the solution seems very obvious, waiting to happen.

    Especially in our grassroots commons the paradox can do its dirty work.

  12. #ParadoxOfEmergence

    The Paradox Of Emergence is the inability to explain to pragmatic people who say "Show me the money" in terms of what your solution is capable of. A good emergent design that models with emergent forces as building blocks to which it specifies simple rules, may have prepared a Golden Dragon that is ready and waiting to be unleashed. Yet it exists entirely in emergent space, it is pure potential all the way. The Dragon is lurking unseen to anyone but the designers themself, making the solution a tough sell, where investments in time and money are asked for. OTOH once the Dragon has been unleashed, then its true value becomes readily apparent to anyone. Another example is chess. Can the first inventor of the game, convey Magnus Carlson level concepts to demonstrate the power & potential of this new game, where other people only see some simple building blocks and rule set?

    #SX #SocialCoding #Emergence

  13. @strypey

    I'm working on another blog post titled "Revolutionary evolution" which relates to possible outcome of #SX design with emergent forces. Where an unexpected "Spark of ignition" is possible and a #commons is able to ignite into massive concerted action + cocreation. Such that value creation and aggregation enables "Revolution by evolution".

    However before it gets to that, a SX solution first has to pass the #ParadoxOfEmergence point, where the *true* Value for the first time becomes really apparent to people who are not deeply engrossed in the mechanics of the ethereal, intangible #EmergenceDesign if it's choreographed for #Potential for radical #change.

    PS. Emergence design means 'with emergent forces', which is different than #EmergentDesign, where the #design itself evolves gradually, through investment and #progression on the "Solution path".

    It has relationship to how we reinvent wheels, and also how well-intended contributions may lead to really bad outcomes at scale.

  14. #ThoughtProvoker 🤔

    #ParadoxOfEmergence. The Paradox of Emergence entails that the more intricate an #EmergentDesign gets, the more complex #WickedProblems it can potentially solve.

    However, all the potential power remains dormant, ethereal and invisible, especially to people other than the designer. It can only be properly perceived and valued, either with deep attention and focus on the emergent dynamics of the design. Or by dilligent practice in the field.

    A design may represent a beautiful emergent Golden Dragon of Problem Solving. Waiting in its lair under Wicked Problem mountain for when its time to breathe its Fires of Solution onto mankind. Ready to soar. Yet what most other people and even at times the designer themself perceive is merely a tiny mouse. Thus they are unwilling to add their 2 cents to a Potential they cannot grasp. Unable to see how their support adds to a sizable Dragon's Hoard that has already emerged, lending power to the dragon so it may be unleashed.

    #SX

  15. @mro @evan @julian @fedify

    P.P.S. My latest blog post about #ActivityPub fediverse contains a "Back to (potentially radical) simplicity" call-to-reflection (among other subject matters) .. social.coop/@smallcircles/1163

    Solution is.. difficult, but simple, yet not easy. 😝

    #SX #SocialCoding #ParadoxOfEmergence

  16. @woozle @Profpatsch @eryn

    Thank you! I am delighted to hear that. An *intent* in itself is already valuable. And even more so, being *intentional* in what you do. Both of these have emergent properties. So you are *already* practicing #SX by sending this toot, it constitutes your 2 cents. And hence, truly, you may call yourself Social experience designer, if that were your dream job like it is mine. 😊

    This is how weird and wonderful emergence is. At least that is my *expectation*. I am also merely practicing, ha ha :)

    #SX #Emergence #ParadoxOfEmergence

  17. #NoteToSelf ✏️

    I discovered, from my own experience in the commons in the past and by writing them down, what I now call and will elaborate for #SX: The #Paradox of #Emergence.

    #ParadoxOfEmergence. A deep insight. I should take some time to elaborate its relation to the commons and how our individual work relates to the larger whole. And why we forget about that relation if we "play our own game" autonomously and try to aggregate value to affect big change. It also relates to #ExpectationManagement again: Who are the other players?

    social.coop/@smallcircles/1163