• 0 Posts
  • 65 Comments
Joined 3 years ago
cake
Cake day: October 18th, 2023

help-circle

  • Not for me (usually), because I know it’s a very complex game and that anyone who is more than passingly familiar with it is going to be better than me. My frustration level when I lose is directly proportional to the number of dumb mistakes I made. If I did well for my skill level and the other person just played better, then it becomes a learning opportunity rather a source of frustration.

    This applies to other games as well. The only exception is when it’s a game where luck plays a big role and it just isn’t going my way that day. Then I’m not winning or learning, which can also be super frustrating.




  • …just because ethics.

    Not ethics, practicality. There are only so many people contributing so many hours to open source projects. It’s impossible to handle the entire incoming stream of reports without some filtering.

    And your analogy isn’t really capturing the problem. If you want to stick with the (slightly hyperbolic) nuke analogy, it’s more like getting 9 reports that nukes are going to be launched but 6 of them name different source countries, 4 of them say it’ll actually be tomorrow night, 2 of them say the nukes will be unarmed for some reason, and one says it’s actually bottle rockets being launched. I hope you can find them in time because they’re buried among 362 other intelligence reports about god knows what, many of which are duplicates of things you already knew about. Also, you don’t know any of the sources or what their motives and competency levels are.

    @OwOarchist@pawb.social didn’t say anything about banning AI usage at all, just that we need a better system to restrict contributions to people who can demonstrate that they can filter the noise out of their own contributions instead of just spamming mailing lists with everything their chosen tool spits out. No one is going to dump a valid bug report just because a contributor used AI to find it. They want to dump the endless stream of duplicate and invalid reports being submitted by people that don’t bother confirming that the reports they’re submitting are new and valid.


  • They don’t even have to be intentionally built in. Anything that generates unnecessary work for FOSS volunteers is a win for proprietary software companies.

    Even an easy to use and well-built tool that produces good results would result in mailing list and bug report noise simply because people like to contribute. If we set aside those who are just trying to pad their resume with open source contributions and bad actors trying disrupt FOSS projects, we’re still left with a lot of well-intentioned, mostly inexperienced devs generating duplicate and/or invalid reports and requests.

    Since the current state of AI tools certainly does not produce consistently good results, I don’t think organizations that are hostile to FOSS projects actually need to do anything at all for them to be disruptive. Just make their shitty tools accessible and other people will significantly contribute to maintainer burnout without even intending to.


  • I’m not convinced they actually exist. Even the very conservative implanted medical device company I recently left, for reasons unrelated to AI, is adopting it.

    But they’re doing it right. Generative AI is only used for internal tools and automation. The software that runs on clinical devices is still written using a rigorous manual process where every module, function, and operation is planned out, reviewed, and documented before any of the code is written.

    The only clinical use of AI is in data analysis because (non-generative) AI can be really good at finding patterns in massive piles of data. Those results are then presented to physicians, along with the raw data, for review.

    But the AI bros don’t understand the ideas of “appropriate context” and “safe adoption.” Since “move fast and break things” attracts startup capital, it must be the right approach for everyone everywhere in everything, right?



  • That damn search bar was the only reason I ever started looking at launchers. I used LG and Samsung phones for years and wanted a more streamlined interface closer to stock android, so I got a pixel.

    And the very first time I turned it on, I was incredibly disappointed to see this giant Google logo nailed to the bottom of the screen, existing only to provide functionality that I don’t want.

    So into the launcher rabbit hole I dove.


  • I wonder if anything will be done.

    If they get a cut of the booking cost, then they have no incentive to dissuade listing creators from doing whatever the fuck they can to get renters to pull out the credit card.

    They already have your money by the time you arrive at your rental and realize the listing was complete horseshit. Most people either can’t or won’t change their planned accomodations that late in their trip.

    So you stay in your falsely advertised hovel and complain to the booking company afterward, who says, “we don’t create the listings, inaccuracies in them aren’t our fault.”

    Nothing will change until the problem is pervasive enough that bookings drop as a result AND the reduced revenue is correctly attributed to it by shareholders AND they pressure the C-suite to implement policy changes accordingly.







  • If you don’t even know what encryption is, that passwords need hashing and what not, then you should really question what you’re doing

    I agree with your point, but I would phrase it more generally: when we’re assigned a task in a problem space we are unfamiliar with, we should always take some time to research that space before designing our solution.

    After all, if we don’t know what encryption or password hashing are, how could we know that we need to learn about them first? But spending just a couple hours one morning reading about password and authentication management would have given the developer a good sense of best practices.

    So she either, A) didn’t think to familiarize herself with a new topic prior to working on it, or B) did read about it and ignored general industry guidance. Both of those options are more problematic to me than simply not knowing specific things. Those are process problems that need to be addressed to build her skills as a developer.

    But ultimately, in my opinion, this is really all the fault of the cheapass director who didn’t want to pay any experienced professionals to handle the task.