home.social

Search

1000 results for “fgraf”

  1. @fgraf

    Yes, indeed. @Johns_priv also brought this up, to which I replied here:

    social.coop/@smallcircles/1165

    What the discussions to the poll shows is that there is so much nuance, and numerous communication use cases and edge cases.

    And in the call to "join the fediverse" and plug in to the wire there is high risk that this nuance is not properly addressed, or is even unaddressible by the general approach that is followed. It is not "been there, done that, copy mastodon, bolt on feature". That organic chaotic growth does not have a naturally healthy outcome. It can grow the blob too.

    That is more or less the key point of my blog post on Grassroots fediverse evolution: that there is a sweet spot to be found between spontaneous grassroots emergence and orchestrated top-down standardization and guidance.

    coding.social/blog/grassroots-

    #SX has a focus on the prosocial design patterns that underly all the various online communication modes, and these can be defined in a tech-independent manner.

    #sx
  2. @fgraf

    Yes, indeed. @Johns_priv also brought this up, to which I replied here:

    social.coop/@smallcircles/1165

    What the discussions to the poll shows is that there is so much nuance, and numerous communication use cases and edge cases.

    And in the call to "join the fediverse" and plug in to the wire there is high risk that this nuance is not properly addressed, or is even unaddressible by the general approach that is followed. It is not "been there, done that, copy mastodon, bolt on feature". That organic chaotic growth does not have a naturally healthy outcome. It can grow the blob too.

    That is more or less the key point of my blog post on Grassroots fediverse evolution: that there is a sweet spot to be found between spontaneous grassroots emergence and orchestrated top-down standardization and guidance.

    coding.social/blog/grassroots-

    #SX has a focus on the prosocial design patterns that underly all the various online communication modes, and these can be defined in a tech-independent manner.

    #sx
  3. @fgraf

    Yes, indeed. @Johns_priv also brought this up, to which I replied here:

    social.coop/@smallcircles/1165

    What the discussions to the poll shows is that there is so much nuance, and numerous communication use cases and edge cases.

    And in the call to "join the fediverse" and plug in to the wire there is high risk that this nuance is not properly addressed, or is even unaddressible by the general approach that is followed. It is not "been there, done that, copy mastodon, bolt on feature". That organic chaotic growth does not have a naturally healthy outcome. It can grow the blob too.

    That is more or less the key point of my blog post on Grassroots fediverse evolution: that there is a sweet spot to be found between spontaneous grassroots emergence and orchestrated top-down standardization and guidance.

    coding.social/blog/grassroots-

    #SX has a focus on the prosocial design patterns that underly all the various online communication modes, and these can be defined in a tech-independent manner.

    #sx
  4. @fgraf

    Yes, indeed. @Johns_priv also brought this up, to which I replied here:

    social.coop/@smallcircles/1165

    What the discussions to the poll shows is that there is so much nuance, and numerous communication use cases and edge cases.

    And in the call to "join the fediverse" and plug in to the wire there is high risk that this nuance is not properly addressed, or is even unaddressible by the general approach that is followed. It is not "been there, done that, copy mastodon, bolt on feature". That organic chaotic growth does not have a naturally healthy outcome. It can grow the blob too.

    That is more or less the key point of my blog post on Grassroots fediverse evolution: that there is a sweet spot to be found between spontaneous grassroots emergence and orchestrated top-down standardization and guidance.

    coding.social/blog/grassroots-

    #SX has a focus on the prosocial design patterns that underly all the various online communication modes, and these can be defined in a tech-independent manner.

    #sx
  5. @fgraf

    Yes, indeed. @Johns_priv also brought this up, to which I replied here:

    social.coop/@smallcircles/1165

    What the discussions to the poll shows is that there is so much nuance, and numerous communication use cases and edge cases.

    And in the call to "join the fediverse" and plug in to the wire there is high risk that this nuance is not properly addressed, or is even unaddressible by the general approach that is followed. It is not "been there, done that, copy mastodon, bolt on feature". That organic chaotic growth does not have a naturally healthy outcome. It can grow the blob too.

    That is more or less the key point of my blog post on Grassroots fediverse evolution: that there is a sweet spot to be found between spontaneous grassroots emergence and orchestrated top-down standardization and guidance.

    coding.social/blog/grassroots-

    #SX has a focus on the prosocial design patterns that underly all the various online communication modes, and these can be defined in a tech-independent manner.

    #sx
  6. @fgraf maybe just ignore everything scam factory that is #a16z says about anything

  7. ☀ Unser zweites Terrassengespräch dieses Jahr steht an: meetup.com/hse-cluster-events/

    In zwei Wochen reden wir über schwieriges #Kulturerbe und wie es sinnvoll in der Schule vermittelt und diskutiert werden kann.

    📅 24.5., 18.00 Uhr

    🧭 in der Voßstraße 2 in Heidelberg

    👥 mit @[email protected], @[email protected] und Michelle König vom Auguste-Pattberg-Gymnasium Mosbach.

    ➡ Alle sind herzlich eingeladen!

    #Postkolonialismus #Holocaust #Shoah #DarkHeritage #Lehrerbildung #AußerschulischeLernorte #FediLZ #Heidelberg

  8. What we learned using AI agents to refactor a monolith | 1Password

    1password.com/blog/what-we-lea

    > 1Password used AI agents to help refactor a massive codebase. The project taught us several lessons about where agents are useful and where they fall short at each stage of the process.

  9. What we learned using AI agents to refactor a monolith | 1Password

    1password.com/blog/what-we-lea

    > 1Password used AI agents to help refactor a massive codebase. The project taught us several lessons about where agents are useful and where they fall short at each stage of the process.

    #ai #genai #refactoring #softwareengineering

  10. Missed a webinar recently. Luckily there was a recording. But instead of watching it alone we did a "group -watch".

    A colleague and me made up a teams session, one shared the screen and sound and we watched the webinar together.

    Whenever one of us had something to comment or ask, we paused, discussed - and resumed. This felt so much better than watching it alone.

  11. Missed a webinar recently. Luckily there was a recording. But instead of watching it alone we did a "group -watch".

    A colleague and me made up a teams session, one shared the screen and sound and we watched the webinar together.

    Whenever one of us had something to comment or ask, we paused, discussed - and resumed. This felt so much better than watching it alone.

    #teamwork

  12. - We implement the features Step by Step
    - Why not all at once?
    - Becasue we want to check what's along the way and react accordingly
    - But still, we could do all the features at once?

    *sigh

    #agile

  13. "we have coding agents, now everyone will code his/her own software"

    And then I look at a repo:
    Years of bug fixes, security, updates, migrations, , support maybe ...

    Yes for sure, that's what everyone wants to do NOT!

    #agenticCoding

  14. Hmm, muss ich glatt mal ausprobieren. Scheint mir nicht ganz verkehrt zu sein um die codebase kennen zu lernen.

    > Der Coding Tutor
    > Oder: Wie ich aufhörte, meiner KI beim Programmieren zuzuschauen

    > "Selbst schreiben heißt selbst stolpern. Das ist wichtig für das Verständnis."

    blog.mayflower.de/27532-coding

    #claude #softwareengineering

  15. I like .. a webinar for digital #Sovereignty on LinkedIn. But well. Maybe it's good. Let's see if I tune in ... or should I tune in and ask if they also want to have it on the fediverse? 🤔

    > Building Digital Sovereignty: Strategy, AI & Real Control

    "How much control do European companies actually have over their AI — and their data? 🌐

    This question has driven our roadshow across European cities. And the answers we've heard are uncomfortable. Vendor dependencies run deeper than most organizations realize. AI adoption is accelerating. Sovereignty is not keeping pace.

    On June 17, we're bringing the conversation online: "Building Digital Sovereignty: Strategy, AI & Real Control." AI accountability, sovereign infrastructure, and why the window to act is narrowing.
    "

    linkedin.com/events/buildingdi

  16. Kennt das jemand, war da schonmal jemand? rentiert sich das? Hab davon noch nie gehört bisher aber scheint ja schon bisschen größer zu sein. Nur programm ist (noch?) keins online.

    TechDays Munich
    techdaysmunich.net

    #techdaysMunich #münchen

  17. Am Montag war ich auf dem Event "KI in der Softwareentwicklung: Grenzen, Tools und die Zukunft der Junior-Rollen – Lasst uns austauschen!" der LMU Alumni Informatik.

    Ich hab' ja selten den Austausch mit Studierenden. Insofern war es schon auch sehr spannend, deren aktuellen Erwartungen und Bedenken zu hören.

    Aber eben auch die Sichtweise von einigen Alumnis aus verschiedenen Branchen. Man verinkt ja schnell im eigenen Sumpf. Sowas sollte es echt öfters geben.

    alumni.ifi.lmu.de/alumnitalk-k

    #alumni #lmu_Muenchen #LmuAlumniInformatik #LMU #informatik #ki

  18. Am Montag war ich auf dem Event "KI in der Softwareentwicklung: Grenzen, Tools und die Zukunft der Junior-Rollen – Lasst uns austauschen!" der LMU Alumni Informatik.

    Ich hab' ja selten den Austausch mit Studierenden. Insofern war es schon auch sehr spannend, deren aktuellen Erwartungen und Bedenken zu hören.

    Aber eben auch die Sichtweise von einigen Alumnis aus verschiedenen Branchen. Man verinkt ja schnell im eigenen Sumpf. Sowas sollte es echt öfters geben.

    alumni.ifi.lmu.de/alumnitalk-k

    #alumni #lmu_Muenchen #LmuAlumniInformatik #LMU #informatik #ki

  19. Am Montag war ich auf dem Event "KI in der Softwareentwicklung: Grenzen, Tools und die Zukunft der Junior-Rollen – Lasst uns austauschen!" der LMU Alumni Informatik.

    Ich hab' ja selten den Austausch mit Studierenden. Insofern war es schon auch sehr spannend, deren aktuellen Erwartungen und Bedenken zu hören.

    Aber eben auch die Sichtweise von einigen Alumnis aus verschiedenen Branchen. Man verinkt ja schnell im eigenen Sumpf. Sowas sollte es echt öfters geben.

    alumni.ifi.lmu.de/alumnitalk-k

    #alumni #lmu_Muenchen #LmuAlumniInformatik #LMU #informatik #ki

  20. Really nothing beats eat-your-own-dogfood.

    I createda simple webtool for the local alpine club and bulk-added initial data ... That immediately gave me some ideas for #usability improvements now.

  21. Really nothing beats eat-your-own-dogfood.

    I createda simple webtool for the local alpine club and bulk-added initial data ... That immediately gave me some ideas for #usability improvements now.

  22. Really nothing beats eat-your-own-dogfood.

    I createda simple webtool for the local alpine club and bulk-added initial data ... That immediately gave me some ideas for improvements now.

  23. Really nothing beats eat-your-own-dogfood.

    I createda simple webtool for the local alpine club and bulk-added initial data ... That immediately gave me some ideas for #usability improvements now.

  24. Those #excel files are a pain for every #automation. Especially if ppl start building logic into it, any automation approach is feature creeping..

  25. Those files are a pain for every . Especially if ppl start building logic into it, any automation approach is feature creeping..

  26. Those #excel files are a pain for every #automation. Especially if ppl start building logic into it, any automation approach is feature creeping..

  27. Echt schade, dass #mistral und #mistralvibe so unpräsent sind... Ich bin doch immer wieder überrascht

  28. Schöner #Podcast über Tracking im Web vom @bsi

    "Vom Like zum Leak - wie soziale Medien Daten weiterverkaufen"

    pca.st/episode/ac5c3e85-a1c3-4

    #adtech #tracking