• 1 Post
  • 720 Comments
Joined 2 years ago
cake
Cake day: July 14th, 2023

help-circle




  • I don’t think blahaj would object to the basic message.

    There are the occasional man-hating users, sure. But for the most part, the instance seems to accept the idea that men suffer under patriarchy as well.

    Now, when you bring it up in response to women, enbies, etc. suffering under patriarchy… that’s not so great.

    So I guess it depends on what community it would be posted to, and how it would be posted.

    Given how OP seems to be spamming this in multiple unrelated communities… I can’t imagine they would post it to blahaj tactfully. So… maybe you’re right, lol.










  • kibiz0r@midwest.socialtoTechnology@lemmy.worldThe Copilot Delusion
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    2
    ·
    16 days ago

    So if library users stop communicating with each other and with the library authors, how are library authors gonna know what to do next? Unless you want them to talk to AIs instead of people, too.

    At some point, when we’ve disconnected every human from each other, will we wonder why? Or will we be content with the answer “efficiency”?


  • The process is supposed to be sustainable. That doesn’t mean you can take one activity and do it to the exclusion of all others and have that be sustainable.

    Edit:

    Also, regretably, I’m using the now-common framing where “agile” === Scrum.

    If we wanna get pure about it, the manifesto doesn’t say anything about sprints. (And also, you don’t do agile… you do a process which is agile. It’s a set of criteria to measure a process against, not a process itself.)

    And reasonable people can definitely assert that Scrum does not meet all the criteria in the agile manifesto — at least, as Scrum is usually practiced.


  • It’s funny (or depressing), because the original concept of agile is very well aligned with an open source/inner source philosophy.

    The whole premise of a sprint is supposed to be that you move quickly and with purpose for a short period of time, and then you stop and refactor and work on your tools or whatever other “non value-add” stuff tends to be neglected by conventional deliverable-focused processes.

    The term “sprint” is supposed to make it clear that it’s not a sustainable 100%-of-the-time every-single-day pace. It’s one mode of many.

    Buuuut that’s not how it turned out, is it?