Elektrine lite

← Feed

@Postmortal_Pop@lemmy.world

2026-10-20 14:11 UTC

To that I’d argue that you vet the people before the code. I’m taking baby steps into godot for my own dream project and, while it pains to admit, when I’m having a hard time figuring something out I use deepseek to lay out a tutorial and cite the documentation so I can fact check it. I don’t know a lot about coding, but I know not to trust a bot and I know enough to figure out what most things mean. Two of us to every skilled coder like trade apprentices, you’d still occasionally have to fix a stupid mistake when your Dingus mounts all the fixtures to the drywall, but you’re actually doing a lot less on average and you can instead focus on the really complicated things. In turn, the apprentices get to a point of working on their own and the masters don’t need to carry the load. Might even save some people from the cult of vibe coders

Replies (1)

  • @jj4211@lemmy.world 2026-10-20 14:53

    Note that if I can’t readily tell if a submission has had “AI assistance” or not, then I am not particularly interested in playing detective in the pursuit of purity. So in your case it’s likely I wouldn’t really care if it looks reasonably curated. But I can understand having a standing policy to cite when you just don’t feel like vetting what is more obviously “slop”. Though if your submission basically advertises the AI assistant in use, I’m not a fan. If it vaguely discloses, ideally with nuance, the nature of AI assistance (without promoting specific solutions), then I’d feel better. I am a bit disappointed in, for example, an issue I just received that could have just said “need to add an explicit requirement” but instead was a needlessly long writeup with a little robot emoji and “created by claude code” at the end. Just tell me the gist and it saves me time, I don’t want an AI generated dissertation on every little thing, that takes me more work than the ‘unprofessional’ blurb that folks want AI to massage.

    Open ##5280509