What I find really disturbing is the impossibility to catch up with the development - which agent system to use, which model, what are the right models for what tasks?
I do not fear that some agents will pollute my repos with their PR. In opposite, I suppose that we will end at a point where for each question, task, or problem, one will find many (AI-coded) solutions, making it impossible to choose a right, solid, reliable one. I recently thought about having a database of tools per task so that a comparison would be possible. But the maintenance costs of something like this are enormous when including benchmarks, comparisons, etc. on different qualities.
Yes, I'd confirm that it's sufficient to say the truth :-)
I like one of my pages (you have to scroll to the bottom for the legal stuff): http://www.palettewb.com/
Yep, it's some kind of an advertisement, but for an open source project.
I made some experience with parsing command line options when working on an open source traffic simulation named SUMO (http://sumo.dlr.de) and decided to re-code the options library. It works similar to Python's argparse library - the options are defined first, then you may retrieve the values type-aware.
I do not fear that some agents will pollute my repos with their PR. In opposite, I suppose that we will end at a point where for each question, task, or problem, one will find many (AI-coded) solutions, making it impossible to choose a right, solid, reliable one. I recently thought about having a database of tools per task so that a comparison would be possible. But the maintenance costs of something like this are enormous when including benchmarks, comparisons, etc. on different qualities.