I had an idea, more of a stress-test really.
I have been building my IDE for a few months now, it's actually getting to a pretty solid state, but there's a feature I really wanna try.
Essentially, point it at a repo, have it check the issues/PRs and manage it. It generates a team to manage the codebase and any issue gets delegated to the team member qualified to do it. That team member implements it and the 'team head' reviews it, before a PR is made.
If I run it, pointed at Forem, it'd be going through thousands and probably drain my bank faster than I can hit stop... So instead, what I propose, is I set it up and have it monitor a post's comments. tagged with [feature], [bug], [random], you write your request as a comment and it'll kick off a job to create a PR, then respond to your comment with the PR's link.
The idea being that it can maintain a repo... But private repos dont really have an issues board, you'd likely have a log-sink that errors go to and it'd in that case, look at recurring errors and patch them. Or an app might have a 'user feedback' system, where it'd take that feedback, judge whether it's worth implementing and do it.
The end-goal being when I get Dwarven Stronghold up and running, that'll be the single source of monetization. You can donate, sure, but if you want a feature, it's either free request if it's something genuinely broad-scope, but then it's in a queue, if it's something more urgent, or you want it just for you (who knows, maybe you want pink bearded dwarves), you send your request, it does a quote (literally how much it'd likely cost in development + 5%), then you can pay it and it'll make it. If you're not happy with it, you get 3 rounds of feedback, third being direct to human (me), if you're still not satisfied, then a full refund.
Well that's atleast how I plan on using it. But the core idea is that it becomes your triage team for any project, internal, or external and because you can wire up your own AI provider (including your own), you can essentially use it as your frontline support service... I mostly want to run the experiment to see what's the average cost and success rate, that way I can see whether my VC system, concurrency system and sitemap actually make development cheaper and more accurate. I'll then create a follow-up post after a week or 2 with all the stats, usages, etc. So it's not just a black-box experiment.
Who'd be interested in partaking in the experiment? For the sake of not overwhelming Forem's PR system, these PR's will be pointed at my fork for review, once I've reviewed them, then they'll get pushed through to Forem.
Top comments (6)
Me! Still confused, but I am interested (in Dwarven Stronghold).
Basically, put my money where my mouth is. When I do it, write a comment about something you want or want fixed in dev.to and my IDE will implement it. I'll review it (for research purposes and QC) and then create the PR to forem for it. Simple. Eg. @francistrdev I imagine you'd like a gif search, so you dont have to google them?
Aaaah! I know exactly what I want!
dev.to/effessdev/comment/3f65m
A progress bar! Is this how I am supposed to post the comment?
[feature] add a minimal progress bar at the top of the post page to know how much of the post we have read (progress excludes the comment section)
If I got what you are doing correctly, this is a wonderful idea!
A gif search is useful, but I rarely use the integrated search. I tend to search in Google so that I get a good variety of images to use from. More creativity on my end because you will never know what GIF/Images I use for my article. One day is Anime and the other is just something else.
This is a really interesting experiment. I like that you're measuring the actual cost, success rate, and review process instead of treating AI coding as a black box. The follow-up stats should be especially interesting.