Policies about vibecoding and IA in software development

FYI your last message here about that gave me a lot of food for thought, and I’m working hard to develop an approach that’s as nuanced as possible, while also practical to implement in a policy for fediverse.party. Here’s where my thinking is at currently. Feedback welcome! Here or there (ideally there, so the deliberations on it are all discoverable in one place).

EDIT: Also …

Everything I said about Mirlo and CodeBerg applies just as much to SongHive, BandWagon, Emissary, Atlas, etc. :blush:

I’ll read your post thoroughly, when I get a chance. Yes, there’s a lot to think about, and good people will probably change their opinions on this stuff a dozen times as the tech (and our uses of it) evolve.

Your comment about nuance is important. Too often, people only see issues like this as black vs. white, us vs. them, and we all lose when we let that sentiment win.

I think we NEED to find (and use) the good parts of this tech or else the bad guys certainly will win.

1 Like