pull down to refresh
100 sats \ 1 reply \ @Scoresby OP 23h \ parent \ on: The problem with AI generated contributions to open source projects AI
I think I would describe the group differently: there is a group of people who just learned about bitcoin and want to fix it. They have not taken the time to delve into it's history very much, certainly not the history of its development (mailing list archives, github comments, etc...). They may not even be aware of the proper form a BIP should take, but they have learned that there is such a thing as a BIP and with Chat at their side they are able to produce something that superficially resembles a BIP draft submitted by an experienced Bitcoin developer who has done all the things mentioned above.
I do not believe these people care very much whether AI is a magic bullet or not, nor do they have the humility to realize that their great idea for a BIP should probably stew for a few years before they even consider submitting it.
I'm sure there are many others who are relatively new to Bitcoin or who have not been involved in Bitcoin development, yet who have excellent ideas -- but I also think that writing the BIP yourself is a manageable hurdle for such individuals.
there is a group of people who just learned about bitcoin and want to fix it. They have not taken the time to delve into it's history very much, certainly not the history of its development
That group is continuously there and has been from the beginning in Bitcoin (and is also not unique in Bitcoin.)
jgarzik has made no secret of him starting like that.I think that the most harmful symptom in the above is "want to fix". As a conservative developer that doesn't want to fix what isn't broken, especially not something as fragile as protocol or consensus, resisting this is probably the most exhausting part of the job in the long term. And most people that have a yolo mindset keep it. One way or another, you'll always find them trying to change things, cradle to grave. I often feel that change is a greater good than stability to this group of developers.
However, these aren't the same group of people as vibe coders per se. There's some overlap and cross-pollination but I think that those are distinct groups. I've dealt with people like this in FOSS since the 90s
reply