Can we stop posting this headline? Again and again and again?
It’s not news.
If a sizable portion of the population did want to do something stupid, that’d be news.
This is… It’s not even propaganda. It’s just a waste of our limited time and emotional capacity for idiocy.
He needs to put his money where his mouth is, and subsidize healthy food and move to single payer insurance so that healthcare can be affordable, if he’s going to spout off like that.
This ai bot bolds the oddest things 🤔
Meh, Irish Whiskey and Scotch are still available. The loss will be forgotten over a single glass.
That reads like the sort of thing Wolfram Alpha was designed to absolutely obliterate, if only the raw data representing each of those keywords had been loaded in.
I introduced a “small one story structure, its walls no wider than the span of a single door” next to the farmhouse my players were investigating. They didn’t believe the owners who told them what it was for, and went to check it out for themselves, hackles up and weapons drawn.
It’s an outhouse.
Just an outhouse.
RE Battlemaps: strongly opposed to allowing them. Lemmy.world already has a battlemaps community. Ttrpg.network is welcome to make such a community too, I suppose. That content works for many more ttrpgs than dnd, so putting it in its own space makes more sense than allowing it in here.
RE artwork, if someone wants to post a hand-drawn scene of their group’s epic win/loss against the bbeg, that’s cool. I think we like seeing dnd success stories from folks, and a picture can be worth a thousand words. But, if that person is open for commissions, I would strongly prefer not to know about it.
IMO advertising needs to be segregated to opt-in communities kept exclusively for that purpose, much like LFG posts get their own space to mot pollute the general discussion.
(Similarly, links out to other sites that have comment sections, like youtube, should IMO be required to have actual supporting text content worthy of discussion, as without it they are just more advertising. That’s outside the scope of the original discussion tho.)
Edit: RE homebrew–IMO it too should be sequestered, as it represents a divergence from everyone else’s frame of reference.
Preface: I have a lot of AI skepticism.
My company is using Cursor and Windsurf, focusing on agent mode (and whatever Windsurf’s equivalent is). It hallucinates real hard with any open ended task, but when you have ALL of:
Then you can tell the agent to write test cases before writing code, and run all relevant tests when making any code changes. What it produces is often fine, but rarely great. If you get clever with setting up rules (that tell it to do all of the above), you can sometimes just drop in a product requirement and have it implement, making only minor recommendations. It’s as if you are pair programming with an idiot savant, emphasis on idiot.
But whose app is well covered with tests? (Admittedly, AI can help speed up the boilerplating necessary to backfill test cases, so long as someone knows how the app is supposed to work). Whose app is well-modularized such that it’s easy to select only downstream affected tests for any given code change? (If you know what the modules should be, AI can help… But it’s pretty bad at figuring that out itself). And who writes well thought out product use cases nowadays?
If we were still in the olde waterfall era, with requirements written by business analysts, then maybe this could unlock the fabled 100x gains per developer. Or 10x gains. Or 1.1x gains, most likely.
But nowadays it’s more common for AI to write the use cases, hallucinate edge cases that aren’t real, and when coupled with the above, patchwork together an app that no one fully understands, and that only sometimes works.
Edit: if all of that sounds like TDD, which on its own gives devs a speed boost when they actually use it consistently, and you wonder if CEOs will claim that the boosts are attributable to AI when their devs finally start to TDD like they have been told to for decades now, well, I wonder the same thing.