Then what are you arguing about

Enjoy it all you want, but stop buying the content. That’s a choice you can easily make. You can’t easily make the choice to stop buying petroleum products.

Ugh, this same old tired comparison.

Most oil products have little to no practical alternatives. There are plenty of alternatives to the Harry Potter franchise. And no, the story is not good. If you think it’s good, I implore you to explore other children’s fiction, because you’re obviously missing out.

So much of agile “process” gets so close to the point while still missing it, it’s infuriating. Absolutely 100% agree that story points are mostly meaningless, but story pointing shouldn’t be the point of backlog refinement. The point should be to discuss upcoming work, clarify things, ask questions, make sure everyone’s on the same page, moving in the same direction, and making sure all the work is accounted for. Story points can be a nice punctuation to all that discussion and planning effort, but for the most part it’s nothing more than a contrivance to satisfy management’s boner for tracking useless metrics.

I want sex work to be legal and sex workers to enjoy the same standards and protections of any other worker. Forming a parasocial relationship with a fake digital entity should be way more harmful than paying for a sex worker’s services.

I… Yeah, I just said pretty much the same thing lol

Sure, that’s a very, very robust way of doing things. And I’m not trying to say what you’re describing is wrong either. I’m just saying that some places don’t have the knowledge/ability to set things up that way, so they play fast and loose with prod access. Couple that with giving LLMs free reign over the computer with those prod settings, and you end up in situations like in the original post.

It’s not unrealistic, is all I’m trying to claim. It’s a failure on several levels, but it’s not unrealistic.

Hopefully they’re not storing their production database in git lol. They should be taking backups of the database, but unless they’re making one after every transaction, permanent data loss is a real possibility.

Some places deploy to prod multiple times a day. Trying to coordinate access through a management server in situations like that can get cumbersome. It’s also easier to audit who’s doing what if they connect from their personal environment. Different strokes for different folks of course, but it’s certainly not uncommon to be able to connect to prod directly from a dev box.

Well, sure, but even if a developer correctly tests on a development environment, they still probably have prod settings laying around on their filesystem for the times where they need to put out fires in prod. That’s kinda what it looks like what happened here - the LLM found a .env file with prod settings, and used that config to run destructive tests. All the more reason to not give an LLM side wide reaching access to your computer, but it’s not necessarily an indication that someone regularly tests in prod.

Ah yes, Lulu was the greatest work of Nomura’s belt era

I promise you, you don’t know what you’re talking about, but you’re dug in because any amount of nuance threatens your stance of “Linux bad because no play popular games, grr”

So this conversation isn’t going to go anywhere. Feel free to continue, but it’s already effectively over. Nothing I say will change what you think because you’re entrenched, and nothing you say will change what I think because it won’t be based in reality or reason.

I wonder what has to happen to someone to make them deny someone’s personal experiences in order to defend kernel level anti-cheat

It’s literally because Taco Bell is one of the few fast food places that has a decent amount of fiber in most of their items, and most people’s diets are sorely lacking in fiber. So the sudden influx gives them the shits, and they blame it on the Taco Bell, instead of their poor diet.

Eat your vegetables, eat more beans, and your Taco Bell shits will be no more.

Lol k, keep making assertions about my personal experiences. Anything other than admit there might be some nuance you’re not seeing

I think I’m thinking of Battlefield 2042, the one with the huge maps and like 128v128 matches. Never said I played any of the COD franchise, those games are dog shit

LMAO I can promise you, they worked at one point, and I did play them. I know apex doesn’t work in Linux now because the devs purposely decided to break Linux/Proton compatibility, and I believe Warzone is the same way. Battlefield was a buggy mess and not very fun to me when I played it, so I didn’t really keep up with what happened there, but I wouldn’t be surprised if that was dev incompetency as well. Why blame Linux when it’s the devs of those games that are breaking compatibility, either purposely or out of incompetence?

deleted by creator

Chunked and capped

Random thought - do you use AI to author your comments/posts?